public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/47484] New: [4.4/4.5/4.6 regression] share/python/aotcompile.py and share/python/classfile.py pollute common namespace
Date: Thu, 27 Jan 2011 01:47:00 -0000	[thread overview]
Message-ID: <bug-47484-8172@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.4/4.5/4.6 regression] share/python/aotcompile.py
                    and share/python/classfile.py pollute common namespace
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gerald@pfeifer.com
                CC: aph@redhat.com
            Blocks: 346


share/python/aotcompile.py and share/python/classfile.py pollute common
namespace; cf. Bug #346.

This has been introduced by the following patch:

2008-06-30  Joshua Sumali  <jsumali@redhat.com>
        Andrew Haley  <aph@redhat.com>

        * configure.ac (java-home): new AC_ARG_ENABLE.
        (aot-compile-rpm): Likewise.
        :
        * contrib/aot-compile.in: New file.
        * contrib/aotcompile.py.in: Likewise.
        * contrib/aot-compile-rpm.in: Likewise.
        * contrib/classfile.py: Likewise.
        * contrib/rebuild-gcj-db.in: Likewise.


             reply	other threads:[~2011-01-27  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27  1:47 gerald at pfeifer dot com [this message]
2011-01-27 11:02 ` [Bug libgcj/47484] " rguenth at gcc dot gnu.org
2011-02-08 14:48 ` rguenth at gcc dot gnu.org
2011-02-14 14:28 ` gary at gcc dot gnu.org
2011-04-16 10:20 ` [Bug libgcj/47484] [4.4/4.5 " jakub at gcc dot gnu.org
2011-04-18 14:25 ` 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-47484-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).