public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libgcj/6068: libgcj build picks up libgcj.spec from install tree
Date: Wed, 27 Mar 2002 19:06:00 -0000	[thread overview]
Message-ID: <20020328030600.27382.qmail@sources.redhat.com> (raw)

The following reply was made to PR libgcj/6068; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: gcc-bugs@gcc.gnu.org
Cc: tromey@redhat.com, gcc-gnats@gcc.gnu.org
Subject: Re: libgcj/6068: libgcj build picks up libgcj.spec from install tree
Date: 27 Mar 2002 20:32:54 -0700

 Tom>     I couldn't reproduce this.  I'm waiting for more information
 Tom>     from Anthony.
 
 The problem can be seen easily with an xscale-elf target.
 The definition of CXX in libjava/Makefile has many more -B and -L
 options than does the definition of GCJ.
 
 Tom


             reply	other threads:[~2002-03-28  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 19:06 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08 11:58 tromey
2002-03-27 15:14 tromey
2002-03-26 15:06 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=20020328030600.27382.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).