public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/4776
Date: Fri, 02 Nov 2001 07:23:00 -0000 [thread overview]
Message-ID: <20011113204602.3839.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR java/4776; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: Craig Rodrigues <rodrigc@mediaone.net>
Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, rodrigc@gcc.gnu.org,
george.goffe@seagate.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
java-prs@gcc.gnu.org
Subject: Re: java/4776
Date: 13 Nov 2001 14:03:52 -0700
>>>>> "Craig" == Craig Rodrigues <rodrigc@mediaone.net> writes:
Craig> PR 4776 looks a lot like PR 2812. You submitted a patch
Craig> which looks like it should have solved it, but according to this
Craig> PR, it is still a problem in gcc 3.0.2.
Craig> Any ideas?
I can't explain it. The patch is definitely there, and I believe it
was tested by a net user before it was committed.
Maybe a look at config.log would help.
It sounds like the gcc build is picking up the libiconv header file
but for some reason it isn't seeing the libiconv library.
Tom
next reply other threads:[~2001-11-13 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 7:23 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 23:56 java/4776 Craig Rodrigues
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=20011113204602.3839.qmail@sourceware.cygnus.com \
--to=tromey@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).