linking problem

linking problem

Post by Ching-jung Ch » Sat, 30 Dec 1995 04:00:00



Could somebody tell me how to solve this problem while linking my programs ??

ld: Output file requires shared library `libc.so.4'
gcc: Internal compiler error: program ld got fatal signal 6

The gcc options were  -g -ansi. If I remove -g then it works fine.
I am using gcc version 2.6.3 and libc.so.4.6.27. (They came with
slackware 2.0, on Pentium 133)

Thanks.

-cjchen

 
 
 

linking problem

Post by William S. Gribb » Sat, 30 Dec 1995 04:00:00




> >ld: Output file requires shared library `libc.so.4'
> >gcc: Internal compiler error: program ld got fatal signal 6

> On my system, /lib/libc.so.4 is a symbolic link to
> /lib/libc.so.4.6.27.  If you don't have the symbolic link, put it in
> (or maybe your /lib/libc.so.4 is a symbolic link to a different file
> that maybe doesn't exist).

Possible, but unlikely.  This problem is 99.9999999% likely to be caused by
a bug in binutils and the -g option on the original poster's final
link command line.  

Remove the -g from your final link step and see if that doesn't fix it.

Bill Gribble

 
 
 

linking problem

Post by Francis C. Swas » Sat, 30 Dec 1995 04:00:00




Quote:>Could somebody tell me how to solve this problem while linking my programs ??

>ld: Output file requires shared library `libc.so.4'
>gcc: Internal compiler error: program ld got fatal signal 6

On my system, /lib/libc.so.4 is a symbolic link to
/lib/libc.so.4.6.27.  If you don't have the symbolic link, put it in
(or maybe your /lib/libc.so.4 is a symbolic link to a different file
that maybe doesn't exist).

Frank
--

Tel: 802-769-4011 (tie: 446), Fax: 802-769-4253 (tie: 446)    (o o)
           Speaking *from* but not *for* IBM             -oOO--(_)--OOo-

 
 
 

linking problem

Post by jviss » Tue, 02 Jan 1996 04:00:00





>> >ld: Output file requires shared library `libc.so.4'
>> >gcc: Internal compiler error: program ld got fatal signal 6

>> On my system, /lib/libc.so.4 is a symbolic link to
>> /lib/libc.so.4.6.27.  If you don't have the symbolic link, put it in
>> (or maybe your /lib/libc.so.4 is a symbolic link to a different file
>> that maybe doesn't exist).
>Possible, but unlikely.  This problem is 99.9999999% likely to be caused by
>a bug in binutils and the -g option on the original poster's final
>link command line.  
>Remove the -g from your final link step and see if that doesn't fix it.
>Bill Gribble

Try giving the -lc explicitly when isuing the -g option

Johann

 
 
 

1. Metro Link Motif linking problem

I am having a problem linking an X/Motif application with the static libraries
in Metro Link Motif 2.0.1.   If I add the -static directive in the makefile I
get "undefined reference" errors for everything in the Motif libs.  I checked
and all of the .a files are there with the .so files.  I used nm to verify each
of the unresolved symbols was actually contained in the libraries I specified in
the make.  Another application that is built by the same makefile that doesn't
use any X or Motif libs compiles fine(statically) and grows tenfold in size.  I
also tried to build the .a files directly(with fully qualified pathname) instead
of using -l and had the same problem.  Any ideas???

Thanks,
bill

2. CDPATH problem in KSH and BASH

3. 2.4.18 linking problem - ?configuration options problem?

4. EXA 8500 with Solaris v7

5. Problems compiling fvwm => linking problem

6. Slackware 3.1

7. xwave linking problems "undefined reference"

8. Vinnie Jordan of SCO sends derogatory mail.

9. X library link problems

10. Strange linking problem (__divss,__divus)

11. HELP: linking problem on Linux

12. fvwm-1.24r link problem

13. GhostScript compilation/linking problem