linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Steve Dickson <SteveD@redhat.com>,
	linux-nfs@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [nfs-utils RESENT PATCH 1/1] locktes/rpcgen: tweak how we override compiler settings
Date: Mon, 20 Jan 2020 09:48:20 +0100	[thread overview]
Message-ID: <20200120084820.GB31890@dell5510> (raw)
In-Reply-To: <5149cf4e-7d78-2cbd-99e4-a4cb66822308@benettiengineering.com>

Hi Giulio, Steve,

> > Note... Giulio's patch is doing something similar
> > https://lore.kernel.org/linux-nfs/20200115160806.99991-1-giulio.benetti@benettiengineering.com/T/#u

> > Does something like that as well as setting the AM_XXX help the your cross-compile?

> IMHO tools/* utility must be built with cross-compiler too, not with
> /usr/bin/gcc. Buildroot provide host-nfs-utils for that, especially for
> rpcgen.

> Please take a look at my WIP patch for bumping nfs-utils to latest in
> Buildroot:
> https://github.com/giuliobenetti/buildroot/commit/12671eb21d62a5474dc476381015069382775668

> and please note this line:
> --with-rpcgen=$(HOST_DIR)/bin/rpcgen

> that means that nfs-utils must use already host-nfs-utils/rpcgen instead of
> internal one to generate rpcs. This is why tools/* is not needed as host to
> build target. Indeed host-nfs-utils is built when nfs-utils is built. At
> least I understand this.

> Can you Petr confirm that?
> Because at this point the patch you're pointing is not needed.

Sorry, I overlooked this mail. Ack, it's correct for buildroot, as I already
wrote yesterday.
But not sure if the patch isn't needed for Gentoo packaging.
I guess if needed, it still can be rebased and applied later.

Kind regards,
Petr

      reply	other threads:[~2020-01-20  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05 12:05 [nfs-utils RESENT PATCH 1/1] locktes/rpcgen: tweak how we override compiler settings Petr Vorel
2020-01-07 19:20 ` Steve Dickson
2020-01-07 19:38   ` Steve Dickson
2020-01-14 18:36     ` Petr Vorel
2020-01-16 21:22       ` Steve Dickson
2020-01-16 21:34         ` Giulio Benetti
2020-01-20  8:48           ` Petr Vorel [this message]

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=20200120084820.GB31890@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).