public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5196: make fail: Must be a separator on rules line 654. (HP Itanium System, HP-UX 11.20)
Date: Sun, 06 Jan 2002 09:06:00 -0000 [thread overview]
Message-ID: <20020106170602.27356.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/5196; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: rodrigc@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, rdailey@usgs.gov, gcc-gnats@gcc.gnu.org,
rodrigc@gcc.gnu.org
Subject: Re: java/5196: make fail: Must be a separator on rules line 654. (HP Itanium System, HP-UX 11.20)
Date: 06 Jan 2002 10:15:06 -0700
>>>>> "Craig" == rodrigc <rodrigc@gcc.gnu.org> writes:
> Synopsis: make fail: Must be a separator on rules line 654. (HP
> Itanium System, HP-UX 11.20)
Craig> The makefile error you got was in the fastjar directory.
Craig> This is not a critical part of gcc. If you
Craig> do not want the java compiler, you can
Craig> use the --enable-languages flag to configure to only
Craig> enable the languages you want, see:
Craig> http://gcc.gnu.org/install/configure.html
I'd like to know the problem here.
fastjar uses automake to generate its Makefile.
In theory such Makefiles are completely portable.
If there is a real problem here, then we've found an automake bug and
I'd like to fix it.
Tom
next reply other threads:[~2002-01-06 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 9:06 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 16:06 neroden
2002-01-04 22:04 rodrigc
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=20020106170602.27356.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).