public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbuck at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/15093] make bootstrap fails to configure libffi
Date: Tue, 27 Apr 2004 00:48:00 -0000	[thread overview]
Message-ID: <20040427003937.26890.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040423104405.15093.olle@cb.uu.se>


------- Additional Comments From jbuck at gcc dot gnu dot org  2004-04-27 00:39 -------
The suggestion to recommend a CONFIG_SHELL of bash is the wrong fix; this just
hides the bug.  Jim Wilson pointed out the real problem in

http://gcc.gnu.org/ml/gcc/2004-04/msg01227.html

There is a proposed patch at

http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01754.html

That's for the 3.4 branch.  I have verified that it works on Compaq Tru64.
For the trunk, the corresponding change to

libffi/configure.ac

should be made.


-- 


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


  parent reply	other threads:[~2004-04-27  0:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 10:51 [Bug bootstrap/15093] New: " olle at cb dot uu dot se
2004-04-23 10:54 ` [Bug bootstrap/15093] " olle at cb dot uu dot se
2004-04-23 12:10 ` pinskia at gcc dot gnu dot org
2004-04-23 15:50 ` olle at cb dot uu dot se
2004-04-23 15:59 ` [Bug libgcj/15093] " pinskia at gcc dot gnu dot org
2004-04-24 13:55 ` pinskia at gcc dot gnu dot org
2004-04-27  0:48 ` jbuck at gcc dot gnu dot org [this message]
2004-04-27  6:21 ` cvs-commit at gcc dot gnu dot org
2004-04-27  6:26 ` cvs-commit at gcc dot gnu dot org
2004-04-27 11:35 ` pinskia at gcc dot gnu dot org
2004-04-30  0:54 ` pinskia at gcc dot gnu dot org
2004-04-30  0:58 ` pinskia at gcc dot gnu dot org
2004-05-06 12:43 ` pinskia at gcc dot gnu dot org
2004-05-15 18:10 ` pinskia at gcc dot gnu dot org
2004-05-26 14:00 ` bangerth at dealii dot org
2004-06-22 16:47 ` pinskia at gcc dot gnu dot org
2004-06-26  4:15 ` 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=20040427003937.26890.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).