From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC 1/2] link gdbserver against libiberty
Date: Tue, 21 Jan 2014 01:49:00 -0000 [thread overview]
Message-ID: <52DDD1BA.7050202@codesourcery.com> (raw)
In-Reply-To: <1390243792-31176-2-git-send-email-tromey@redhat.com>
On 01/21/2014 02:49 AM, Tom Tromey wrote:
> 2014-01-20 Tom Tromey <tromey@redhat.com>
>
> * Makefile.in (LIBIBERTY_BUILDDIR, LIBIBERTY): New variables.
> (SUBDIRS, REQUIRED_SUBDIRS): Add libiberty.
> (FLAGS_TO_PASS): Remove AR, AR_FLAGS
period is missing ...
>
> FLAGS_TO_PASS = \
> "prefix=$(prefix)" \
> @@ -213,8 +216,6 @@ FLAGS_TO_PASS = \
> "includedir=$(includedir)" \
> "against=$(against)" \
> "DESTDIR=$(DESTDIR)" \
> - "AR=$(AR)" \
> - "AR_FLAGS=$(AR_FLAGS)" \
> "CC=$(CC)" \
> "CFLAGS=$(CFLAGS)" \
> "CXX=$(CXX)" \
... and I don't understand why do we remove AR and AR_FLAGS from
FLAGS_TO_PASS.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-01-21 1:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 18:49 [RFC 0/2] let gdbserver use libiberty Tom Tromey
2014-01-20 18:49 ` [RFC 2/2] delete gdbserver's freeargv Tom Tromey
2014-02-07 16:35 ` Pedro Alves
2014-01-20 18:49 ` [RFC 1/2] link gdbserver against libiberty Tom Tromey
2014-01-21 1:49 ` Yao Qi [this message]
2014-01-21 2:33 ` Tom Tromey
2014-02-07 14:49 ` Tom Tromey
2014-02-07 16:32 ` Pedro Alves
2014-02-07 21:00 ` Tom Tromey
2014-02-10 13:27 ` Pedro Alves
2014-02-12 16:44 ` Tom Tromey
2014-02-12 16:49 ` Pedro Alves
2014-02-08 2:36 ` Yao Qi
2014-01-21 2:03 ` Yao Qi
2014-01-20 18:54 ` [RFC 0/2] let gdbserver use libiberty Tom Tromey
2014-06-12 20:37 ` Tom Tromey
2014-06-16 13:26 ` James Greenhalgh
2014-06-18 12:27 ` Marcus Shawcroft
2014-06-19 14:48 ` Tom Tromey
2014-06-20 10:52 ` Pedro Alves
2014-06-20 12:01 ` Gary Benson
2014-06-20 14:16 ` Tom Tromey
2014-06-20 14:44 ` [COMMITTED PATCH] Fix mingw32 build on x86-64 RHEL 6.5 Gary Benson
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=52DDD1BA.7050202@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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