From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] pkg-infra: make sure cross compiling is enabled when host == target
Date: Sun, 15 Jul 2012 01:13:30 +0200 [thread overview]
Message-ID: <20120715011330.7b329324@skate> (raw)
In-Reply-To: <1342301006-3761-1-git-send-email-arnout@mind.be>
Le Sat, 14 Jul 2012 23:23:26 +0200,
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> a ?crit :
> When compiling for the same architecture and libc as the host,
> GNU_TARGET_NAME and GNU_HOST_NAME are equal. configure scripts use
> these to detect cross-compilation, and will decide that we're doing
> native compilation. This may trigger running of executables,
> which fail because of missing libraries in the host environment.
>
> To solve this, set the vendor part in GNU_HOST_NAME to buildroot.
>
> This problem exists for instance in xserver_xorg-server on x86_64.
Hum, after thinking a bit more about this, why would we change
GNU_HOST_NAME? It sounds strange to include "buildroot" in the name of
the build machine tuple. Adding it to the target machine tuple would
seem much more appropriate, no?
I.e:
GNU_TARGET_NAME=$(ARCH)-unknown-linux-$(LIBC)$(ABI)
changed to:
GNU_TARGET_NAME=$(ARCH)-buildroot-linux-$(LIBC)$(ABI)
No?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-14 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 22:01 [Buildroot] [PATCH] pkg-infra: make sure cross compiling is enabled when host == target Arnout Vandecappelle
2012-07-13 20:55 ` Thomas Petazzoni
2012-07-14 21:23 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2012-07-14 23:13 ` Thomas Petazzoni [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=20120715011330.7b329324@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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.
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.