From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Mark H Weaver <mhw@netris.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Compiling a linux kernel from git
Date: Sun, 07 Jul 2019 03:00:21 -0400 [thread overview]
Message-ID: <87y31acosa.fsf@dustycloud.org> (raw)
In-Reply-To: <87h87y8pk6.fsf@netris.org>
Mark H Weaver writes:
> Hi Chris,
>
> I wrote earlier:
>> My first guess is that '/gnu/store/…-linux-next-…-checkout/include'
>> should not be in the C include path while compiling that file, but that
>> it's getting added. The difference might be due to the fact that the
>> 'source' in this case is a directory instead of a tarball.
>
> I see now what's happening more precisely. Our gcc-7 package inherits
> from gcc-6 'native-search-paths' for the CPATH variable. Because of
> this, the 'set-paths' phase in 'gnu-build-system' sets the CPATH to
> include <NATIVE_INPUT>/include for all native inputs that are
> directories with an 'include' subdirectory.
>
> The 'source' is itself a native input. When it's a tarball, it will not
> be included, but when it's a source checkout, it _is_ included, although
> it shouldn't be.
Oh, that's quite curious.
>> For now, I would try packing the git checkout as a tarball, and then
>> using that tarball as your 'source'.
>
> I'm now fairly confident that this workaround would work. Another
> workaround would be to add another phase that removes the CPATH
> component corresponding to 'source', as Tobias does.
>
> Mark
Thanks! I got things working by going the tarball route, though
slightly more indirectly than the approach you suggested here. What I
did was get the latest release-candidate tarball and list the patches I
specifically needed in the package definition. Happily this worked!
Happy to say I'm on my way to the conference with a functioning laptop.
next prev parent reply other threads:[~2019-07-07 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 16:01 Compiling a linux kernel from git Christopher Lemmer Webber
2019-07-06 22:21 ` Mark H Weaver
2019-07-07 3:57 ` Mark H Weaver
2019-07-07 7:00 ` Christopher Lemmer Webber [this message]
2019-07-07 23:30 ` Mark H Weaver
2019-07-06 23:41 ` Tobias Geerinckx-Rice
2019-07-06 23:49 ` Tobias Geerinckx-Rice
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y31acosa.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).