all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org, Christopher Lemmer Webber <cwebber@dustycloud.org>
Subject: Re: Compiling a linux kernel from git
Date: Sun, 07 Jul 2019 01:41:45 +0200	[thread overview]
Message-ID: <87pnmmd93a.fsf@nckx> (raw)
In-Reply-To: <877e8v5ezu.fsf@dustycloud.org>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

Chris,
 
Christopher Lemmer Webber wrote: 
> Anyone more familiar with the linux build process who can give 
> me some tips?  Especially since I board a plane very early 
> tomorrow morning :) 

My own kernel package has nothing left in common with linux-libre, 
but it does build from git and has this phase + comment which I'd 
hoped
would never see the light of day:

  (add-before 'configure 'fix-CPATH 
    (lambda _ 
      ;; Temporary hack to remove -checkout/include which breaks 
      things.  ;; Why is this not necessary when building in a 
      ‘guix environment’ ;; and in the Guix linux-libre package? 
      Git-checkout-related?  (setenv "CPATH" (string-join 
                       (cdr (string-split (getenv "CPATH") #\:)) 
                       ":")) 
      #t))

I'd remove it to see what happens, but that would be tomorrow and 
you appear to be in something of a hurry. 

Good luck!

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-07-06 23:41 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
2019-07-07 23:30       ` Mark H Weaver
2019-07-06 23:41 ` Tobias Geerinckx-Rice [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnmmd93a.fsf@nckx \
    --to=me@tobias.gr \
    --cc=cwebber@dustycloud.org \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.