public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com> To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/4804 Date: Sat, 03 Nov 2001 11:36:00 -0000 [thread overview] Message-ID: <20011114231602.18360.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR java/4804; it has been noted by GNATS. From: Jeff Sturm <jsturm@one-point.com> To: Tom Tromey <tromey@redhat.com> Cc: gcc-gnats@gcc.gnu.org, georg.wild@gmx.de, gcc-bugs@gcc.gnu.org Subject: Re: java/4804 Date: Wed, 14 Nov 2001 19:21:20 -0500 (EST) On 14 Nov 2001, Tom Tromey wrote: > >>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes: > > Jeff> I saw this too. In my case I have autoconf 2.50 installed. > Jeff> jar/Makefile has > > Jeff> EXEEXT = no > > An interesting failure! > > Did you re-run autoconf? If so then that is the problem. Use the > `contrib/gcc_update' script to do updates and you'll be ok. I think that's just what happened. Anyway, the configure script generated by autoconf 2.50 is broken... the first time through it writes ac_cv_exeext=no to the cache file. The next time, it takes the value "no" verbatim from cache. I'll report it to the autoconf folks. Shall we close this PR? Jeff
next reply other threads:[~2001-11-14 23:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-03 11:36 Jeff Sturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-13 15:16 java/4804 Tom Tromey 2001-11-02 14:23 java/4804 Tom Tromey 2001-11-02 12:36 java/4804 Tom Tromey 2001-11-02 12:16 java/4804 Georg Wild 2001-11-02 8:19 java/4804 Jeff Sturm
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=20011114231602.18360.qmail@sourceware.cygnus.com \ --to=jsturm@one-point.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: linkBe 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).