On Thu, Nov 16, 2006 at 09:15:35PM +0000, Christos Zoulas wrote:
> In article <20061116142942.GA13660@tibre.lip6.fr>,
> Manuel Bouyer  <bouyer@antioche.eu.org> wrote:
> >Hi,
> >trying to cross-build current on a darwin host (which used to work fine;
> >this is my main build machine for developements) I get (source updated
> >half an hour ago):
> >cc -O3 -mtune=G5 -mcpu=G5 -no-cpp-precomp
> >-I/local/blues1/bouyer/tmp/i386/obj/Volumes/data/bouyer/current/src/tools/compat
> >-I/local/blues1/bouyer/tmp/i386/obj/Volumes/data/bouyer/current/src/tools/compat/include  -I/Volumes/data/bouyer/current/src/tools/paxctl/../compat
> >-DHAVE_NBTOOL_CONFIG_H=1  -D_FILE_OFFSET_BITS=64 -c -o paxctl.lo.o   
> >/Volumes/data/bouyer/current/src/usr.bin/paxctl/paxctl.c
> >/Volumes/data/bouyer/current/src/usr.bin/paxctl/paxctl.c:44:17: elf.h:
> >No such file or directory
> >/Volumes/data/bouyer/current/src/usr.bin/paxctl/paxctl.c: In function
> >`main': /Volumes/data/bouyer/current/src/usr.bin/paxctl/paxctl.c:145:
> >error: parse error before "Elf32_Ehdr"
> >
> >Any idea ?
> >I started from a clean obj and destdir
> 
> I think that we need to supply an elf.h for the platforms that do not have it.

Shouldn't we always supply one, to make sure it has the righ values ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--