public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: povey@dstc.edu.au
To: java-gnats@sourceware.cygnus.com
Subject: libgcj/1211: libtool broken on Solaris 2.6
Date: Wed, 20 Dec 2000 12:21:00 -0000	[thread overview]
Message-ID: <19990802025355.17046.qmail@egcs.cygnus.com> (raw)

>Number:         1211
>Category:       libgcj
>Synopsis:       libtool broken on Solaris 2.6
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    tromey
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 12:17:40 PST 2000
>Closed-Date:    Mon Aug 02 20:20:40 PDT 1999
>Last-Modified:  Mon Aug 02 20:20:40 PDT 1999
>Originator:     povey@dstc.edu.au
>Release:        libgcj-2.95
>Organization:
>Environment:
sparc-sun-solaris2.6
>Description:
libtool fails when linking shared libs.  The following error
is given:

ld: warning: option -o appears more than once, first setting taken
ld: fatal: file libgcj.so.0: cannot open file: No such file or directory
ld: fatal: File processing errors. No output written to .libs/libgcj.so.0.0.0
collect2: ld returned 1 exit status
>How-To-Repeat:
Occurs when running make
>Fix:
I replaced the configured libtool with a local copy built
from libtool-1.3.3 and replaced the libtool-1.2f version
shipped with libgcj and it compiled fine.
>Release-Note:

>Audit-Trail:

Formerly PR libgcj/16

State-Changed-From-To: open->closed
State-Changed-By: tromey
State-Changed-When: Mon Aug  2 20:20:40 1999
State-Changed-Why:
I've updated libgcj to use libtool 1.3.3.
I did this on both the trunk and the 2.95 branch
(in case we ever make a 2.95.1 release from that
same branch).
Since you report that this fixes the problem, 
I've changed the PR directly to "closed" instead
of going through a feedback cycle.
On the off chance that this doesn't fix it,
please report back.
>Unformatted:



                 reply	other threads:[~2000-12-20 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19990802025355.17046.qmail@egcs.cygnus.com \
    --to=povey@dstc.edu.au \
    --cc=java-gnats@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).