public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/60261] New: [4.9 Regression] Weird java install with --enable-version-specific-runtime-libs
Date: Tue, 18 Feb 2014 11:17:00 -0000	[thread overview]
Message-ID: <bug-60261-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60261
           Summary: [4.9 Regression] Weird java install with
                    --enable-version-specific-runtime-libs
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P3
         Component: java
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rguenth at gcc dot gnu.org

I get in

/usr/lib64/gcc/x86_64-suse-linux/
4.9  gcj-4.9-15  lib64  logging.properties  security

/usr/lib64/gcc/x86_64-suse-linux/4.9/
ecj.jar  include  jvgenmain        libgcj.la  libgcj.spec   libgij.so
ecj1     jc1      libgcj-tools.so  libgcj.so  libgcj_bc.so  pkgconfig

/usr/lib64/gcc/x86_64-suse-linux/gcj-4.9-15/
libjavamath.la  libjavamath.so

/usr/lib64/gcc/x86_64-suse-linux/lib64/gcj-4.9-15
classmap.db  libjvm.la  libjvm.so

not sure what happens without --enable-version-specific-runtime-libs.

Behaved "more sanely" with 4.8, everything under /usr/lib64/gcj-4.8-14/
(I also have --program-suffix=4.x)


             reply	other threads:[~2014-02-18 11:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 11:17 rguenth at gcc dot gnu.org [this message]
2014-02-18 11:18 ` [Bug java/60261] " rguenth at gcc dot gnu.org
2014-02-18 11:36 ` rguenth at gcc dot gnu.org
2014-02-18 11:47 ` rguenth at gcc dot gnu.org
2014-02-18 12:05 ` rguenth at gcc dot gnu.org
2014-02-18 12:50 ` rguenth at gcc dot gnu.org
2014-02-18 12:56 ` rguenth at gcc dot gnu.org
2014-02-20  8:43 ` rguenth at gcc dot gnu.org

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-60261-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).