From: Petr Vorel <petr.vorel@gmail.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-nfs@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [nfs-utils PATCH] locktest: Makefile.am: remove host compiler costraint
Date: Wed, 22 Jan 2020 17:13:53 +0100 [thread overview]
Message-ID: <20200122161353.GA21075@dell5510> (raw)
In-Reply-To: <6606c604-61ef-a3fa-8ced-1d9dfb822f64@RedHat.com>
Hi Steve,
> >> 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>
> > Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
> > Tested-by: Petr Vorel <petr.vorel@gmail.com>
> > NOTE: as I understand it's a compilation issue of a tool, so I didn't run
> > rpcgen, I just test various compilation variants for buildroot.
> Just to be clear... Giulio's patch, removing CC and LIBTOOL from the
> locktest/Makefile.am does allows your cross build to succeed, correct?
Yes, for buildroot it's ok. I'm just not able to verify Gentoo.
> steved.
Kind regards,
Petr
next prev parent reply other threads:[~2020-01-22 16:13 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 [this message]
2020-01-22 16:44 ` Steve Dickson
2020-01-22 17:56 ` Steve Dickson
2020-01-22 18:11 ` Giulio Benetti
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=20200122161353.GA21075@dell5510 \
--to=petr.vorel@gmail.com \
--cc=SteveD@redhat.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@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 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.