RE: GNU gcc upgrades

-----Original Message-----
From: Daniel C. von Asmuth [mailto:asmuth-8LkvcxCLB6JmR6Xm/[email protected]]
> If have almost never encountered such problems even when I compiled code
> with different compilers (not just GNU ones), though I have recently had
> trouble with the OpenSSL library on an OS the name of which shall not be
> mentioned in polite company (but it compiled fine).
>
> Of course, if you are not programming in C, but rather in C++, you are
> looking for trouble. (why do you suppose somebody invented Java and C minor
> in the first place?)

I know nothing about c++ nor do I care to learn, code was written in C and the problems occurred twice, after a Linux upgrade each time, first from a 1.12 kernel to a 2.0, then from a 2.0 to a 2.2. Each time the libc changed, and each time I had to rework the code. At least, if it's my code, then it's not so bad as i know what it's meant to do. I hate to work on other people's code.

As for Java, it wasn't invented for coping with changes in compilers but with changes in platforms. In my case the platform remained the same.

Maybe you're just lucky.

I also note that trying to upgrade to a 2.4.13 kernel failed because the kernel would not compile, hence why I'm still running a 2.2 kernel at the moment. Since I'm about to load the 2.4 on a spare PC, I look forward to a new set of warning/errors that the new libc will generate :^)

I also know a few people who ended up removing the latest glibc and reverted to a prior version because nothing worked anymore. And these are professional programmers, not mere amateurs like myself.

John

EOM 

NOTICE - This message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein.  If you have received this message in error please notify the sender immediately and delete the message.