Very Computer

Whenever I try to compile somthing that uses X, I get

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

I am using gcc 2.6.3 and X 3.1.1.  There IS a libc.so.4, which is
symbolically linked to /lib/libc.so.4.6.27.  However, ldconfig only
shows it up as /lib/libc.so.4.6.27.

What do I need to do to successfully link an X app?  E-mail responses
preferred.

--
Michael Lindner


--
Michael P Lindner

: Whenever I try to compile somthing that uses X, I get

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

: I am using gcc 2.6.3 and X 3.1.1.  There IS a libc.so.4, which is
: symbolically linked to /lib/libc.so.4.6.27.  However, ldconfig only
: shows it up as /lib/libc.so.4.6.27.

I have posted a similar question to another group.  I get exactly
the same error message when I try to compile a program with
debugging info.  When I compile without debugging info all is well.
If you get a response by email please pass it along.

Thanks in advance,
Doug

This is a reply to the original post and my previous reply as I have
solved my own problem and possibly yours.  All I did was add a -lc
to the command line so that the compiler user the standard C (?)
library which it was looking for.

gcc blah blah blah -lc

Doug

AFIAK the point it is making is that you have linked together object
files that need libc.so.4 *and* ones that need
libc.so.something_else. This would produce a runtime link confict.
--

 .  _\\__[oo       from       | Phones: +44 121 471 3789 (home)

.  l___\\    /~~) /~~[  /   [ | PGP-fp: D7 03 2A 4B D8 3A 05 37
 # ll  l\\  ~~~~ ~   ~ ~    ~ |         A1 93 FE EA BE E3 2A 91