Subject: Re: build.sh failure
To: Todd Vierling <firstname.lastname@example.org>
From: James Chacon <email@example.com>
Date: 02/19/2003 14:35:56
Yes..Remember, that build.sh is assuming a known stable working host system
that can build local tools/programs.
If your host system can't compile things, then nothing is gonna work..
>On Wed, 19 Feb 2003, Emmanuel Dreyfus wrote:
>: > Looks like the host machine's libc.so doesn't have __times13(), a
>: > version-renamed function defined by a later version of a .h file in
>: > /usr/include. Make sure your libc.so on the sgimips machine is at least as
>: > new as the files in /usr/include.
>: I thought build.sh was removingthis kind of troubles?
>Huh? If your host system has newer .h includes than the build of libc.so,
>things will break. build.sh cannot correct this for you.
>One way .h files and libc.so can get out of sync is if you are doing a
>(native, not cross) build to DESTDIR=/ and the build stops between the "make
>includes" step and the step where src/lib is installed.
>-- Todd Vierling <firstname.lastname@example.org>