From: Stephen Hemminger <shemminger@vyatta.com>
To: "Diego Elio Pettenò" <flameeyes@gmail.com>
Cc: netdev@vger.kernel.org, Daniel Kurtz <djkurtz@google.com>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH] Link directly to the archive files rather than using search paths.
Date: Thu, 9 Dec 2010 17:56:44 -0800 [thread overview]
Message-ID: <20101209175644.00feca1d@nehalam> (raw)
In-Reply-To: <1291942572-12653-1-git-send-email-flameeyes@gmail.com>
On Fri, 10 Dec 2010 01:56:12 +0100
Diego Elio Pettenò <flameeyes@gmail.com> wrote:
> While the previous code was supposed to work nonetheless, it could be
> messed up if further -L were used in LDFLAGS to list the path where glibc's
> libutil was to be found.
>
> References: https://bugs.gentoo.org/347489
>
> CC: Daniel Kurtz <djkurtz@google.com>
> CC: Mike Frysinger <vapier@gentoo.org>
> Signed-off-by: Diego Elio Pettenò <flameeyes@gmail.com>
> ---
> Makefile | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index c03d74c..d1ace1f 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -33,11 +33,10 @@ CCOPTS = -D_GNU_SOURCE -O2 -Wstrict-prototypes -Wall
> CFLAGS = $(CCOPTS) -I../include $(DEFINES)
> YACCFLAGS = -d -t -v
>
> -LDLIBS += -L../lib -lnetlink -lutil
> -
> SUBDIRS=lib ip tc misc netem genl
>
> LIBNETLINK=../lib/libnetlink.a ../lib/libutil.a
> +LDLIBS += $(LIBNETLINK)
>
> all: Config
> @set -e; \
Please be more clear in your subject, yes I can tell this is for
iproute utilities but others may not.
When refering to "previous code" either reply to the original
message thread or provide a link to the changes.
--
next prev parent reply other threads:[~2010-12-10 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 0:56 [PATCH] Link directly to the archive files rather than using search paths Diego Elio Pettenò
2010-12-10 1:56 ` Stephen Hemminger [this message]
2010-12-10 2:02 ` Diego Elio Pettenò
2010-12-10 4:03 ` Stephen Hemminger
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=20101209175644.00feca1d@nehalam \
--to=shemminger@vyatta.com \
--cc=djkurtz@google.com \
--cc=flameeyes@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vapier@gentoo.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