Changes between Initial Version and Version 3 of Ticket #192


Ignore:
Timestamp:
Jul 26, 2008, 12:48:59 PM (16 years ago)
Author:
mloskot
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #192

    • Property Status newassigned
    • Property Owner set to mloskot
    • Property Versionsvn-trunk
    • Property Milestone3.0.1
    • Property Keywords solaris added
  • Ticket #192 – Description

    initial v3  
    22
    331. In autogen.sh, the existence of libtoolize is checked by using which(1).   Solaris 'which' prints error message ("No such file ..") to standard out instead of standard error, so this procedure fails.   Testing with -x may be an approach that is more portable :
    4 
     4{{{
    55  for libtoolize in glibtoolize libtoolize; do
    66    LIBTOOLIZE=`which $libtoolize 2>/dev/null`
     
    99    fi
    1010  done
    11 
     11}}}
    1212
    13132. In configure.in, additional CFLAGS are appended :
    14    CXXFLAGS="${CXXFLAGS} -Wall -ansi -pedantic -Wno-long-long"
    15    CFLAGS="${CFLAGS} -Wall -ansi -pedantic -Wno-long-long"
     14   
     15{{{
     16CXXFLAGS="${CXXFLAGS} -Wall -ansi -pedantic -Wno-long-long"
     17CFLAGS="${CFLAGS} -Wall -ansi -pedantic -Wno-long-long"
     18}}}
    1619
    1720Since these are gcc'isms, compilation with other compilers fails.   I think there is a portable  autoconf macro for adding pedantic/all-warning somewhere.. Otherwise, a test based on uname(1) or a small compilation test macro should solve the problem.
    18