public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsturm@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jsturm@gcc.gnu.org,
	mark@codesourcery.com, nobody@gcc.gnu.org, warren.dodge@tek.com
Subject: Re: bootstrap/10657: java section can not find ;ibiconv
Date: Thu, 08 May 2003 13:58:00 -0000	[thread overview]
Message-ID: <20030508135823.7197.qmail@sources.redhat.com> (raw)

Synopsis: java section can not find ;ibiconv

Responsible-Changed-From-To: unassigned->jsturm
Responsible-Changed-By: jsturm
Responsible-Changed-When: Thu May  8 13:58:23 2003
Responsible-Changed-Why:
    I'll take it.
State-Changed-From-To: open->analyzed
State-Changed-By: jsturm
State-Changed-When: Thu May  8 13:58:23 2003
State-Changed-Why:
    There are two distinct aspects of this PR:
    - why does the bootstrap fail
    - why does jc1 need iconv when configured with --disable-nls
    
    The first is a consequence of bootstrapping from a gcc compiler coninstalled with GNU libiconv.  I don't know how to fix it easily, since configuration and libiconv detection is performed with the bootstrap compiler, not the stage1 compiler.  Nevertheless the problem should be documented.
    
    For the second, it's debateable whether jc1 should try to use -liconv in this case.  The Java language requires Unicode support.  One option is to not build the java frontend at all with --disable-nls.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10657


             reply	other threads:[~2003-05-08 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 13:58 jsturm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08 10:06 Christian Ehrhardt
2003-05-07 22:56 Jeff Sturm
2003-05-07 13:56 Christian Ehrhardt
2003-05-07  5:16 warren.dodge

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=20030508135823.7197.qmail@sources.redhat.com \
    --to=jsturm@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=nobody@gcc.gnu.org \
    --cc=warren.dodge@tek.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).