From: Paul Gilliam <pgilliam@us.ibm.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch] Allow compilation by IBM's xlc compiler
Date: Fri, 01 Apr 2005 23:07:00 -0000 [thread overview]
Message-ID: <200504011503.35642.pgilliam@us.ibm.com> (raw)
In-Reply-To: <20050401224525.GA2344@nevyn.them.org>
On Friday 01 April 2005 14:45, Daniel Jacobowitz wrote:
> On Fri, Apr 01, 2005 at 02:40:16PM -0800, Paul Gilliam wrote:
> >
> >
>
> Several of your mails have been empty - not useful.
Please don't exagerate: it's only 40% 8-)
> Also, they could all do with a little explanation.
I thought the subject was enough, but if you want more detail, I can do that.
Basicly we're just trying to get the testsuite to run with the IBM xlc compiler.
For the most part, it's just renameing the flags: -qmkshrobj for -shared,
-qpic for -fpic and that kind of thing. In one case, xlc was puting out a warning
that gcc doesn't and that had be turned off.
> The patches for -shared are not great. I posted a testcase (several
> months ago, for a patch which is still pending) which moved the
> PIC/shared tests to lib/gdb.exp. One of us should dust off that patch
> if you need to add cases to every one of them.
>
Could you give me a URL to your testsuite patch? I have 6 or so of these so If
you have a better way, I'd love to use it.
Thanks,
-=# Paul #=-
next prev parent reply other threads:[~2005-04-01 23:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 22:43 Paul Gilliam
2005-04-01 22:45 ` Daniel Jacobowitz
2005-04-01 23:07 ` Paul Gilliam [this message]
2005-04-01 23:13 ` Daniel Jacobowitz
2005-04-06 17:52 ` [patch] add testsuite infrastructure to deal with shared libraries Paul Gilliam
2005-04-12 18:25 ` [patch] add testsuite infrastructure to deal with shared libraries (now supports IBM's xlc compiler) Paul Gilliam
2005-04-14 19:07 ` Daniel Jacobowitz
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=200504011503.35642.pgilliam@us.ibm.com \
--to=pgilliam@us.ibm.com \
--cc=gdb-patches@sources.redhat.com \
/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