public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: tromey@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/4804 Date: Fri, 02 Nov 2001 14:23:00 -0000 [thread overview] Message-ID: <20011114182603.17575.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR java/4804; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: 520036556988-0001@t-online.de (Georg Wild) Cc: "Jeff Sturm" <jsturm@one-point.com>, <gcc-gnats@gcc.gnu.org>, <georg.wild@gmx.de>, <gcc-bugs@gcc.gnu.org> Subject: Re: java/4804 Date: 14 Nov 2001 11:42:07 -0700 >>>>> "Georg" == Georg Wild <520036556988-0001@t-online.de> writes: Georg> cd . && automake --gnu --include-deps Makefile Georg> automake: configure.in: required file `./depcomp' not found You shouldn't be re-running automake unless you have the correct version installed. Did you get gcc from cvs? If so then you should use the `contrib/gcc_update' script and not `cvs update'. If you got gcc from a snapshot or something then we have a different problem. Georg> As far as I see at the moment, the problem 4804 is produced by Georg> line 3965 of /ltmain.sh No, EXEEXT will be computed in configure, not ltmain.sh. Georg> *) exeext= ;; Georg> I think somehow this exeext= ;; doesn't work correctly Nope, this code is correct. Georg> /windows/gcc/fastjar/missing: Unknown `--run' option Your depcomp problem and this problem are symptoms of using the wrong version of automake. Tom
next reply other threads:[~2001-11-14 18:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-02 14:23 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-13 15:16 java/4804 Tom Tromey 2001-11-03 11:36 java/4804 Jeff Sturm 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=20011114182603.17575.qmail@sourceware.cygnus.com \ --to=tromey@redhat.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).