unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Rutherther via Guix-patches via <guix-patches@gnu.org>
To: 68058@debbugs.gnu.org
Cc: "Christoph B." <buck.christoph@googlemail.com>,
	Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	Jean-Pierre De Jesus DIAZ <jean@foundationdevices.com>,
	Jean-Pierre De Jesus Diaz <jean@foundation.xyz>
Subject: [bug#68058] [PATCH] gnu: cross-gcc-toolchain: Add native-search-paths.
Date: Fri, 06 Sep 2024 21:12:15 +0000	[thread overview]
Message-ID: <87frqco5au.fsf@protonmail.com> (raw)
In-Reply-To: <806b88813c0d8ef1265c43b49324d4ae4338fb0d.1703678931.git.jean@foundationdevices.com>


Hello everyone,

I am currently trying to do some stuff around the arm-none-eabi toolchain,
namely also adding the 12.3 gcc toolchain. I am facing a problem with
this. Currently the `search-paths` of xgcc also include "include",
"include/c++", "lib" and "lib64" instead of just the ones under
"$target/include", ... Because of this, and mainly because they
come first, newlib doesn't build as it picks up wrong included file.
This is easily fixed by not adding the top-level include and lib,
but only the ones under the target.

Do you happen to know why the search-paths contain these for the
cross builds? And even if that is sensible, is this really the way
to go even for native-search-paths, shouldn't the top ones
be removed, or at least moved after the ones under target?

Regards,
Rutherther





      parent reply	other threads:[~2024-09-06 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-27 12:09 [bug#68058] [PATCH] gnu: cross-gcc-toolchain: Add native-search-paths Jean-Pierre De Jesus DIAZ via Guix-patches via
2024-04-09 22:44 ` Thiago Jung Bauermann
2024-04-10  9:46   ` Jean-Pierre De Jesus Diaz
2024-05-16 14:09 ` [bug#68058] Christoph B. via Guix-patches via
2024-09-06 21:12 ` Rutherther via Guix-patches via [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=87frqco5au.fsf@protonmail.com \
    --to=guix-patches@gnu.org \
    --cc=68058@debbugs.gnu.org \
    --cc=buck.christoph@googlemail.com \
    --cc=jean@foundation.xyz \
    --cc=jean@foundationdevices.com \
    --cc=rutherther@protonmail.com \
    --cc=thiago.bauermann@linaro.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 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).