Patrik Lundin <pat...@sigterm.se> writes: > Hello, > > When looking at the output of ./configure in net/kea I noticed the > following warning which I have previously missed: > === > ./configure[15929]: test: <: unexpected operator/operand > === > > The responsible code in the configure script should be this: > === > # gcc 4.4 would emit warnings about breaking strict aliasing rules. > # See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41874 > CXX_DUMP_VERSION=`$CXX -dumpversion | cut -f1-2 -d.` > if test "$CXX_DUMP_VERSION" \< "4.5"; then > WARNING_GCC_44_STRICT_ALIASING_CFLAG="-fno-strict-aliasing" > fi > === > > The error message is thrown because the builtin test does not support > the "<" operator (which /bin/test does). > > The funny thing is that gcc in base does not seem to suffer from the > bug that is described in the bug tracker linked above, because the build > generates no warnings relating to strict-aliasing. > > This means that the failing "test" can actually be thought of as a > feature. It is of course brittle, and will modify the build parameters > if someone decides to teach the test builtin about "<" prior to bumping > base gcc past 4.5.
This is a very unlikely scenario. > Basically I am just asking for pointers from other porters, anyone have > an idea how I should deal with this? Should I bother at all? I guess you could just use /bin/test. -- jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
