public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnstar9988 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32785] (hpux11.11)link test not allowed GCC_NO_EXECUTABLES.
Date: Tue, 17 Jul 2007 03:26:00 -0000 [thread overview]
Message-ID: <20070717032648.4050.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32785-14862@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from cnstar9988 at gmail dot com 2007-07-17 03:26 -------
Subject: Re: (hpux11.11)link test not allowed GCC_NO_EXECUTABLES.
Bug 25035
Bug 28125
Bug 28949
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28949
----- Original Message -----
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: <cnstar9988@gmail.com>
Sent: Tuesday, July 17, 2007 11:19 AM
Subject: [Bug target/32785] (hpux11.11)link test not allowed
GCC_NO_EXECUTABLES.
>
>
> ------- Comment #3 from pinskia at gcc dot gnu dot org 2007-07-17
> 03:19 -------
> Can you read config.log and see why it is failing?
>
>
> --
>
> pinskia at gcc dot gnu dot org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Severity|critical |normal
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32785
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
------- Comment #5 from cnstar9988 at gmail dot com 2007-07-17 03:26 -------
Created an attachment (id=13927)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13927&action=view)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32785
next prev parent reply other threads:[~2007-07-17 3:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 2:18 [Bug target/32785] New: link " cnstar9988 at gmail dot com
2007-07-17 2:35 ` [Bug target/32785] " cnstar9988 at gmail dot com
2007-07-17 3:12 ` [Bug target/32785] (hpux11.11)link " cnstar9988 at gmail dot com
2007-07-17 3:19 ` pinskia at gcc dot gnu dot org
2007-07-17 3:26 ` cnstar9988 at gmail dot com [this message]
2007-07-17 3:29 ` cnstar9988 at gmail dot com
2007-07-17 4:11 ` pinskia at gcc dot gnu dot org
2007-07-17 4:55 ` cnstar9988 at gmail dot com
2007-07-17 4:57 ` cnstar9988 at gmail dot com
2007-07-17 5:09 ` cnstar9988 at gmail dot com
2007-07-17 6:06 ` cnstar9988 at gmail dot com
2007-07-17 6:36 ` [Bug bootstrap/32785] " pinskia at gcc dot gnu dot org
2007-07-17 6:43 ` cnstar9988 at gmail dot com
2007-07-17 9:53 ` rask at sygehus dot dk
2007-07-17 9:56 ` cnstar9988 at gmail dot com
2007-07-17 10:04 ` cnstar9988 at gmail dot com
2007-07-17 10:30 ` cnstar9988 at gmail dot com
2007-07-18 2:26 ` cnstar9988 at gmail dot com
2007-07-18 6:49 ` cnstar9988 at gmail dot com
2007-07-19 7:17 ` cnstar9988 at gmail dot com
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=20070717032648.4050.qmail@sourceware.org \
--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).