From: Joel Brobecker <brobecker@adacore.com>
To: Harald Koenig <H.Koenig@science-computing.de>
Cc: Pedro Alves <pedro@codesourcery.com>,
bug-gdb@gnu.org, gdb-patches@sourceware.org,
Harald Koenig <koenig@science-computing.de>
Subject: Re: some compile errors fo gdb-7.0.1
Date: Mon, 01 Mar 2010 06:51:00 -0000 [thread overview]
Message-ID: <20100301065110.GC2832@adacore.com> (raw)
In-Reply-To: <20100223163505.GA21619@atuin.science-computing.de>
> one more small patch for AIX in config/mh-ppc-aix in case $CC includes
> spaces. for some reason in older gdb version we needed CC='gcc
> -isystem /usr/include' shows that quoting problem. will test if this
> still is needed (read: what's the real problem and a better fix, iff
> still needed at alll).
Your patch looks reasonable to me, but it is not relevant to GDB
specifically. You need to send it to gcc-patches.
> Index: mh-ppc-aix
> ===================================================================
> RCS file: /cvs/src/src/config/mh-ppc-aix,v
> retrieving revision 1.3
> diff -u -r1.3 mh-ppc-aix
> --- mh-ppc-aix 16 Aug 2009 12:49:48 -0000 1.3
> +++ mh-ppc-aix 23 Feb 2010 16:31:34 -0000
> @@ -5,4 +5,4 @@
> # don't do it any more.
> BOOT_ADAFLAGS = -gnatapg
> BOOT_LDFLAGS = -Wl,-bbigtoc
> -LDFLAGS = `case $(CC) in *gcc*) echo -Wl,-bbigtoc ;; esac;`
> +LDFLAGS = `case "$(CC)" in *gcc*) echo -Wl,-bbigtoc ;; esac;`
--
Joel
prev parent reply other threads:[~2010-03-01 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100215141621.GA9469@atuin.science-computing.de>
2010-02-18 19:23 ` Pedro Alves
2010-02-23 15:22 ` Harald Koenig
2010-02-23 17:08 ` Pedro Alves
2010-02-23 16:35 ` Harald Koenig
2010-02-23 17:14 ` Harald Koenig
2010-02-24 12:51 ` Harald Koenig
2010-02-24 13:35 ` Build errors on AIX Pedro Alves
2010-02-24 14:09 ` Harald Koenig
2010-03-01 6:47 ` Joel Brobecker
2010-03-01 6:51 ` Joel Brobecker [this message]
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=20100301065110.GC2832@adacore.com \
--to=brobecker@adacore.com \
--cc=H.Koenig@science-computing.de \
--cc=bug-gdb@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=koenig@science-computing.de \
--cc=pedro@codesourcery.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