From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] tools/vtpm: use LDLIBS to pass -lgmp
Date: Tue, 3 Apr 2012 16:07:51 +0200 [thread overview]
Message-ID: <20120403140751.GA4553@aepfle.de> (raw)
In-Reply-To: <20346.63753.211063.200875@mariner.uk.xensource.com>
On Tue, Apr 03, Ian Jackson wrote:
> Olaf Hering writes ("[Xen-devel] [PATCH] tools/vtpm: use LDLIBS to pass -lgmp"):
> > tools/vtpm: use LDLIBS to pass -lgmp
> >
> > Linking tpmd will fail with recent toolchains because -lgmp is passed
> > via LDFLAGS instead of LDLIBS. With this change -lgpm is placed at the
> > end of the gcc cmdline and linking tpmd succeeds again.
> ...
> > CFLAGS += $(WFLAGS) -g -I.. -I. -O2 -fno-strict-aliasing
> > +CFLAGS += -I../../../../tools/vtpm_manager/manager
> > - LDFLAGS += -lgmp
> > + LDLIBS += -lgmp
> >
> > -BINDIR := /usr/sbin/
> > +BINDIR := /usr/bin/
>
> Please could you make sure not to include unrelated changes in your
> patches. That makes the job of the reviewer /much/ harder, because we
> would have to inspect every hunk of your patches looking for this kind
> of thing creeping in.
This patch changes a patch file for vtpm which has LDFLAGS in the
context around the changed lines.
See the space between the '-' and LDFLAGS.
Olaf
next prev parent reply other threads:[~2012-04-03 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 9:14 [PATCH] tools/vtpm: use LDLIBS to pass -lgmp Olaf Hering
2012-04-03 13:20 ` Ian Jackson
2012-04-03 14:07 ` Olaf Hering [this message]
2012-04-03 14:10 ` Ian Jackson
2012-04-03 14:18 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2012-05-04 17:43 Olaf Hering
2012-05-10 16:36 ` Ian Jackson
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=20120403140751.GA4553@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.