Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Norbert Lange <nolange79@gmail.com>
To: buildroot@buildroot.org
Cc: Norbert Lange <nolange79@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH] package/libxml-parser-perl: fix build when host matches target gcc
Date: Sat, 10 Dec 2022 14:17:11 +0100	[thread overview]
Message-ID: <20221210131713.274886-1-nolange79@gmail.com> (raw)

The host configure and build step looks for same compiler name
(eg. x86_64-linux-gnu-gcc), and the build potentially breaks
if the target compiler is named identically.

revert PATH env variable to not include the target binaries.

Signed-off-by: Norbert Lange <nolange79@gmail.com>
---
 package/libxml-parser-perl/libxml-parser-perl.mk | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/libxml-parser-perl/libxml-parser-perl.mk b/package/libxml-parser-perl/libxml-parser-perl.mk
index 37cef2e418..4af4485429 100644
--- a/package/libxml-parser-perl/libxml-parser-perl.mk
+++ b/package/libxml-parser-perl/libxml-parser-perl.mk
@@ -14,6 +14,7 @@ LIBXML_PARSER_PERL_RUN_PERL = `which perl`
 
 HOST_LIBXML_PARSER_PERL_CONFIGURE_OPTS = \
 	$(HOST_CONFIGURE_OPTS) \
+	PATH="$(PATH)" \
 	LD="$(HOSTCC)"
 
 define HOST_LIBXML_PARSER_PERL_CONFIGURE_CMDS
-- 
2.35.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-12-10 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 13:17 Norbert Lange [this message]
2022-12-10 16:18 ` [Buildroot] [PATCH] package/libxml-parser-perl: fix build when host matches target gcc Yann E. MORIN
2022-12-10 16:55   ` Norbert Lange

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=20221210131713.274886-1-nolange79@gmail.com \
    --to=nolange79@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox