upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

Post by Steve Farre » Mon, 25 Mar 1996 04:00:00



in the short time i had libc-5.2.18 installed (vs my out of the box
slackware 3.0 libc-5.0.9) my sendmail stopped working (presumably
file-locking was broken), and make stopped working.  

anyone have anything to say about this?  is this just something
people deal with?   i was rather shocked and frustrated to have
so many vital functions fail when "upgrading" my c library!

what's up?

 
 
 

upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

Post by Arthur D. Jeriji » Mon, 25 Mar 1996 04:00:00



>in the short time i had libc-5.2.18 installed (vs my out of the box
>slackware 3.0 libc-5.0.9) my sendmail stopped working (presumably
>file-locking was broken), and make stopped working.  

        I don't know about the sendmail problem (perhaps an upgrade and
a recompile might help), but I do know that you need to download the
source code for GNU make 3.74 and the release notes for libc-5.2.18.
Just patch the make sources with the diff in the release notes, rebuild
make, and you're ready to go.

Quote:>anyone have anything to say about this?  is this just something
>people deal with?   i was rather shocked and frustrated to have
>so many vital functions fail when "upgrading" my c library!
>what's up?

        Unfortunately, things like this happen in the Linux world
with all of its dynamic development.  For instance, look at the transition
from a.out to ELF.  Those who use libc-5.3.x need to worry about
even more programs breaking because of malloc() changes.  Personally,
I think this is healthy development; it is at least better than
maintaining strict backwards compatibility, as is done in the
Microsoft world.

        I hope this helps.



 
 
 

upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

Post by Andy Walke » Mon, 25 Mar 1996 04:00:00



> in the short time i had libc-5.2.18 installed (vs my out of the box
> slackware 3.0 libc-5.0.9) my sendmail stopped working (presumably
> file-locking was broken), and make stopped working.

> anyone have anything to say about this?  is this just something
> people deal with?   i was rather shocked and frustrated to have
> so many vital functions fail when "upgrading" my c library!

> what's up?

Did you read the file release.libc-5.2.18? It states there that
make *WILL* break, because of a bug in make which fortunately
didn't bite with older libc's. It also provides a patch for
recompiling make. If you've installed Slackware you should be
able to fetch the make sources, patch them, and compile a new
version using the Berkeley pmake that is also installed as part
of Slackware.

I recommend fetching make-1.74.2.tar.gz from alpha.gnu.ai.mit.edu
as this fixes both the above bug, and the problem with killing
make processes (i.e. hitting ctrl-c on a kernel make used to stop
the parent make, but not the sub-processes).

I'm surprised that you think sendmail is broken. It shouldn't be,
although I've never personally tested the code that is supposed
to handle a missing flock() system call (i.e. 1.2.x kernels).
What kernel are you running?

-Andy

 
 
 

upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

Post by MJ Gumbl » Wed, 27 Mar 1996 04:00:00


:
: in the short time i had libc-5.2.18 installed (vs my out of the box
: slackware 3.0 libc-5.0.9) my sendmail stopped working (presumably
: file-locking was broken), and make stopped working.  
:
: anyone have anything to say about this?  is this just something
: people deal with?   i was rather shocked and frustrated to have
: so many vital functions fail when "upgrading" my c library!

I had this too, last night.... what is the latest working libc.5?

--

 
 
 

upgrading from libc-5.0.9 -> libc-5.2.18 brakes system?

Post by Karl Heinz Kreme » Thu, 28 Mar 1996 04:00:00




> :
> : in the short time i had libc-5.2.18 installed (vs my out of the box
> : slackware 3.0 libc-5.0.9) my sendmail stopped working (presumably
> : file-locking was broken), and make stopped working.
> :
> : anyone have anything to say about this?  is this just something
> : people deal with?   i was rather shocked and frustrated to have
> : so many vital functions fail when "upgrading" my c library!

> I had this too, last night.... what is the latest working libc.5?

There is a new version of make available on sunsite that works
with libc-5.2.18.

The problem with sendmail (at least on my machine) turned out
to be a procmail problem. I was using procmail as the local
mailer. Whenever sendmail tried to deliver mail locally the
problem occured. (this also showed up when I run procmail
manually).

After changing the local mailer to "deliver" sendmail was
working fine again.

I had no time yet to re-compile procmail (or try to fix it),
so I'll stick with deliver for a while.

Karl Heinz

--
Karl Heinz Kremer    http://vsun02.ag01.kodak.com     Kodak AG
FAX: +49.7335.12 7271              Telephone: +49.7335.12 7673
KNET/KMX: 631 7673                        PROFS: (KOKAG) K2080

 
 
 

1. problems upgrading libraries - libc-5.0.9 -> libc-5.2.18

-----BEGIN PGP SIGNED MESSAGE-----

hi,

i'm having a major problem upgrading to libc-5.2.18 from libc-5.0.9.
my system is already ~85% ELF, running linux 1.2.11.

here's what i do:

1) install gcc 2.7.2 binaries

2) install binutils-2.6.0.2.bin

3) install ld.so-1.7.14

4) install libc-5.2.18.bin as per instructions:
     cd /
     rm -f /usr/lib/libc.so /usr/lib/libm.so
     rm -f /usr/include/iolibio.h /usr/include/iostdio.h
     rm -f /usr/include/ld_so_config.h /usr/include/localeinfo.h
     rm -rf /usr/include/netinet /usr/include/net /usr/include/pthread
     tar -xzf libc-5.2.18.bin.tar.gz

so, i've got three independent problems. A is minor B and C are major.

A) the ldconfig that comes with ld.so-1.7.14 doesn't work for me.  if
i compile it myself though, it works fine.  no big deal really but i
would think it should work 'out of the box'.

B) everything works ok until i install the new libc.  after installing
the new libc, a variety of commands fail to work, including:
ls, whereis, clear, rm, etc.  basically, a lot of /usr/bin stops
working.  that is, if i try to do a ls, i see nothing.  it just
doesn't list anything but returns no errors.

any ideas about this?  a lot of /usr/bin was updated using slackware
3.0 to get an ELF system and perhaps this wasn't the best choice.
where the hell is ls kept?  i haven't been able to figure out what to
d/l from tsx-11 yet so i can compile my own ls, especially one that is
statically linked for these events.

any ideas?  anyone know where i can find the programs in /usr/bin?

C) finally, after upgrading to the new libm (libm.so.5.0.5) programs will
no longer compile, i always get the same error -
/usr/lib/libm.so: undefined reference to `__errno_location'

using libm.so.5.0.0 however elminates this error.

so, what's going on!  my system is being too weird.

- -pjf


U of Utah biochem grad student in the Bass lab - zinc fingers + dsRNA!

zifi runs LINUX 1.2.11 -=-=-=WEB=-=-=->  http://zifi.genetics.utah.edu

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Say NO to GAK! - fight for your privacy!

iQCVAwUBMOcJ503Qo/lG0AH5AQEiQQP/UTFYJPnfe1RB7GFmuo0v0f3U5bheP+j4
3DED+ItXNM5y9A70V+UGP2//yVwtjL8GDJA3N+ai3QdjhfjGndcVIsQIoVWmYvU3
Rc8TdC5PwEqivA68eU8jqBPSe03PxP9EKWsrg4HPuCgZJQGR8S/BO/KEAwLv5Klf
TNh49zokY5w=
=qD9k
-----END PGP SIGNATURE-----
--

U of Utah biochem grad student in the Bass lab - zinc fingers + dsRNA!

zifi runs LINUX 1.2.11 -=-=-=WEB=-=-=->  http://zifi.genetics.utah.edu

2. Security systems..

3. Problems with "make" when upgrading to libc-5.2.18

4. System crash

5. How to upgrade to 2.0 without libc-5.2.18?

6. subscribe

7. Tips for compiling libc-5.2.18 with 1.3.* include files (Was: filedoalloc.o in libc-5.2.18, not ok with linux-1.3.72 headers, ok with 1.2.13)

8. Only one partition OK?

9. ld.so-1.7.14 + libc-5.2.18

10. Problems with libc-5.2.18

11. building libc-5.2.18

12. Is libc-5.2.18 broken ?

13. SIGFPE and libc-5.2.18