Can't link X apps - missing shared lib?

Can't link X apps - missing shared lib?

Post by Michael P Lindn » Tue, 24 Oct 1995 04:00:00



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

 
 
 

Can't link X apps - missing shared lib?

Post by Doug Summervil » Wed, 25 Oct 1995 04:00:00



: 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

 
 
 

Can't link X apps - missing shared lib?

Post by Doug Summervil » Thu, 26 Oct 1995 04:00:00


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

 
 
 

Can't link X apps - missing shared lib?

Post by B.A.McCau.. » Thu, 26 Oct 1995 04:00:00




>: 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.

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

 
 
 

1. Linking with Shared and Non-shared libs.

This may be a stupid question but...

I have built X11 R5 for my rs6000 running AIX 3.2, the default
ibm.cf specifies the rules for building shared libraries. R5 is
great, however when I try to run an application that that was
linked with the Motif lib (from IBM 1.1.4 ,non-shared) and the
new X11R5 libs (shared) I get the following:

root on ief% testit.rs6000
Could not load program testit.rs6000
Could not load library libXm.a[shr4.o]
Error was: No such file or directory

I've tried the -bnso -bI:/lib/syscalls.exp flags but then the
linker has a bunch of unknown symbols.

Any help would be appreciated...

--


IEF Development                     |     TIMSG: BLOC
Texas Instruments, Plano Texas      |     (214) 575-4732

2. file saving problem after mounting

3. Why can't I link w/ shared X libs?

4. Problem with "vi"

5. Help - shared libs lib****.so.4 lib***.so.5

6. moving files prior to 2 days

7. convert 'a' lib' into 'so' lib

8. changing process name

9. X lib missing for some apps, help

10. Profiling an App(missing lib)

11. GCC 3.1 build fails - '/usr/lib/sparcv9/values-Xa.o' missing

12. Slackware 2.2's GCC doesn't link X libs

13. 2.1.5 Emacs Package requires a missing Shared Lib