On 7/7/07, Martin Schröder
2007/7/7, George N. White III
: I (slightly) abused your build.sh configuration by compiling with -std=c99 on Fedora Release 7 (i686, gcc (GCC) 4.1.2 20070502 (Red Hat 4.1.2-12)) and using system libraries (fewer chances for the compile to fail and less time to compile):
Not that it should make a difference, but does the standard build.sh work?
Yes -- not tested, but the .pool files are identical between the standard build and my -std=c99 build.
I have no problems with OpenSUSE 10.1 (gcc (GCC) 4.1.0 (SUSE Linux)) and 10.2 (gcc (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux)) and -std=c99 -Wall.
Interesting. Could it be that Red Hat has a different take on whether strsep is
visible under std=c99?
CC='cc -std=c99 -Wall' ./build.sh > build-c99-Wall.log 2>&1
failed at the same place, and from this build,
source/build/libs/obsdcompat/config.log
fails to detect strsep:
configure:5077: checking whether strsep is declared
configure:5106: cc -std=c99 -Wall -c -g -O2 -Wall -Wpointer-arith
-Wuninitialized -Wsign-compare -Wno-pointer-sign conftest.c >&5
conftest.c: In function 'main':
conftest.c:50: error: 'strsep' undeclared (first use in this function)
conftest.c:50: error: (Each undeclared identifier is reported only once
conftest.c:50: error: for each function it appears in.)
conftest.c:50: warning: unused variable 'p'
configure:5112: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| // ...shortened
| #define HAVE_STRING_H 1
| //...
| /* end confdefs.h. */
|
| #ifdef HAVE_STRING_H
| # include