From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/micropython: fix building after dropping GIT_DIR=. workaround
Date: Sun, 04 Feb 2024 16:07:55 +0100 [thread overview]
Message-ID: <87sf28p8s4.fsf@48ers.dk> (raw)
In-Reply-To: <20240121131614.3ADE3863A1@busybox.osuosl.org> (Yann E. MORIN's message of "Sun, 21 Jan 2024 14:12:16 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=6c9be611a8b7b4caac746920c08035761a9b9d9c
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> The MICROPYTHON_MAKE_ENV variable contained two things;
> - the comon target environment variables CC, CFLAGS et al. defined in
> TARGET_MAKE_ENV,
> - the GIT_DIR workaround
> Commit 9024e1866523 (package/micropython: drop GIT_DIR=. workaround)
> totally dropped the assignment to MICROPYTHON_MAKE_ENV, but did not
> replace its expansin with TARGET_MAKE_ENV.
> This yields build error like:
> LINK build-standard/micropython
> arm-linux-gcc: ERROR: unsafe header/library path used in cross-compilation: '-L/usr/lib64/../lib64'
> Fix this by expanding TARGET_MAKE_ENV in lieu of MICROPYTHON_MAKE_ENV.
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Committed to 2023.02.x and 2023.11.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-04 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 13:12 [Buildroot] [git commit] package/micropython: fix building after dropping GIT_DIR=. workaround Yann E. MORIN
2024-02-04 15:07 ` Peter Korsgaard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf28p8s4.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=yann.morin.1998@free.fr \
/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 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.