On Sun, 2012-11-25 at 17:37 +0100, Pierre Labastie wrote:
> Hello,
>
> I know it has been reported by Tobias on lfs-support, but it seems to me
> it is an issue with the current version of check, and it should be
> addressed in the book:
> - the error occurs during make:
> ----------------------------
> /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I.. -O3 -pipe -march=native -Wall -ansi -pedantic -Wextra
> -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings
> -Wno-variadic-macros -MT putenv.lo -MD -MP -MF .deps/putenv.Tpo -c -o
> putenv.lo putenv.c
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O3 -pipe -march=native
> -Wall -ansi -pedantic -Wextra -Wstrict-prototypes -Wmissing-prototypes
> -Wwrite-strings -Wno-variadic-macros -MT putenv.lo -MD -MP -MF
> .deps/putenv.Tpo -c putenv.c -fPIC -DPIC -o .libs/putenv.o
> putenv.c:5:1: error: expected identifier or '(' before '{' token
> make[2]: *** [putenv.lo] Error 1
> make[2]: Leaving directory `/mnt/lfs/sources/check-0.9.9/lib'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/mnt/lfs/sources/check-0.9.9'
> make: *** [all] Error 2
> ------------------------------
> The reason is clearly a syntax error in the file putenv.c :
> ----------------------
> > less lib/putenv.c
>
> #include "libcompat.h"
>
> int
> putenv (const char *string CK_ATTRIBUTE_UNUSED);
> {
> assert (0);
> return 0;
> }
> -------------------------
> On the other hand, this file should not be compiled, since it is a
> fallback if putenv is not present, but it is easy to check that putenv
> is in the glibc library. Now, in configure output, we have:
> --------------------------
> checking for pipe... no
> checking for putenv... no
> checking for setenv... no
> checking for sleep... no
> checking for strdup... no
> checking for strsignal... no
> checking for unsetenv... no
> --------------------------------
Hmm, on a Fedora 17 host, I get:
checking for pipe... yes
checking for putenv... yes
checking for setenv... yes
checking for sleep... yes
checking for strdup... yes
checking for strsignal... yes
checking for unsetenv... yes
Looks like something is broken/out of date on your host!
Thanks,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
