public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@klose.in-berlin.de>
To: gcc-gnats@gcc.gnu.org
Cc: Tom Tromey <tromey@redhat.com>, Anthony Green <green@redhat.com>
Subject: libgcj/5984: inclusion of libgcj-version in jar filename (libgcjX.jar)
Date: Sun, 17 Mar 2002 04:56:00 -0000	[thread overview]
Message-ID: <E16mZtI-0000UJ-00@gate.local> (raw)


>Number:         5984
>Category:       libgcj
>Synopsis:       inclusion of libgcj-version in jar filename (libgcjX.jar)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 17 04:56:10 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Matthias Klose
>Release:        3.1 CVS
>Organization:
Debian
>Environment:
System: Linux
Architecture: i686
	
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc i386-linux
>Description:

When installing more than one gcc/gcj version under the same prefix, the
runtime environment of these two versions should not conflict. In the thread
starting at

	http://gcc.gnu.org/ml/java/2002-01/msg00151.html

it was argued, that libgcj.jar belongs to the runtime environment.

	
>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-03-17 12:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17  4:56 Matthias Klose [this message]
2002-04-30 12:44 tromey

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=E16mZtI-0000UJ-00@gate.local \
    --to=doko@klose.in-berlin.de \
    --cc=doko@cs.tu-berlin.de \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=green@redhat.com \
    --cc=tromey@redhat.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).