public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/8745] AIX 5.1 xlc compilation problems
Date: Thu, 18 Oct 2012 16:16:00 -0000 [thread overview]
Message-ID: <bug-8745-4717-ryv0XprdtZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-8745-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=8745
brobecker at gnat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brobecker at gnat dot com
--- Comment #4 from brobecker at gnat dot com 2012-10-18 16:16:16 UTC ---
Looking at the files involved, it looks like it should be redispatched to gcc
(libiberty) and bfd, no?
Stuart: There aren't many people with access to an AIX system, and even those
who do may not have access to xlc. All I know is that I am able to build GDB on
AIX when using GCC as the compiler. Can you try using GCC instead?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-10-18 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8745-4717@http.sourceware.org/bugzilla/>
2011-11-18 15:57 ` tromey at redhat dot com
2011-11-18 21:07 ` stuart_kemp at hotmail dot com
2011-11-18 21:28 ` tromey at redhat dot com
2012-10-18 16:16 ` brobecker at gnat dot com [this message]
2012-10-18 16:32 ` palves at redhat dot com
2012-10-18 20:19 ` stuart_kemp at hotmail dot com
2012-10-18 20:28 ` brobecker at gnat dot com
2014-02-16 19:31 ` jackie.rosen at hushmail dot com
2014-05-28 19:40 ` schwab at sourceware dot org
[not found] <20040511144800.8745.stuart_kemp@hotmail.com>
2009-08-07 0:08 ` tromey at redhat 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=bug-8745-4717-ryv0XprdtZ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).