>From [EMAIL PROTECTED] Thu Jun 21 00:44:08 2001
>> >>From [EMAIL PROTECTED] Thu Jun 21 00:19:14 2001
>>
>> >If you create your own stdio implementation, wouldn't it be a better
>> >idea to create your own stdio.h too instead of relying on the glibc
>> >version?
>>
>> I am doing this since 1984..... I believe the way I do it now is the best way.
>What I meant was: you don't have your own stdio.h. You're using the
>one from the system (printf.c does #include <stdio.h> and there is no
>stdio.h in the cdrtools package).
>I think it would make more sense for you to write your own
>(minimalist) stdio.h file. It would match your own stdio perfectly,
>and you wouldn't have the gcc 3.0 problems at all.
It would be very hard to make such an approach portable.
If you decide to have your own stdio.h, it should be POSIX compliant.
Unfortunately, stdio.h relies on many implementation specific stuff like
the local stdio package as well as on POSIX oddities. Believe me, it's
close to imposible to do this with stdio.h in a portable way.
Writing portable software is like driving a ship in a wild river.
If you notice that you only have few contacts to the riverside yo know
that you are driving at the right place...
Adding support for a new OS for all my software has become simpler amd simpler
within the last few years. In total, I currently own ~ 10 MB of software.
Not all of this software has already been released as Open Source software.
If I go to a new OS, I usually first compile 'smake'. This is very easy because
smake doesn't need a make program to bootstrap. As smake includes automake
features, it will create missing rule files for the makefile system on the fly.
Next step is compiling star as you usually cannot rely on the local
tar implementaion. Using smake and it's automake features, this usually works
even without manual intervention. Note that the smake & the star source tree
both have been designed not to rely on symlinks to make boostrap easier.
Star has a -copylinks option that allows to convert symlinks into copies, if the
target OS does not support symlinks.
Third step is to unpack the tar archive of my whole source structure and to run
smake on it. For the last few new OS'es I added, the time to make everything
work was around 2 hours!
The final hard work is to add SCSI transport support for the new OS into libscg.
This usually takes ~ one month in total.
J�rg
EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni) If you don't have iso-8859-1
[EMAIL PROTECTED] (work) chars I am J"org Schilling
URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
