unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mitchell Schmeisser <mitchellschmeisser@librem.one>
Cc: 61698-done@debbugs.gnu.org
Subject: bug#61698: Incorrect Native *_PATH's when linux source is not a tarball.
Date: Thu, 02 Mar 2023 16:23:16 -0500	[thread overview]
Message-ID: <87jzzyetkr.fsf@gmail.com> (raw)
In-Reply-To: <rgtcr2ilfuycg9.fsf@arl.psu.edu> (Mitchell Schmeisser's message of "Tue, 21 Feb 2023 15:45:42 -0500")

Hello Mitchell,

Mitchell Schmeisser <mitchellschmeisser@librem.one> writes:

> This is a bit of a convoluted bug but here it goes. The title may not be
> entirely correct.
>
> When ~set-paths~ is called it adds all of the inputs to ~C_INCLUDE_PATH~
> and friends /except/ the source input.
>
> #+BEGIN_SRC scheme
> (define-public linux-zynq
>   (customize-linux #:name "linux-zynq"
> 		   #:linux linux-libre-5.15
> 		   #:source (package-source linux-xlnx-5.15.0)
> 		   #:defconfig "xilinx_zynq_defconfig"))
> #+END_SRC
>
> However, below is a snippet from the `set-paths` phase targeting arm-linux-gnueabihf

[...]


> This only happens when source is a git repository, and only when
> building the kernel.
> When a tarball is used this does not happen because it is not a directory in the store.

This has already been fixed on the core-updates branch [0], which is
scheduled for a merge in a not too distant future.  See commit
6454208222 ("build: gnu-build-system: Remove source from native
inputs.").

Closing.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-03-02 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 20:45 bug#61698: Incorrect Native *_PATH's when linux source is not a tarball Mitchell Schmeisser via Bug reports for GNU Guix
2023-03-02 21:23 ` Maxim Cournoyer [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

  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=87jzzyetkr.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=61698-done@debbugs.gnu.org \
    --cc=mitchellschmeisser@librem.one \
    /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 public inbox

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

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).