> > Is there a libc5 version of sfdisk available which anyone has gotten
> > to work with tomsrtbt?
>
> I will be releasing a foolproof libc5 compilation environment so it will
> be much easier to builod your own libc5 stuff.  Until then, consider that
> the normal fdisk is also batchable.  Just put the commands, exactly as
> they need to be typed, into a file, then run fdisk with that file as the
> input.  The format will be much uglier than it is with sfdisk, but it does
> work fine.

 The libc5 compile kit that you've announced earlier worked fine for me
(after some struggle) w/ a minor change. I use
"CC=gcc -bi586-pc-linux-tomsrtbt -isystem
/usr/i586-pc-linux-tomsrtbt/include" (I've got the same version of gcc as
you used to furnish the compile kit).

 This change enabled me to compile the latest dosemu for libc5 even though
dosemu got lots and lots of local .header files with names that collide with
files in /usr/include. Some rules specify -nostdinc themselves and these I
guess a cc.sh shell script would be needed (to make automagic).

 I'll be working more on this when/if I get more time; shouldn't it be
possible to change all the default include paths in the spec files? Given
that atleast /usr/include is hardcoded into gcc it might be easier to
symlink all the necessary directories at runtime (ugly, ugly, ugly).

 George: I've just downloaded the util-linux2.10o.bz2 tarball. I'll mail you
a libc5 version shortly.


//Bj�rnen.

Reply via email to