public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jrt at worldlinc dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/48533] New: Installer fails on libjava component
Date: Sat, 09 Apr 2011 19:05:00 -0000	[thread overview]
Message-ID: <bug-48533-8172@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48533

           Summary: Installer fails on libjava component
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jrt@worldlinc.net


I just built gcc-4.6.0 with all components requested, built with /usr/local/ as
prefix. Ada not built. On "make install", libjava fails later in installation
process because it tries to find and link a libppl file by looking in /usr/lib
instead of /usr/local/lib. I copied the first not-found file into /usr/lib and
it linked that and failed on the next one. This system has two versions of ppl
and cloog files, 0.10.2 in /usr and 0.11 in /usr/local. The first is required
for gcc-4.4.5 and the other for 4.6.0 and the linkers and installer should find
the right version for the right gcc. The installer goes looking first in
/usr/lib and fails, though. Why doesn't it at least use the system library path
which is said to list /usr/local/lib before /usr/lib? The only references to
the wrong prefix that I found in the top makefile and the libjava makefile are
in the var oldincludedir=/usr/include.


             reply	other threads:[~2011-04-09 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 19:05 jrt at worldlinc dot net [this message]
2011-04-13 18:53 ` [Bug libgcj/48533] " jrt at worldlinc dot net
2011-04-14 17:02 ` jrt at worldlinc dot net
2011-05-29 20:32 ` joakimds at kth dot se

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=bug-48533-8172@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).