Very Computer

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

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

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-

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

Very Computer

linking problem

linking problem

linking problem

linking problem

linking problem