libc-4.4.4 upgrade

libc-4.4.4 upgrade

Post by Bill McCu » Thu, 23 Dec 1993 14:21:14



I am trying to upgrade my c libraries from 4.4.1 to 4.4.4.  The
installation went according to plan, i.e., I installed ld.so-1.3,
inc-4.4.4, and image-4.4.4, but when I try to compile (in particular
link) my program, I get

/usr/lib/crt0.o: Undefined symbol ___fpu_control referenced from text segment
/usr/lib/crt0.o: Undefined symbol ___setfpucw referenced from text segment

It worked fine before the the attempted upgrade.
Any clues about what I did wrong? (kernel 0.99.pl13)


 
 
 

libc-4.4.4 upgrade

Post by Hal N. Broo » Fri, 24 Dec 1993 01:15:33



>I am trying to upgrade my c libraries from 4.4.1 to 4.4.4.  The
>installation went according to plan, i.e., I installed ld.so-1.3,
>inc-4.4.4, and image-4.4.4, but when I try to compile (in particular
>link) my program, I get

>/usr/lib/crt0.o: Undefined symbol ___fpu_control referenced from text segment
>/usr/lib/crt0.o: Undefined symbol ___setfpucw referenced from text segment

>It worked fine before the the attempted upgrade.
>Any clues about what I did wrong? (kernel 0.99.pl13)



When you use the -g option of gcc, /usr/lib/gcrt0.o is linked in rather
than /usr/lib/crt0.o.

With the libc-4.4.4 distribution, /usr/lib/gcrt0.o is only available in
the extra-4.4.4.tar.gz file.

Either get /usr/lib/gcrt0.o out of extra-4.4.4.tar.gz, or don't use
the -g option of gcc.

======================================================================

======================================================================

 
 
 

libc-4.4.4 upgrade

Post by Bob Mart » Fri, 24 Dec 1993 09:45:03


: I am trying to upgrade my c libraries from 4.4.1 to 4.4.4.  The
: installation went according to plan, i.e., I installed ld.so-1.3,
: inc-4.4.4, and image-4.4.4, but when I try to compile (in particular
: link) my program, I get

: /usr/lib/crt0.o: Undefined symbol ___fpu_control referenced from text segment
: /usr/lib/crt0.o: Undefined symbol ___setfpucw referenced from text segment

: It worked fine before the the attempted upgrade.
: Any clues about what I did wrong? (kernel 0.99.pl13)


What version of gcc are you using? 4.4.4 requires 2.4.5 .
--

bob martin  

 
 
 

1. upgrading to libc-4.4.4, gcc-2.4.5, and -mieee-fp

Since I've advised people in the past that it was alright to upgrade
from rather old versions of the kernel, gcc, and libc, to current
versions without heeding the warnings of dependencies, I thought
I should mention the following oversight on my part.

I upgraded to libc-4.4.4 *before* upgrading to gcc-2.4.5, and
as a result, I overwrote the /usr/lib/gcc-lib/i486-linux/2.4.5/specs
file provided in image-4.4.4.tar.gz with the old one that was in
gcc-2.4.5-p1.tar.gz.

The only ill effect of this was that the gcc option "-mieee-fp" didn't
have the desired effect of forcing libieee.a to be linked.

This is just a note to warn everyone about this possibility.  If
your "specs" file is the correct one for use with gcc-2.4.5 and
libc-4.4.4, it should be 519 bytes rather than 500, and it should
have something about ieee in it.

======================================================================

======================================================================

2. Interesting Pickle...

3. Upgrading to libc.4.4

4. User account defaults in OS5

5. Compiling libc-4.4.4: what's mkimage?

6. HTTPD Conf

7. seyon and libc-4.4.4?

8. Running X with Redhat5.2 on MAG LCD LS500

9. Slackware libc-4.4.4 package available

10. tcp.c errors with pl13p and libc-4.4.4?

11. BUG: 'tar +help' doesn't work with libc.so.4.4!!

12. where to get libc-5.4.4

13. [Fwd: Where I can get libc-5.4.4]