From: Efraim Flashner <efraim@flashner.co.il>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: 42681@debbugs.gnu.org
Subject: [bug#42681] [PATCH core-updates] gnu: bootstrap-gcc: Don't use CPATH search paths.
Date: Mon, 3 Aug 2020 09:40:26 +0300 [thread overview]
Message-ID: <20200803064026.GF1134@E5400> (raw)
In-Reply-To: <20200802203421.5959-1-kuba@kadziolka.net>
[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]
On Sun, Aug 02, 2020 at 10:34:21PM +0200, Jakub Kądziołka wrote:
> This updates the bootstrap-gcc to use the same search path strategy as
> the main compilers, making the bootstrap environment more similar across
> architectures, and fixing the bootstrap path on non-x86 architectures
> again.
>
> This is a follow up to commit 7cde865f12dd67e55946a52a21103e71f447eced.
>
> * gnu/packages/bootstrap.scm (%bootstrap-gcc)[native-search-paths]: Use
> C_INCLUDE_PATH and CPLUS_INCLUDE_PATH instead of CPATH.
> ---
>
> Note: because I don't have any non-x86 machines on hand, I haven't
> actually tested the patch yet.
>
> Efraim, you have helped me investigate this with your ARM board, perhaps
> you could test this patch?
>
> Regards,
> Jakub Kądziołka
> gnu/packages/bootstrap.scm | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/bootstrap.scm b/gnu/packages/bootstrap.scm
> index c39e60ec8b..fd6c2e099c 100644
> --- a/gnu/packages/bootstrap.scm
> +++ b/gnu/packages/bootstrap.scm
> @@ -740,8 +740,11 @@ exec ~a/bin/.gcc-wrapped -B~a/lib \
> "1m5miqkyng45l745n0sfafdpjkqv9225xf44jqkygwsipj2cv9ks")))))))))
> (native-search-paths
> (list (search-path-specification
> - (variable "CPATH")
> + (variable "C_INCLUDE_PATH")
> (files '("include")))
> + (search-path-specification
> + (variable "CPLUS_INCLUDE_PATH")
> + (files '("include/c++" "include")))
> (search-path-specification
> (variable "LIBRARY_PATH")
> (files '("lib" "lib64")))))
> --
> 2.28.0
>
I'm building out to hello on my aarch64 board now, starting from
make-boot0 apparently. Guile is only listed once so hopefully it won't
take too long.
I assume this doesn't break anything on x86_64?
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-03 6:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 20:34 [bug#42681] [PATCH core-updates] gnu: bootstrap-gcc: Don't use CPATH search paths Jakub Kądziołka
2020-08-03 6:40 ` Efraim Flashner [this message]
2020-08-03 11:03 ` Jakub Kądziołka
2020-08-04 6:00 ` Efraim Flashner
2020-08-04 12:34 ` bug#42681: " Jakub Kądziołka
2020-08-05 8:56 ` [bug#42681] " Efraim Flashner
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=20200803064026.GF1134@E5400 \
--to=efraim@flashner.co.il \
--cc=42681@debbugs.gnu.org \
--cc=kuba@kadziolka.net \
/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.