>From: [EMAIL PROTECTED] (Bill Davidsen)
>> - libc.so.5 has been standard less than 2 years ago
> At the time you built the program you could have said that about a.out
>object format. It's not standard now, and while I'm sure there are
>issues with it (or any new library), there were lots of problems with
>libc.so.5 as well, they just didn't bite you.
Well, I have libc.so.5 on a SuSE system installed with the latest
version from August 1998
>> - libc.so.6 has big binary compatibility problems.
>> SuSE/RH libc.so.6 definitely had problems up to the mid
>> of last year. There have even been problems with
>> RH binaries on RH!
> I think the word you want is "had" rather than "has," or at least I've
>seen no problems with RH/Slackware/SuSE in 6+ months.
That's what I like to say: It really seems that during the last 6 months
problems get solved. However, I got a serious report from a guy who
used a RH-6.2 cdrecord binary on RH-6.2 and it did not work correctly.
After he compiled it himself on the same machine, everything worked.
> In what way would your program behave incorrectly if you just linked
>it static? On Linux, of course, I'm told there is/was a problem on
>Solaris. Your software is great, but I don't tend to have multiple
>copies running, don't run it hundreds of times a day in scripts, and
>generally don't care if it is a bit larger than it needs to be, as long
>as it *works* without having to jump through hoops to load libraries or
>other inobvious stuff.
Good question.... One big problem with Linux in general is that
you need a really old system where you compile otherwise binaries
won"t run.
One example: my autoconf always checks for the best variant if several
possible implementations are available for a problem.
As Linux recently introduced a working mmap() which finally allows you
get as much as shared memory for the FIFO as you have RAM.
If you like to run such a binary on a 4 months old Linux, it won't work
beacuse the mmap() was buggy. If you compile on that old system
autoconf selects SYSv shared mem wich limits you to 4 or 12 MB.
> If there are problems in your SCSI library, and I assume there are
>since you have new versions regularly, you don't tell people to go find
>a back version which works right, you fix the problem and tell people to
>go forward.
> I still think that static linked is the better solution, or a build
>agains the latest libc with the probles you saw fixed, and tell people
>to upgrade rather than cling to the past.
At least you cannot use any /dev/sg feature that has been introduced the
last 2 years.
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]
