Date: Tue, 21 May 2002 14:03:41 +0000 From: "J. Mallett" <jmallett@FreeBSD.ORG> To: Ruslan Ermilov <ru@FreeBSD.ORG> Cc: "J. Mallett" <jmallett@FreeBSD.ORG>, Mike Barcroft <mike@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/elf2aout elf2aout.c Message-ID: <20020521140340.GA9107@FreeBSD.ORG> In-Reply-To: <20020521135256.GA10621@sunbay.com> References: <200205200756.g4K7ueM28492@freefall.freebsd.org> <20020520125748.E8089@espresso.q9media.com> <20020521074034.GB53675@sunbay.com> <20020521042755.B56179@espresso.q9media.com> <20020521093456.GA74330@sunbay.com> <20020521133802.GB5716@FreeBSD.ORG> <20020521135256.GA10621@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 21, 2002 at 04:52:56PM +0300, Ruslan Ermilov wrote: > > You just lamented having to do 'make includes'. > > > > Now, consider that when bootstrapping we use the host includes. I doubt a > > host uses types it doesn't understand. > > > Yes, so what? How changing src/sys/sys/elf32.h to use uint32_t breaks > bootstrapping? (We don't use it during bootstrapping.) I was referring to your implication that <sys/elf32.h> is broken because it uses the less portable type, despite the fact that if someone has our elf32.h, it should really only work with our complete set of headers, and therefore they will have the appropriate types. I probably just misunderstood you, or you said it off-handedly and forgot or something. My point was that our <sys/> headers aren't expected to be portable with a set of host includes being used with them. Thanks. -- jmallett@FreeBSD.org | C, MIPS, POSIX, UNIX, BSD, IRC Geek. http://www.FreeBSD.org | The Power to Serve Vote for me for FreeBSD core or the cute little bunny gets it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020521140340.GA9107>