binutils chapter5

Ken Moffat ken at kenmoffat.uklinux.net
Mon May 3 08:27:12 PDT 2004


On Mon, 3 May 2004 vincent.vandaele at tele2.fr reposted:

> Hello
> When I compile binutils in chapter 5
> when I run   make LDFLAGS="-all-static"
> I have
>
> -W -Wall -Wtraditional -pedantic  ../../binutils-2.14/libiberty/fdmatch.c -o pic/fdmatch.o; \ else true; fi gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../binutils-2.14/libiberty/../include  -W -Wall -Wtraditional -pedantic ../../binutils-2.14/libiberty/fdmatch.c -o fdmatch.o if [ x"" != x ]; then \
>   gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../binutils-2.14/libiberty/../include  -W -Wall -Wtraditional -pedantic  ../../binutils-2.14/libiberty/fibheap.c -o pic/fibheap.o; \ else true; fi gcc -c -DHAVE_CONFIG_H -g -O2 -I. -I../../binutils-2.14/libiberty/../include  -W -Wall -Wtraditional -pedantic ../../binutils-2.14/libiberty/fibheap.c -o fibheap.o
> ../../binutils-2.14/libiberty/fibheap.c: In function `fibheap_delete_node':
> ../../binutils-2.14/libiberty/fibheap.c:285: error: `LONG_MIN' undeclared (first use in this function)
> ../../binutils-2.14/libiberty/fibheap.c:285: error: (Each undeclared identifier is reported only once
> ../../binutils-2.14/libiberty/fibheap.c:285: error: for each function it appears in.)
> make[1]: *** [fibheap.o] Error 1
> make[1]: Leaving directory `/mnt/lfs/sources/binutils-build/libiberty'
> make: *** [all-libiberty] Error 2
>
> Thanks
>

 OK, so you're trying to restart and you can't get any help locally.
In this case, google doesn't seem very helpful, so you're thrown back
onto your own analytical and debugging skills - you built LFS before,
with some difficulties, but I imagine this wasn't one of them.  So,
think back and identify what has changed in either the host, or in how
you are trying to build.

 Because LONG_MIN is in capitals, it looks as if it's a macro, which
often means it comes from a header file.  Did you trash the Mandrake
host when you lost your first LFS ?  Is there an error message some way
above what you posted, saying that in include file was not found ?  Does
$PATH look sensible ?

 I've no idea what the problem is, but programming is far more about
debugging the broken stuff than it is about writing shiny new programs,
so developing the analytical skill will be worth your while.

Ken
-- 
 das eine Mal als Tragödie, das andere Mal als Farce




More information about the lfs-support mailing list