public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/9431: configure generates invalid makefile on HP-UX system
Date: Wed, 07 May 2003 08:56:00 -0000 [thread overview]
Message-ID: <20030507085600.13592.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/9431; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, William.L.Kleb@NASA.Gov,
nobody@gcc.gnu.org
Cc:
Subject: Re: other/9431: configure generates invalid makefile on HP-UX system
Date: Wed, 7 May 2003 01:50:50 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=9431
Hello,
could the submitter please be more clear about what is invalid about
the generated makefile? How does it fail? With what version of make?
Note that gcc does not officially support any makes aside from GNU
make. Thanks,
Dara
next reply other threads:[~2003-05-07 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 8:56 Dara Hazeghi [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-10 7:42 giovannibajo
2003-05-09 17:26 Bil Kleb
2003-05-07 10:18 giovannibajo
2003-01-24 10:16 William.L.Kleb
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=20030507085600.13592.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.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).