Bug 217069 - /usr/bin/ld: cannot find -lgcj
Summary: /usr/bin/ld: cannot find -lgcj
Keywords:
Status: CLOSED DUPLICATE of bug 214195
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 173278
TreeView+ depends on / blocked
 
Reported: 2006-11-23 17:32 UTC by Andrew Cagney
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-11-23 18:49:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Andrew Cagney 2006-11-23 17:32:55 UTC
Description of problem:

Given a minimal install machine with rpms added using (ref:
http://sourceware.org/frysk/build/#fc6 ):

torreja$ sudo yum install -y \
    antlr jdom junit gcc-java gcc-c++ dejagnu \
    libglade-java-devel libvte-java-devel \
    automake xmlto transfig eclipse-ecj dogtail \
    sharutils cvs audit-libs-devel binutils-devel
torreja$ sudo yum install -y \
    glibc-devel.ppc

the command:

torreja$ gcj -m64  -g -O   -o frysk2493/Npe --main=Npe frysk2493/Npe.o
/usr/bin/ld: cannot find -lgcj
collect2: ld returned 1 exit status

fails.  For reference:

$ rpm -qa --queryformat '%{NAME}.%{ARCH}\n' | grep gcj
java-1.4.2-gcj-compat.ppc
libgcj-devel.ppc64
libgcj.ppc
libgcj.ppc64

torreja is in toronto

Comment 1 Andrew Cagney 2006-11-23 17:44:15 UTC
work-around?

torreja$ sudo yum install libgcj-devel.ppc
torreja$ rpm -qa --queryformat '%{NAME}.%{ARCH}\n' | grep gcj
libgcj-devel.ppc
java-1.4.2-gcj-compat.ppc
libgcj.ppc
libgcj.ppc64
torreja$ gcj -m64  -g -O   -o frysk2493/Npe --main=Npe frysk2493/Npe.o
torreja$

confused!


Comment 2 Jakub Jelinek 2006-11-23 18:49:22 UTC
You want gcc 4.1.1-35 and above, this sounds like a dup of #214195.

*** This bug has been marked as a duplicate of 214195 ***

Comment 3 Andrew Cagney 2006-11-23 19:03:18 UTC
$ ssh torreja rpm -q gcc
gcc-4.1.1-30

so yes, likely.  When is 4.1.1-35 gcc available on FC-6?



Note You need to log in before you can comment on or make changes to this bug.