It figures out the name on the fly, so it will differ. I will eventually post a complete chrooted libc5 kit that will be foolproof in that it won't depend on how your system is configured. -Tom On Tue, 14 Nov 2000, Henricus Holtman wrote: > Date: Tue, 14 Nov 2000 01:00:11 -0800 > From: Henricus Holtman <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: I think doc error in toms-libc5-kit-0.3 > > In README in toms-libc5-kit-0.3 you say: > > (3) To compile to libc5, you then need to make your gcc really be: > > gcc -nostdinc \ > -I/usr/i586-pc-linux-tomsrtbt/include \ > -I/usr/lib/gcc-lib/i586-pc-linux-tomsrtbt/2.95.1/include \ > -bi586-pc-linux-tomsrtbt > > I think you mean to say: > > > (3) To compile to libc5, you then need to make your gcc really be: > > gcc -nostdinc \ > -I/usr/i586-pc-linux-tomsrtbt/include \ > -I/usr/lib/gcc-lib/i586-pc-linux-tomsrtbt/egcs-2.91.66/include \ > -bi586-pc-linux-tomsrtbt > > > With this figured out I was able to compile afio, and run it against > tomsrtbt, > which made me very happy. > > Thank you, > Henricus Holtman >
