public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rwild at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46887] Invalid AIX linker flag '-bnoerok', it has to be '-bernotok'
Date: Mon, 13 Dec 2010 16:47:00 -0000 [thread overview]
Message-ID: <bug-46887-4-ukwnTC66Mp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46887-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46887
Ralf Wildenhues <rwild at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rwild at gcc dot gnu.org
--- Comment #1 from Ralf Wildenhues <rwild at gcc dot gnu.org> 2010-12-13 16:46:54 UTC ---
Does this actually hit you any time? If yes, please post configure command
line, and cut and paste error and command(s) that caused it, and whether the
obvious fix lets the build succeed where it did not before. Thanks.
The ltcf* and ltconfig stuff is so old and outdated, I didn't think it was used
anywhere in the tree any more.
next prev parent reply other threads:[~2010-12-13 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 16:46 [Bug target/46887] New: " michael.haubenwallner at salomon dot at
2010-12-13 16:47 ` rwild at gcc dot gnu.org [this message]
2010-12-13 22:19 ` [Bug target/46887] " michael.haubenwallner at salomon dot at
2011-02-28 17:11 ` dje at gcc dot gnu.org
2011-03-02 5:49 ` rwild at gcc dot gnu.org
2011-12-09 16:03 ` gseanmcg at gmail dot com
2011-12-10 20:38 ` dje at gcc dot gnu.org
2011-12-10 21:05 ` dje at gcc dot gnu.org
2011-12-12 14:33 ` gseanmcg at gmail dot com
2011-12-12 14:41 ` paolo.carlini at oracle dot com
2011-12-12 16:29 ` michael.haubenwallner at salomon dot at
2011-12-12 16:37 ` dje at gcc dot gnu.org
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=bug-46887-4-ukwnTC66Mp@http.gcc.gnu.org/bugzilla/ \
--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).