[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61698: Incorrect Native *_PATH's when linux source is not a tarball.
From: |
Maxim Cournoyer |
Subject: |
bug#61698: Incorrect Native *_PATH's when linux source is not a tarball. |
Date: |
Thu, 02 Mar 2023 16:23:16 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) |
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#61698: Incorrect Native *_PATH's when linux source is not a tarball.,
Maxim Cournoyer <=