* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
@ 2013-06-05 21:59 Thomas Petazzoni
2013-06-05 21:59 ` [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture Thomas Petazzoni
2013-06-06 8:31 ` [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Markos Chandras
0 siblings, 2 replies; 11+ messages in thread
From: Thomas Petazzoni @ 2013-06-05 21:59 UTC (permalink / raw)
To: buildroot
On some architectures, such as MIPS, the linker supports several 'ld
emulation', and depending on which flavor of the architecture you're
building for, one should be passing the proper -m <something> option
to ld, otherwise ld defaults to the default emulation, which may not
necessarily be compatible with the object files that are being
linked. See for example the following build failure:
http://autobuild.buildroot.org/results/0e1/0e18e02e01148afb36acd2293b3fdc56c6bb8413/build-end.log
So, we extend the toolchain wrapper to also wrap the ld linker, and
allow a BR_LD_EMULATION variable to be passed to it.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
arch/Config.in | 3 +++
toolchain/toolchain-external/ext-tool.mk | 6 ++++-
.../toolchain-external/ext-toolchain-wrapper.c | 26 +++++++++++++++++-----
3 files changed, 29 insertions(+), 6 deletions(-)
diff --git a/arch/Config.in b/arch/Config.in
index 5ca05cd..aab9922 100644
--- a/arch/Config.in
+++ b/arch/Config.in
@@ -192,6 +192,9 @@ config BR2_GCC_TARGET_CPU
config BR2_GCC_TARGET_CPU_REVISION
string
+config BR2_LD_TARGET_EMULATION
+ string
+
# Set up target binary format
choice
prompt "Target Binary Format"
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index 93b3b15..c132e6a 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -141,6 +141,7 @@ CC_TARGET_CPU_:=$(call qstrip,$(BR2_GCC_TARGET_CPU)-$(BR2_GCC_TARGET_CPU_REVISIO
endif
CC_TARGET_ARCH_:=$(call qstrip,$(BR2_GCC_TARGET_ARCH))
CC_TARGET_ABI_:=$(call qstrip,$(BR2_GCC_TARGET_ABI))
+LD_TARGET_EMULATION_:=$(call qstrip,$(BR2_LD_TARGET_EMULATION))
# march/mtune/floating point mode needs to be passed to the external toolchain
# to select the right multilib variant
@@ -164,6 +165,9 @@ ifneq ($(CC_TARGET_ABI_),)
TOOLCHAIN_EXTERNAL_CFLAGS += -mabi=$(CC_TARGET_ABI_)
TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_ABI='"$(CC_TARGET_ABI_)"'
endif
+ifneq ($(LD_TARGET_EMULATION_),)
+TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_LD_EMULATION='"$(LD_TARGET_EMULATION_)"'
+endif
ifeq ($(BR2_BINFMT_FLAT),y)
TOOLCHAIN_EXTERNAL_CFLAGS += -Wl,-elf2flt
TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_BINFMT_FLAT
@@ -468,7 +472,7 @@ $(HOST_DIR)/usr/bin/ext-toolchain-wrapper: $(STAMP_DIR)/ext-toolchain-installed
for i in $(TOOLCHAIN_EXTERNAL_CROSS)*; do \
base=$${i##*/}; \
case "$$base" in \
- *cc|*cc-*|*++|*++-*|*cpp) \
+ *cc|*cc-*|*++|*++-*|*cpp|*ld) \
ln -sf $(@F) $$base; \
;; \
*) \
diff --git a/toolchain/toolchain-external/ext-toolchain-wrapper.c b/toolchain/toolchain-external/ext-toolchain-wrapper.c
index 9d79d68..e2b945e 100644
--- a/toolchain/toolchain-external/ext-toolchain-wrapper.c
+++ b/toolchain/toolchain-external/ext-toolchain-wrapper.c
@@ -23,7 +23,7 @@
static char path[PATH_MAX];
static char sysroot[PATH_MAX];
-static char *predef_args[] = {
+static char *gcc_predef_args[] = {
path,
"--sysroot", sysroot,
#ifdef BR_ARCH
@@ -55,13 +55,21 @@ static char *predef_args[] = {
#endif
};
+static char *ld_predef_args[] = {
+ path,
+#ifdef BR_LD_EMULATION
+ "-m", BR_LD_EMULATION,
+#endif
+};
+
int main(int argc, char **argv)
{
char **args, **cur;
char *relbasedir, *absbasedir;
char *progpath = argv[0];
char *basename;
- int ret, i, count = 0;
+ char **predef_args;
+ int ret, i, predef_args_sz, count = 0;
/* Calculate the relative paths */
basename = strrchr(progpath, '/');
@@ -113,15 +121,23 @@ int main(int argc, char **argv)
return 3;
}
- cur = args = malloc(sizeof(predef_args) + (sizeof(char *) * argc));
+ if (!strncmp("-ld", basename + strlen(basename) - 3, 3)) {
+ predef_args_sz = sizeof(ld_predef_args);
+ predef_args = ld_predef_args;
+ } else {
+ predef_args_sz = sizeof(gcc_predef_args);
+ predef_args = gcc_predef_args;
+ }
+
+ cur = args = malloc(predef_args_sz + (sizeof(char *) * argc));
if (args == NULL) {
perror(__FILE__ ": malloc");
return 2;
}
/* start with predefined args */
- memcpy(cur, predef_args, sizeof(predef_args));
- cur += sizeof(predef_args) / sizeof(predef_args[0]);
+ memcpy(cur, predef_args, predef_args_sz);
+ cur += predef_args_sz / sizeof(char *);
/* append forward args */
memcpy(cur, &argv[1], sizeof(char *) * (argc - 1));
--
1.8.1.2
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture
2013-06-05 21:59 [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Thomas Petazzoni
@ 2013-06-05 21:59 ` Thomas Petazzoni
2013-06-06 8:37 ` Markos Chandras
2013-06-06 8:31 ` [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Markos Chandras
1 sibling, 1 reply; 11+ messages in thread
From: Thomas Petazzoni @ 2013-06-05 21:59 UTC (permalink / raw)
To: buildroot
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
arch/Config.in.mips | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/Config.in.mips b/arch/Config.in.mips
index 1454fb4..7f134f8 100644
--- a/arch/Config.in.mips
+++ b/arch/Config.in.mips
@@ -76,3 +76,11 @@ config BR2_GCC_TARGET_ABI
default "32" if BR2_MIPS_OABI32
default "n32" if BR2_MIPS_NABI32
default "64" if BR2_MIPS_NABI64
+
+config BR2_LD_TARGET_EMULATION
+ default "elf64ltsmip" if BR2_mips64el
+ default "elf64btsmip" if BR2_mips64
+ default "elf32ltsmip" if BR2_mipsel && !BR2_MIPS_NABI32
+ default "elf32btsmip" if BR2_mips && !BR2_MIPS_NABI32
+ default "elf32ltsmipn32" if BR2_mipsel && BR2_MIPS_NABI32
+ default "elf32btsmipn32" if BR2_mips && BR2_MIPS_NABI32
--
1.8.1.2
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
2013-06-05 21:59 [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Thomas Petazzoni
2013-06-05 21:59 ` [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture Thomas Petazzoni
@ 2013-06-06 8:31 ` Markos Chandras
2013-06-06 8:51 ` Thomas Petazzoni
1 sibling, 1 reply; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 8:31 UTC (permalink / raw)
To: buildroot
On 5 June 2013 22:59, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> On some architectures, such as MIPS, the linker supports several 'ld
> emulation', and depending on which flavor of the architecture you're
> building for, one should be passing the proper -m <something> option
> to ld, otherwise ld defaults to the default emulation, which may not
> necessarily be compatible with the object files that are being
> linked. See for example the following build failure:
>
> http://autobuild.buildroot.org/results/0e1/0e18e02e01148afb36acd2293b3fdc56c6bb8413/build-end.log
>
> So, we extend the toolchain wrapper to also wrap the ld linker, and
> allow a BR_LD_EMULATION variable to be passed to it.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/Config.in | 3 +++
> toolchain/toolchain-external/ext-tool.mk | 6 ++++-
> .../toolchain-external/ext-toolchain-wrapper.c | 26 +++++++++++++++++-----
> 3 files changed, 29 insertions(+), 6 deletions(-)
>
> diff --git a/arch/Config.in b/arch/Config.in
> index 5ca05cd..aab9922 100644
> --- a/arch/Config.in
> +++ b/arch/Config.in
> @@ -192,6 +192,9 @@ config BR2_GCC_TARGET_CPU
> config BR2_GCC_TARGET_CPU_REVISION
> string
>
> +config BR2_LD_TARGET_EMULATION
> + string
> +
> # Set up target binary format
> choice
> prompt "Target Binary Format"
> diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
> index 93b3b15..c132e6a 100644
> --- a/toolchain/toolchain-external/ext-tool.mk
> +++ b/toolchain/toolchain-external/ext-tool.mk
> @@ -141,6 +141,7 @@ CC_TARGET_CPU_:=$(call qstrip,$(BR2_GCC_TARGET_CPU)-$(BR2_GCC_TARGET_CPU_REVISIO
> endif
> CC_TARGET_ARCH_:=$(call qstrip,$(BR2_GCC_TARGET_ARCH))
> CC_TARGET_ABI_:=$(call qstrip,$(BR2_GCC_TARGET_ABI))
> +LD_TARGET_EMULATION_:=$(call qstrip,$(BR2_LD_TARGET_EMULATION))
>
> # march/mtune/floating point mode needs to be passed to the external toolchain
> # to select the right multilib variant
> @@ -164,6 +165,9 @@ ifneq ($(CC_TARGET_ABI_),)
> TOOLCHAIN_EXTERNAL_CFLAGS += -mabi=$(CC_TARGET_ABI_)
> TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_ABI='"$(CC_TARGET_ABI_)"'
> endif
> +ifneq ($(LD_TARGET_EMULATION_),)
> +TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_LD_EMULATION='"$(LD_TARGET_EMULATION_)"'
> +endif
> ifeq ($(BR2_BINFMT_FLAT),y)
> TOOLCHAIN_EXTERNAL_CFLAGS += -Wl,-elf2flt
> TOOLCHAIN_EXTERNAL_WRAPPER_ARGS += -DBR_BINFMT_FLAT
> @@ -468,7 +472,7 @@ $(HOST_DIR)/usr/bin/ext-toolchain-wrapper: $(STAMP_DIR)/ext-toolchain-installed
> for i in $(TOOLCHAIN_EXTERNAL_CROSS)*; do \
> base=$${i##*/}; \
> case "$$base" in \
> - *cc|*cc-*|*++|*++-*|*cpp) \
> + *cc|*cc-*|*++|*++-*|*cpp|*ld) \
> ln -sf $(@F) $$base; \
> ;; \
> *) \
> diff --git a/toolchain/toolchain-external/ext-toolchain-wrapper.c b/toolchain/toolchain-external/ext-toolchain-wrapper.c
> index 9d79d68..e2b945e 100644
> --- a/toolchain/toolchain-external/ext-toolchain-wrapper.c
> +++ b/toolchain/toolchain-external/ext-toolchain-wrapper.c
> @@ -23,7 +23,7 @@
> static char path[PATH_MAX];
> static char sysroot[PATH_MAX];
>
> -static char *predef_args[] = {
> +static char *gcc_predef_args[] = {
> path,
> "--sysroot", sysroot,
> #ifdef BR_ARCH
> @@ -55,13 +55,21 @@ static char *predef_args[] = {
> #endif
> };
>
> +static char *ld_predef_args[] = {
> + path,
> +#ifdef BR_LD_EMULATION
> + "-m", BR_LD_EMULATION,
> +#endif
> +};
> +
> int main(int argc, char **argv)
> {
> char **args, **cur;
> char *relbasedir, *absbasedir;
> char *progpath = argv[0];
> char *basename;
> - int ret, i, count = 0;
> + char **predef_args;
> + int ret, i, predef_args_sz, count = 0;
>
> /* Calculate the relative paths */
> basename = strrchr(progpath, '/');
> @@ -113,15 +121,23 @@ int main(int argc, char **argv)
> return 3;
> }
>
> - cur = args = malloc(sizeof(predef_args) + (sizeof(char *) * argc));
> + if (!strncmp("-ld", basename + strlen(basename) - 3, 3)) {
> + predef_args_sz = sizeof(ld_predef_args);
> + predef_args = ld_predef_args;
> + } else {
> + predef_args_sz = sizeof(gcc_predef_args);
> + predef_args = gcc_predef_args;
> + }
> +
> + cur = args = malloc(predef_args_sz + (sizeof(char *) * argc));
> if (args == NULL) {
> perror(__FILE__ ": malloc");
> return 2;
> }
>
> /* start with predefined args */
> - memcpy(cur, predef_args, sizeof(predef_args));
> - cur += sizeof(predef_args) / sizeof(predef_args[0]);
> + memcpy(cur, predef_args, predef_args_sz);
> + cur += predef_args_sz / sizeof(char *);
>
> /* append forward args */
> memcpy(cur, &argv[1], sizeof(char *) * (argc - 1));
> --
> 1.8.1.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Hi Thomas,
My understanding is that this is also a problem with buildroot
toolchains as well. So whilst your patch fixes the problem with
external
toolchains, MIPS64/n64 buildroot toolchains will still have the same problem.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture
2013-06-05 21:59 ` [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture Thomas Petazzoni
@ 2013-06-06 8:37 ` Markos Chandras
2013-06-06 8:57 ` Thomas Petazzoni
0 siblings, 1 reply; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 8:37 UTC (permalink / raw)
To: buildroot
On 5 June 2013 22:59, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/Config.in.mips | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/Config.in.mips b/arch/Config.in.mips
> index 1454fb4..7f134f8 100644
> --- a/arch/Config.in.mips
> +++ b/arch/Config.in.mips
> @@ -76,3 +76,11 @@ config BR2_GCC_TARGET_ABI
> default "32" if BR2_MIPS_OABI32
> default "n32" if BR2_MIPS_NABI32
> default "64" if BR2_MIPS_NABI64
> +
> +config BR2_LD_TARGET_EMULATION
> + default "elf64ltsmip" if BR2_mips64el
> + default "elf64btsmip" if BR2_mips64
> + default "elf32ltsmip" if BR2_mipsel && !BR2_MIPS_NABI32
> + default "elf32btsmip" if BR2_mips && !BR2_MIPS_NABI32
> + default "elf32ltsmipn32" if BR2_mipsel && BR2_MIPS_NABI32
> + default "elf32btsmipn32" if BR2_mips && BR2_MIPS_NABI32
> --
> 1.8.1.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Hi Thomas,
binutils set el32{l,b}smipn32 as default ABI for MIPS64 as well. The
elf64{l,b}tsmip one need to be used only if you want to use the n64
ABI. My opinion is that this patch needs to be changed to something
like this:
+config BR2_LD_TARGET_EMULATION
+ default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
+ default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
+ default "elf32ltsmip" if BR2_mipsel && !BR2_MIPS_NABI32
+ default "elf32btsmip" if BR2_mips && !BR2_MIPS_NABI32
+ default "elf32ltsmipn32" if BR2_mipsel && BR2_MIPS_NABI32
+ default "elf32btsmipn32" if BR2_mips && BR2_MIPS_NABI32
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
2013-06-06 8:31 ` [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Markos Chandras
@ 2013-06-06 8:51 ` Thomas Petazzoni
2013-06-06 8:56 ` Markos Chandras
0 siblings, 1 reply; 11+ messages in thread
From: Thomas Petazzoni @ 2013-06-06 8:51 UTC (permalink / raw)
To: buildroot
Dear Markos Chandras,
On Thu, 6 Jun 2013 09:31:25 +0100, Markos Chandras wrote:
> My understanding is that this is also a problem with buildroot
> toolchains as well. So whilst your patch fixes the problem with
> external
> toolchains, MIPS64/n64 buildroot toolchains will still have the same
> problem.
Yes, I do remember your patch
http://patchwork.ozlabs.org/patch/244694/. Normally, for internal
toolchains, the idea is that the tools (gcc, ld) are configured, at
build time, to produce the 'right' code by default, without requiring
any tuning. The man page of 'ld' says:
-m emulation
Emulate the emulation linker. You can list the available
emulations with the --verbose or -V options.
If the -m option is not used, the emulation is taken from the
"LDEMULATION" environment variable, if that is defined.
Otherwise, the default emulation depends upon how the linker
was configured.
The last paragraph being the important one here. See what OpenEmbedded
is doing:
https://github.com/openembedded/oe-core/blob/master/meta/recipes-devtools/binutils/binutils-2.23.2/mips64-default-ld-emulation.patch.
The problem here is that the MIPS tuples do not contain the ABI, so the
ld/configure.tgt and bfd/config.bfd scripts of binutils have no way of
knowing which emulation you would like to have by default. Maybe we
need to improve binutils to make this configurable?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
2013-06-06 8:51 ` Thomas Petazzoni
@ 2013-06-06 8:56 ` Markos Chandras
2013-06-06 9:13 ` Markos Chandras
0 siblings, 1 reply; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 8:56 UTC (permalink / raw)
To: buildroot
On 6 June 2013 09:51, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Markos Chandras,
>
> On Thu, 6 Jun 2013 09:31:25 +0100, Markos Chandras wrote:
>
>> My understanding is that this is also a problem with buildroot
>> toolchains as well. So whilst your patch fixes the problem with
>> external
>> toolchains, MIPS64/n64 buildroot toolchains will still have the same
>> problem.
>
> Yes, I do remember your patch
> http://patchwork.ozlabs.org/patch/244694/. Normally, for internal
> toolchains, the idea is that the tools (gcc, ld) are configured, at
> build time, to produce the 'right' code by default, without requiring
> any tuning. The man page of 'ld' says:
>
> -m emulation
> Emulate the emulation linker. You can list the available
> emulations with the --verbose or -V options.
>
> If the -m option is not used, the emulation is taken from the
> "LDEMULATION" environment variable, if that is defined.
>
> Otherwise, the default emulation depends upon how the linker
> was configured.
>
> The last paragraph being the important one here. See what OpenEmbedded
> is doing:
> https://github.com/openembedded/oe-core/blob/master/meta/recipes-devtools/binutils/binutils-2.23.2/mips64-default-ld-emulation.patch.
>
> The problem here is that the MIPS tuples do not contain the ABI, so the
> ld/configure.tgt and bfd/config.bfd scripts of binutils have no way of
> knowing which emulation you would like to have by default. Maybe we
> need to improve binutils to make this configurable?
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
Hi Thomas,
Yes I've seen this patch before but given this is not in the upstream
binutils code I had to "workaround" it by using the exported
LDEMULATION variable. It might worth taking this to the binutils
mailing list.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture
2013-06-06 8:37 ` Markos Chandras
@ 2013-06-06 8:57 ` Thomas Petazzoni
2013-06-06 9:04 ` Markos Chandras
0 siblings, 1 reply; 11+ messages in thread
From: Thomas Petazzoni @ 2013-06-06 8:57 UTC (permalink / raw)
To: buildroot
Dear Markos Chandras,
On Thu, 6 Jun 2013 09:37:41 +0100, Markos Chandras wrote:
> binutils set el32{l,b}smipn32 as default ABI for MIPS64 as well. The
> elf64{l,b}tsmip one need to be used only if you want to use the n64
> ABI. My opinion is that this patch needs to be changed to something
> like this:
>
> +config BR2_LD_TARGET_EMULATION
> + default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
> + default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
> + default "elf32ltsmip" if BR2_mipsel && !BR2_MIPS_NABI32
> + default "elf32btsmip" if BR2_mips && !BR2_MIPS_NABI32
> + default "elf32ltsmipn32" if BR2_mipsel && BR2_MIPS_NABI32
> + default "elf32btsmipn32" if BR2_mips && BR2_MIPS_NABI32
Ok, but I'm not too happy with the fact that the BR2_mips64[el]
&& !BR2_MIPS_NABI64 is not being handled here. And according to
arch/Config.in.mips, in fact the n32 ABI does not make sense on 32 bits
BR2_mips and BR2_mipsel.
So, shouldn't this thing be:
config BR2_LD_TARGET_EMULATION
default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
default "elf32ltsmipn32" if BR2_mips64el && BR2_MIPS_NABI32
default "elf32btsmipn32" if BR2_mips64 && BR2_MIPS_NABI32
default "elf32ltsmip" if (BR2_mips64el && BR2_MIPS_OABI32) || BR2_mipsel
default "elf32btsmip" if (BR2_mips64 && BR2_MIPS_OABI32) || BR2_mips
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture
2013-06-06 8:57 ` Thomas Petazzoni
@ 2013-06-06 9:04 ` Markos Chandras
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 9:04 UTC (permalink / raw)
To: buildroot
On 6 June 2013 09:57, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Markos Chandras,
>
> On Thu, 6 Jun 2013 09:37:41 +0100, Markos Chandras wrote:
>
>> binutils set el32{l,b}smipn32 as default ABI for MIPS64 as well. The
>> elf64{l,b}tsmip one need to be used only if you want to use the n64
>> ABI. My opinion is that this patch needs to be changed to something
>> like this:
>>
>> +config BR2_LD_TARGET_EMULATION
>> + default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
>> + default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
>> + default "elf32ltsmip" if BR2_mipsel && !BR2_MIPS_NABI32
>> + default "elf32btsmip" if BR2_mips && !BR2_MIPS_NABI32
>> + default "elf32ltsmipn32" if BR2_mipsel && BR2_MIPS_NABI32
>> + default "elf32btsmipn32" if BR2_mips && BR2_MIPS_NABI32
>
> Ok, but I'm not too happy with the fact that the BR2_mips64[el]
> && !BR2_MIPS_NABI64 is not being handled here. And according to
> arch/Config.in.mips, in fact the n32 ABI does not make sense on 32 bits
> BR2_mips and BR2_mipsel.
>
> So, shouldn't this thing be:
>
> config BR2_LD_TARGET_EMULATION
> default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
> default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
> default "elf32ltsmipn32" if BR2_mips64el && BR2_MIPS_NABI32
> default "elf32btsmipn32" if BR2_mips64 && BR2_MIPS_NABI32
> default "elf32ltsmip" if (BR2_mips64el && BR2_MIPS_OABI32) || BR2_mipsel
> default "elf32btsmip" if (BR2_mips64 && BR2_MIPS_OABI32) || BR2_mips
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers, real-time and embedded Linux
> development, consulting, training and support.
> http://free-electrons.com
>
Hi Thomas,
Yes I believe this makes sense
Reviewed-by: Markos Chandras <markos.chandras@imgtec.com>
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
2013-06-06 8:56 ` Markos Chandras
@ 2013-06-06 9:13 ` Markos Chandras
2013-06-06 10:04 ` Markos Chandras
0 siblings, 1 reply; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 9:13 UTC (permalink / raw)
To: buildroot
On 6 June 2013 09:56, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 6 June 2013 09:51, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Markos Chandras,
>>
>> On Thu, 6 Jun 2013 09:31:25 +0100, Markos Chandras wrote:
>>
>>> My understanding is that this is also a problem with buildroot
>>> toolchains as well. So whilst your patch fixes the problem with
>>> external
>>> toolchains, MIPS64/n64 buildroot toolchains will still have the same
>>> problem.
>>
>> Yes, I do remember your patch
>> http://patchwork.ozlabs.org/patch/244694/. Normally, for internal
>> toolchains, the idea is that the tools (gcc, ld) are configured, at
>> build time, to produce the 'right' code by default, without requiring
>> any tuning. The man page of 'ld' says:
>>
>> -m emulation
>> Emulate the emulation linker. You can list the available
>> emulations with the --verbose or -V options.
>>
>> If the -m option is not used, the emulation is taken from the
>> "LDEMULATION" environment variable, if that is defined.
>>
>> Otherwise, the default emulation depends upon how the linker
>> was configured.
>>
>> The last paragraph being the important one here. See what OpenEmbedded
>> is doing:
>> https://github.com/openembedded/oe-core/blob/master/meta/recipes-devtools/binutils/binutils-2.23.2/mips64-default-ld-emulation.patch.
>>
>> The problem here is that the MIPS tuples do not contain the ABI, so the
>> ld/configure.tgt and bfd/config.bfd scripts of binutils have no way of
>> knowing which emulation you would like to have by default. Maybe we
>> need to improve binutils to make this configurable?
>>
>> Thomas
>> --
>> Thomas Petazzoni, Free Electrons
>> Kernel, drivers, real-time and embedded Linux
>> development, consulting, training and support.
>> http://free-electrons.com
>>
>
> Hi Thomas,
>
> Yes I've seen this patch before but given this is not in the upstream
> binutils code I had to "workaround" it by using the exported
> LDEMULATION variable. It might worth taking this to the binutils
> mailing list.
>
> --
> Regards,
> Markos Chandras - Gentoo Linux Developer
> http://dev.gentoo.org/~hwoarang
Hi Thomas,
Just tested this patch. Looks good to me.
Tested-by: Markos Chandras <markos.chandras@imgtec.com>
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified
2013-06-06 9:13 ` Markos Chandras
@ 2013-06-06 10:04 ` Markos Chandras
0 siblings, 0 replies; 11+ messages in thread
From: Markos Chandras @ 2013-06-06 10:04 UTC (permalink / raw)
To: buildroot
On 6 June 2013 10:13, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 6 June 2013 09:56, Markos Chandras <hwoarang@gentoo.org> wrote:
>> On 6 June 2013 09:51, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com> wrote:
>>> Dear Markos Chandras,
>>>
>>> On Thu, 6 Jun 2013 09:31:25 +0100, Markos Chandras wrote:
>>>
>>>> My understanding is that this is also a problem with buildroot
>>>> toolchains as well. So whilst your patch fixes the problem with
>>>> external
>>>> toolchains, MIPS64/n64 buildroot toolchains will still have the same
>>>> problem.
>>>
>>> Yes, I do remember your patch
>>> http://patchwork.ozlabs.org/patch/244694/. Normally, for internal
>>> toolchains, the idea is that the tools (gcc, ld) are configured, at
>>> build time, to produce the 'right' code by default, without requiring
>>> any tuning. The man page of 'ld' says:
>>>
>>> -m emulation
>>> Emulate the emulation linker. You can list the available
>>> emulations with the --verbose or -V options.
>>>
>>> If the -m option is not used, the emulation is taken from the
>>> "LDEMULATION" environment variable, if that is defined.
>>>
>>> Otherwise, the default emulation depends upon how the linker
>>> was configured.
>>>
>>> The last paragraph being the important one here. See what OpenEmbedded
>>> is doing:
>>> https://github.com/openembedded/oe-core/blob/master/meta/recipes-devtools/binutils/binutils-2.23.2/mips64-default-ld-emulation.patch.
>>>
>>> The problem here is that the MIPS tuples do not contain the ABI, so the
>>> ld/configure.tgt and bfd/config.bfd scripts of binutils have no way of
>>> knowing which emulation you would like to have by default. Maybe we
>>> need to improve binutils to make this configurable?
>>>
>>> Thomas
>>> --
>>> Thomas Petazzoni, Free Electrons
>>> Kernel, drivers, real-time and embedded Linux
>>> development, consulting, training and support.
>>> http://free-electrons.com
>>>
>>
>> Hi Thomas,
>>
>> Yes I've seen this patch before but given this is not in the upstream
>> binutils code I had to "workaround" it by using the exported
>> LDEMULATION variable. It might worth taking this to the binutils
>> mailing list.
>>
>> --
>> Regards,
>> Markos Chandras - Gentoo Linux Developer
>> http://dev.gentoo.org/~hwoarang
>
> Hi Thomas,
>
> Just tested this patch. Looks good to me.
>
> Tested-by: Markos Chandras <markos.chandras@imgtec.com>
>
> --
> Regards,
> Markos Chandras - Gentoo Linux Developer
> http://dev.gentoo.org/~hwoarang
Hi Thomas,
I am also taking a look at the log you provided. It seems even though
libtool uses gcc to do the linking it actually invokes the linker
without the proper options. A mips64/n64 gcc will pass the correct -m
option to the linker but here it seems to ignore that. I could be a
problem with libtool itself.
I am inclined to say that binutils do not need to be changed, because
you should never call the linker directly to do the linking (I recall
directfb does that and fails with the same problem). You should be
using gcc instead and it will pass all the appropriate linker flags to
the linker. Such build systems need fixing instead of trying to
workaround the problem in the toolchain.
Having said that, the entire patchset could be seen as a temporary
workaround for this problem. In the libiscsi case, I need to
understand why libtool invokes the linker without the correct flags.
If you try to compile a simple test program using the buildroot
mip64-linux-gcc toolchain (pass -v as well) you will notice that gcc
passes -melf64btsmip correctly.
--
Regards,
Markos Chandras - Gentoo Linux Developer
http://dev.gentoo.org/~hwoarang
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture
2016-02-20 9:33 Jan Heylen
@ 2016-02-20 9:33 ` Jan Heylen
0 siblings, 0 replies; 11+ messages in thread
From: Jan Heylen @ 2016-02-20 9:33 UTC (permalink / raw)
To: buildroot
based upon patch from Thomas Petazzoni:
http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/60942
Signed-off-by: Jan Heylen <heyleke@gmail.com>
---
arch/Config.in.mips | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/Config.in.mips b/arch/Config.in.mips
index fda1a1d..37e4bf6 100644
--- a/arch/Config.in.mips
+++ b/arch/Config.in.mips
@@ -83,3 +83,11 @@ config BR2_GCC_TARGET_ABI
default "32" if BR2_MIPS_OABI32
default "n32" if BR2_MIPS_NABI32
default "64" if BR2_MIPS_NABI64
+
+config BR2_LD_TARGET_EMULATION
+ default "elf64ltsmip" if BR2_mips64el && BR2_MIPS_NABI64
+ default "elf64btsmip" if BR2_mips64 && BR2_MIPS_NABI64
+ default "elf32ltsmipn32" if BR2_mips64el && BR2_MIPS_NABI32
+ default "elf32btsmipn32" if BR2_mips64 && BR2_MIPS_NABI32
+ default "elf32ltsmip" if (BR2_mips64el && BR2_MIPS_OABI32) || BR2_mipsel
+ default "elf32btsmip" if (BR2_mips64 && BR2_MIPS_OABI32) || BR2_mips
--
2.5.0
^ permalink raw reply related [flat|nested] 11+ messages in thread
end of thread, other threads:[~2016-02-20 9:33 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-05 21:59 [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Thomas Petazzoni
2013-06-05 21:59 ` [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture Thomas Petazzoni
2013-06-06 8:37 ` Markos Chandras
2013-06-06 8:57 ` Thomas Petazzoni
2013-06-06 9:04 ` Markos Chandras
2013-06-06 8:31 ` [Buildroot] [PATCH 1/2] toolchain: wrap 'ld' so that a ld emulation can be specified Markos Chandras
2013-06-06 8:51 ` Thomas Petazzoni
2013-06-06 8:56 ` Markos Chandras
2013-06-06 9:13 ` Markos Chandras
2013-06-06 10:04 ` Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
2016-02-20 9:33 Jan Heylen
2016-02-20 9:33 ` [Buildroot] [PATCH 2/2] arch: define appropriate ld emulation values for the MIPS architecture Jan Heylen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox