From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Steve Dickson <SteveD@RedHat.com>, linux-nfs@vger.kernel.org
Subject: Re: [nfs-utils PATCH] locktest: Makefile.am: remove host compiler costraint
Date: Wed, 22 Jan 2020 19:11:01 +0100 [thread overview]
Message-ID: <92111fa0-a808-84da-19b8-823ad6a26a99@benettiengineering.com> (raw)
In-Reply-To: <ae36c91f-bed4-3839-bdd5-fffdcca9bf40@RedHat.com>
Hi Steve,
On 1/22/20 6:56 PM, Steve Dickson wrote:
>
>
> On 1/15/20 11:08 AM, Giulio Benetti wrote:
>> Currently locktest can be built only for host because CC_FOR_BUILD is
>> specified as CC, but this leads to build failure when passing CFLAGS not
>> available on host gcc(i.e. -mlongcalls) and most of all locktest would
>> be available on target systems the same way as rpcgen etc. So remove CC
>> and LIBTOOL assignments.
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Committed... (tag: nfs-utils-2-4-3-rc6)
I've just setup up a Gentoo to try building nfs-utils, I give a try
anyway by now, so we should be sure.
Best regards
--
Giulio Benetti
Benetti Engineering sas
> steved.
>> ---
>> tools/locktest/Makefile.am | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/tools/locktest/Makefile.am b/tools/locktest/Makefile.am
>> index 3156815d..e8914655 100644
>> --- a/tools/locktest/Makefile.am
>> +++ b/tools/locktest/Makefile.am
>> @@ -1,8 +1,5 @@
>> ## Process this file with automake to produce Makefile.in
>>
>> -CC=$(CC_FOR_BUILD)
>> -LIBTOOL = @LIBTOOL@ --tag=CC
>> -
>> noinst_PROGRAMS = testlk
>> testlk_SOURCES = testlk.c
>> testlk_CFLAGS=$(CFLAGS_FOR_BUILD)
>>
>
next prev parent reply other threads:[~2020-01-22 18:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 16:08 [nfs-utils PATCH] locktest: Makefile.am: remove host compiler costraint Giulio Benetti
2020-01-19 19:10 ` Petr Vorel
2020-01-22 15:24 ` Steve Dickson
2020-01-22 16:13 ` Petr Vorel
2020-01-22 16:44 ` Steve Dickson
2020-01-22 17:56 ` Steve Dickson
2020-01-22 18:11 ` Giulio Benetti [this message]
2020-01-22 18:54 ` Giulio Benetti
2020-01-22 19:30 ` Steve Dickson
2020-01-22 21:55 ` Giulio Benetti
2020-01-27 18:41 ` Steve Dickson
2020-01-27 18:58 ` Giulio Benetti
2020-01-27 19:03 ` Steve Dickson
2020-01-27 19:51 ` Giulio Benetti
2020-02-07 12:33 ` Giulio Benetti
2020-02-07 15:45 ` Steve Dickson
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=92111fa0-a808-84da-19b8-823ad6a26a99@benettiengineering.com \
--to=giulio.benetti@benettiengineering.com \
--cc=SteveD@RedHat.com \
--cc=linux-nfs@vger.kernel.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