From: Peter Korsgaard <peter@korsgaard.com>
To: Alex <earthquake.de@freenet.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] buildroot host builds with g++
Date: Mon, 09 May 2022 08:50:52 +0200 [thread overview]
Message-ID: <87wnevfbcj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <7f010cd1-dd28-f72c-7218-623bcdffa4f1@freenet.de> (Alex's message of "Mon, 9 May 2022 08:46:56 +0200")
>>>>> "Alex" == Alex <earthquake.de@freenet.de> writes:
Hi,
>> > g++ is installed on my build machine where I create my buildroot system.
>> > The project compiles outside of buildroot on my build machine.
>> > Does buildroot environment need a link/variable to the g++ on the
>> > built machine?
>>
>> Are you sure? Based on the above, it doesn't sound like you have a
>> /usr/bin/g++?
> Im sure: $>which g++
> /usr/bin/g++
> g++ is a link which points over etc/alternatives to
> /usr/bin/x86_64-linux-gnu-g++-7
Ok, then you will need to look closer at the build system of that
package to understand what is going on. Perhaps it plays around with
LD_LIBRARY_PATH or similar?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-09 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <80d6f58b-a36e-6148-c6b6-37a29d3244e5@freenet.de>
2022-05-06 15:23 ` [Buildroot] buildroot host builds with g++ Peter Korsgaard
2022-05-08 8:35 ` Alex
2022-05-08 9:06 ` Peter Korsgaard
2022-05-08 18:09 ` Alex
2022-05-08 19:25 ` Peter Korsgaard
2022-05-09 6:46 ` Alex
2022-05-09 6:50 ` Peter Korsgaard [this message]
2022-05-09 8:20 ` Alex
2022-05-06 14:23 Earthquake
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=87wnevfbcj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=earthquake.de@freenet.de \
/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.