public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "warrend@mdhost.cse.tek.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/10657] [3.3 regression] java section can not find libiconv
Date: Wed, 11 Jun 2003 23:23:00 -0000	[thread overview]
Message-ID: <20030611232324.7199.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030507051600.10657.warren.dodge@tek.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From warrend@mdhost.cse.tek.com  2003-06-11 23:23 -------
Subject: Re:  [3.3 regression] java section can not find libiconv


As far as I know this was not fixed. I tried building gcc-3.3-20030508 and
had the problem. I haven't touched it since then.

I also submitted another enhancement request that would solve this
problem. It was to allow us to specify a "library/include directory" which
would be pushed down through the process of making gcc and become part of
the "specs" file also.

This would be similar to the libiconv switch but more general.


  parent reply	other threads:[~2003-06-11 23:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030507051600.10657.warren.dodge@tek.com>
2003-06-08  1:44 ` jsturm@gcc.gnu.org
2003-06-11 22:47 ` pinskia@physics.uc.edu
2003-06-11 23:23 ` warrend@mdhost.cse.tek.com [this message]
2003-07-12  3:19 ` neroden at gcc dot gnu dot org
2003-07-13 16:17 ` jsturm at gcc dot gnu dot org
2003-10-24 20:40 ` neroden at gcc dot gnu dot org
2003-10-24 20:41 ` neroden at gcc dot gnu dot org
2003-11-19 23:25 ` pinskia at gcc dot gnu dot org
2003-11-20  0:20 ` warrend at mdhost dot cse dot tek dot com
2003-11-20  0:31 ` pinskia at gcc dot gnu dot org
2003-11-20  3:29 ` jsturm at gcc dot gnu dot org
2003-11-28  8:40 ` pinskia at gcc dot gnu dot org
2004-01-14  4:45 ` [Bug bootstrap/10657] " pinskia at gcc dot gnu dot org
2004-12-05 17:02 ` [Bug java/10657] " pinskia at gcc dot gnu dot 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=20030611232324.7199.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).