Skip to contentSkip to conversation

Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues

PATCH New Peter Korsgaard 4 participants 21 messages Nov 2, 2017 – Nov 26, 2017

lore
Share & tools
lore

Peter Korsgaard

author
#0 lore raw

cover Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues

Hi,

The following patch series fixes various autobuilder issues from packages selecting BR2_HOSTARCH_NEEDS_IA32_* without ensuring hostarch is x86(-64), breaking the build on the gcc112 ppc64le autobuilder.

--
Bye, Peter Korsgaard

author
#1 lore raw

PATCH 1/4 kvm-unit-test: x86-64 variant only available on x86-64 hosts

We use the host compiler for x86-64 builds, so ensure it is only available on x86-64 hosts.

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/kvm-unit-tests/Config.in | 1 +
 1 file changed, 1 insertion(+)
package/kvm-unit-tests/Config.in +1 -0
index d0d9e2ef96..8b7908eee9 100644
@@ -15,6 +15,7 @@ config BR2_PACKAGE_KVM_UNIT_TESTS
 	# x86-64 we use the host gcc (see .mk file for details)
 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 || !BR2_i386
 	depends on BR2_HOST_GCC_AT_LEAST_4_5 || !BR2_x86_64
+	depends on BR2_HOSTARCH = "x86_64" || !BR2_x86_64
 	select BR2_HOSTARCH_NEEDS_IA32_COMPILER if BR2_x86_64=y
 	help
 	  kvm-unit-tests is a project as old as KVM. As its name
Signature · 1 line
2.11.0
#2 lore raw

PATCH 1/4 kvm-unit-test: x86-64 variant only available on x86-64 hosts

Quoted 13 lines · Peter Korsgaard

We use the host compiler for x86-64 builds, so ensure it is only available on x86-64 hosts.

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/kvm-unit-tests/Config.in | 1 +
 1 file changed, 1 insertion(+)
package/kvm-unit-tests/Config.in +0 -0
index d0d9e2ef96..8b7908eee9 100644

package/kvm-unit-tests/Config.in config BR2_PACKAGE_KVM_UNIT_TESTS · line 18

Quoted 4 lines
package/kvm-unit-tests/Config.in +1 -0
@@ -15,6 +15,7 @@ config BR2_PACKAGE_KVM_UNIT_TESTS
 	# x86-64 we use the host gcc (see .mk file for details)
 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 || !BR2_i386
 	depends on BR2_HOST_GCC_AT_LEAST_4_5 || !BR2_x86_64
+	depends on BR2_HOSTARCH = "x86_64" || !BR2_x86_64

I don't think this is correct: it will also build correctly for x86_64 if the
host is i386, because it uses -m32 (which is the reason to use the host compiler instead of the target compiler).

Regards,
Arnout

Quoted 4 lines
package/kvm-unit-tests/Config.in +0 -0
 	select BR2_HOSTARCH_NEEDS_IA32_COMPILER if BR2_x86_64=y
 	help
 	  kvm-unit-tests is a project as old as KVM. As its name
Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
author
#3 lore raw

PATCH 1/4 kvm-unit-test: x86-64 variant only available on x86-64 hosts

Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle <[email protected]> writes:

Quoted 8 lines · Peter Korsgaard

We use the host compiler for x86-64 builds, so ensure it is only available on x86-64 hosts.

Signed-off-by Peter Korsgaard <[email protected]>

---
package/kvm-unit-tests/Config.in | 1 +

1 file changed, 1 insertion(+)
Quoted 13 lines

package/kvm-unit-tests/Config.in config BR2_PACKAGE_KVM_UNIT_TESTS · line 18

Quoted 9 lines
package/kvm-unit-tests/Config.in +0 -0
index d0d9e2ef96..8b7908eee9 100644
@@ -15,6 +15,7 @@ config BR2_PACKAGE_KVM_UNIT_TESTS
 # x86-64 we use the host gcc (see .mk file for details)

depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 || !BR2_i386 depends on BR2_HOST_GCC_AT_LEAST_4_5 || !BR2_x86_64

package/kvm-unit-tests/Config.in +1 -0
+	depends on BR2_HOSTARCH = "x86_64" || !BR2_x86_64

I don't think this is correct: it will also build correctly for x86_64 if the
host is i386, because it uses -m32 (which is the reason to use the host compiler instead of the target compiler).

But some parts of kvm-unit-tests presumably are 64bit when building for x86-64, which wouldn't work when using the host compiler on a x86 system, right? I don't think x86 system compilers are 32/64bit multilib.

But I haven't actually used a x86 distribution in the last 10 years or so, so perhaps I'm missing something?

Signature · 1 line
Bye, Peter Korsgaard
#4 lore raw

PATCH 1/4 kvm-unit-test: x86-64 variant only available on x86-64 hosts

Quoted 25 lines · Peter Korsgaard
Quoted 11 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle <[email protected]> writes:

Quoted 8 lines · Peter Korsgaard

We use the host compiler for x86-64 builds, so ensure it is only available on x86-64 hosts.

Signed-off-by Peter Korsgaard <[email protected]>

---
package/kvm-unit-tests/Config.in | 1 +

1 file changed, 1 insertion(+)
Quoted 13 lines

package/kvm-unit-tests/Config.in config BR2_PACKAGE_KVM_UNIT_TESTS · line 18

Quoted 9 lines
package/kvm-unit-tests/Config.in +0 -0
index d0d9e2ef96..8b7908eee9 100644
@@ -15,6 +15,7 @@ config BR2_PACKAGE_KVM_UNIT_TESTS
 # x86-64 we use the host gcc (see .mk file for details)

depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 || !BR2_i386 depends on BR2_HOST_GCC_AT_LEAST_4_5 || !BR2_x86_64

package/kvm-unit-tests/Config.in +1 -0
+	depends on BR2_HOSTARCH = "x86_64" || !BR2_x86_64

I don't think this is correct: it will also build correctly for x86_64 if the
host is i386, because it uses -m32 (which is the reason to use the host compiler instead of the target compiler).

Quoted 2 lines

But some parts of kvm-unit-tests presumably are 64bit when building for x86-64,

OK, I assumed everything was built with -m32. If some parts are indeed still
64-bit then it won't work in i386 host.

Quoted 2 lines

which wouldn't work when using the host compiler on a x86 system, right? I don't think x86 system compilers are 32/64bit multilib

Actually, on Debian i386 it is possible to install 64-bit multilib I think. But
obviously we can't count on that.

BTW, what happens on x32, does anybody know that?

Quoted 2 lines

But I haven't actually used a x86 distribution in the last 10 years or so, so perhaps I'm missing something?

Yeah, it's pretty unlikely as well I guess.

I'll apply this patch as well then.

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
author
#5 lore raw

PATCH 1/4 kvm-unit-test: x86-64 variant only available on x86-64 hosts

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle <[email protected]> writes:

Hi,

Quoted 5 lines
Quoted 2 lines

But some parts of kvm-unit-tests presumably are 64bit when building for x86-64,

OK, I assumed everything was built with -m32. If some parts are indeed still
64-bit then it won't work in i386 host.

Exactly.

Quoted 7 lines
Quoted 2 lines

which wouldn't work when using the host compiler on a x86 system, right? I don't think x86 system compilers are 32/64bit multilib

Actually, on Debian i386 it is possible to install 64-bit multilib I think. But
obviously we can't count on that.

BTW, what happens on x32, does anybody know that?

Is x32 really used by any mainstream distro? I would guess it is as rare as building on a !x86 machine.

Quoted 6 lines
Quoted 2 lines

But I haven't actually used a x86 distribution in the last 10 years or so, so perhaps I'm missing something?

Yeah, it's pretty unlikely as well I guess.

I'll apply this patch as well then.

Great, thanks!

Signature · 1 line
Bye, Peter Korsgaard
author
#7 lore raw

PATCH 2/4 ti-gfx: only available on x86(-64) hosts

In reply to Peter Korsgaard

ti-gfx is provided as a x86 self extracting executable, so it is only available on x86(-64) hosts.

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/ti-gfx/Config.in | 1 +
 1 file changed, 1 insertion(+)
package/ti-gfx/Config.in +1 -0
index 6ec2f23117..dc49d822a2 100644
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_TI_GFX
 	bool "ti-gfx"
 	depends on BR2_LINUX_KERNEL && BR2_TOOLCHAIN_USES_GLIBC && BR2_arm
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	select BR2_HOSTARCH_NEEDS_IA32_LIBS
 	select BR2_PACKAGE_HAS_LIBEGL
 	select BR2_PACKAGE_HAS_LIBGLES
Signature · 1 line
2.11.0
Applied
#8 lore raw

PATCH 2/4 ti-gfx: only available on x86(-64) hosts

Quoted 4 lines · Peter Korsgaard

ti-gfx is provided as a x86 self extracting executable, so it is only available on x86(-64) hosts.

Signed-off-by Peter Korsgaard <[email protected]>

Applied to master, thanks.

Regards,
Arnout

Quoted 17 lines
---
 package/ti-gfx/Config.in | 1 +
 1 file changed, 1 insertion(+)
package/ti-gfx/Config.in +1 -0
index 6ec2f23117..dc49d822a2 100644
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_TI_GFX
 	bool "ti-gfx"
 	depends on BR2_LINUX_KERNEL && BR2_TOOLCHAIN_USES_GLIBC && BR2_arm
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	select BR2_HOSTARCH_NEEDS_IA32_LIBS
 	select BR2_PACKAGE_HAS_LIBEGL
 	select BR2_PACKAGE_HAS_LIBGLES
Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
author
#10 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

In reply to Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and host-luajit has limited architecture support, so limit to x86(-64) hosts.

Fixes:
http://autobuild.buildroot.net/results/5f5b5edb058efe976c003678e21bcc28a87cc828/

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/luajit/Config.in | 3 +++
 1 file changed, 3 insertions(+)
package/luajit/Config.in +3 -0
index 1a27c434e1..6b9c6e6ae8 100644
@@ -1,5 +1,8 @@
 config BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS
 	bool
+	# -m32 flag is used for 32bit builds and host-luajit has
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	default y if BR2_i386 || \
 		(BR2_x86_64 && BR2_HOSTARCH='x86_64') || \
 		BR2_powerpc || BR2_arm || BR2_armeb || \
Signature · 1 line
2.11.0
#11 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

Hello,

Quoted 16 lines · Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and host-luajit has limited architecture support, so limit to x86(-64) hosts.

Fixes:
http://autobuild.buildroot.net/results/5f5b5edb058efe976c003678e21bcc28a87cc828/

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/luajit/Config.in | 3 +++
 1 file changed, 3 insertions(+)
package/luajit/Config.in +0 -0
index 1a27c434e1..6b9c6e6ae8 100644

package/luajit/Config.in line 8

Quoted 8 lines
package/luajit/Config.in +3 -0
@@ -1,5 +1,8 @@
 config BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS
 	bool
+	# -m32 flag is used for 32bit builds and host-luajit has
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	default y if BR2_i386 || \
 		(BR2_x86_64 && BR2_HOSTARCH='x86_64') || \
 		BR2_powerpc || BR2_arm || BR2_armeb || \

How is this going to prevent other packages from depending on host-luajit. BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS is all about the target variant of luajit, not the host variant.

Do we need a BR2_PACKAGE_HOST_LUAJIT_ARCH_SUPPORTS or something like that ?

For example, if you enable moarvm, host-luajit will be built, but not luajit.

Don't we have a problem here if your solution is used ?

Thanks!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
author
#12 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> writes:

Hi,

Quoted 10 lines
Quoted 6 lines
package/luajit/Config.in +3 -0
+	# -m32 flag is used for 32bit builds and host-luajit has
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"

default y if BR2_i386 || \
(BR2_x86_64 && BR2_HOSTARCH='x86_64') || \
BR2_powerpc || BR2_arm || BR2_armeb || \

How is this going to prevent other packages from depending on host-luajit. BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS is all about the target variant of luajit, not the host variant.

Correct.

Quoted 5 lines

Do we need a BR2_PACKAGE_HOST_LUAJIT_ARCH_SUPPORTS or something like that ?

For example, if you enable moarvm, host-luajit will be built, but not luajit.

Ahh, I had missed moarvm. Moarvm seems quite special as no other packages need host-luajit but no luajit on the target.

Looking at the upstream project, it doesn't seem to explicitly need host-luajit, just host-lua would do. From Configure.pl:

=item --lua=path/to/lua/executable
Path to a lua executable. (Used during the build when JIT is enabled).

This configure option is even dropped in 2017.10 with the following information in the changelog:

+ Removal of Configure.pl --lua and --has-dynasm options, compiling with these included 3rdparty libs is now required

Where the embedded lua copy is a tweaked lua-5.1.5:

https://github.com/MoarVM/dynasm/blob/d84e11714c9460bbb032de6cb1e06c3cb1c31f07/minilua.c

And indeed, moarvm still builds if moarvm.mk is changed to pull in host-lua and the --lua path is adjusted. Francois, is there a specific reason you went with host-luajit over host-lua?

So I would prefer to do that change instead of adding BR2_PACKAGE_HOST_LUAJIT_ARCH_SUPPORTS.

I'll send a patch for moarvm.

Signature · 1 line
Bye, Peter Korsgaard
#13 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

In reply to Peter Korsgaard
Quoted 2 lines · Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and host-luajit has limited architecture support, so limit to x86(-64) hosts.

I really don't see why this is needed. What we need is that the host and target
bitness is the same. On x86_64, we can always do this by compiling with -m32 (which is what we do in the .mk file). But I see no reason at all why building for a 32-bit target would not be possible on ARM, MIPS or PowerPC (32-bit).

That said, we can't easily test that and nobody cares anyway, so I've committed
with an updated commit message.

Regards,
Arnout

Quoted 23 lines

Fixes:
http://autobuild.buildroot.net/results/5f5b5edb058efe976c003678e21bcc28a87cc828/

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/luajit/Config.in | 3 +++
 1 file changed, 3 insertions(+)
package/luajit/Config.in +3 -0
index 1a27c434e1..6b9c6e6ae8 100644
@@ -1,5 +1,8 @@
 config BR2_PACKAGE_LUAJIT_ARCH_SUPPORTS
 	bool
+	# -m32 flag is used for 32bit builds and host-luajit has
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	default y if BR2_i386 || \
 		(BR2_x86_64 && BR2_HOSTARCH='x86_64') || \
 		BR2_powerpc || BR2_arm || BR2_armeb || \
Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
author
#14 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

Quoted 10 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Arnout" == Arnout Vandecappelle <[email protected]> writes:

Quoted 2 lines · Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and host-luajit has limited architecture support, so limit to x86(-64) hosts.

I really don't see why this is needed. What we need is that the host and target
bitness is the same. On x86_64, we can always do this by compiling with -m32 (which is what we do in the .mk file). But I see no reason at all why building for a 32-bit target would not be possible on ARM, MIPS or PowerPC (32-bit).

Correct, I opted for the simplest possible fix as building on !x86 really isn't a very realistic use case.

Quoted 2 lines

That said, we can't easily test that and nobody cares anyway, so I've committed
with an updated commit message.

Great, thanks!

Signature · 1 line
Bye, Peter Korsgaard
author
#15 lore raw

PATCH 3/4 luajit: only available on x86(-64) hosts

In reply to Peter Korsgaard
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Peter" == Peter Korsgaard <[email protected]> writes:

The -m32 compiler flag is used for 32bit builds and host-luajit has limited architecture support, so limit to x86(-64) hosts.

Fixes:
http://autobuild.buildroot.net/results/5f5b5edb058efe976c003678e21bcc28a87cc828/

Signed-off-by Peter Korsgaard <[email protected]>

Committed to 2017.02.x and 2017.08.x, thanks.

Signature · 1 line
Bye, Peter Korsgaard
author
#16 lore raw

PATCH 4/4 qt5webengine: only available on x86(-64) hosts

In reply to Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and the host tools have limited architecture support, so limit to x86(-64) hosts.

Signed-off-by Peter Korsgaard <[email protected]>
---
 package/qt5/qt5webengine/Config.in | 3 +++
 1 file changed, 3 insertions(+)
package/qt5/qt5webengine/Config.in +3 -0
index 6b68d1b2a8..d40b58062e 100644
@@ -3,6 +3,9 @@ config BR2_PACKAGE_QT5WEBENGINE_ARCH_SUPPORTS
 	default y if BR2_aarch64 || BR2_arm || \
 		BR2_i386 || BR2_x86_64 || \
 		BR2_mips || BR2_mips64
+	# -m32 flag is used for 32bit builds and host tools have
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE # qt5declarative
 	depends on !BR2_BINFMT_FLAT # qt5base-icu
 	depends on BR2_USE_MMU # libglib2, qt5base-dbus
Signature · 1 line
2.11.0
#17 lore raw

PATCH 4/4 qt5webengine: only available on x86(-64) hosts

Quoted 2 lines · Peter Korsgaard

The -m32 compiler flag is used for 32bit builds and the host tools have limited architecture support, so limit to x86(-64) hosts.

Same story here: there are combinations that should work, e.g. building for
x86_64 target on an aarch64 host. However, it's equally likely to break, and the Config.in expressions would be quite complicated to allow it. So I've applied after extending the commit message a little.

Regards,
Arnout

Quoted 21 lines
Signed-off-by Peter Korsgaard <[email protected]>
---
 package/qt5/qt5webengine/Config.in | 3 +++
 1 file changed, 3 insertions(+)
package/qt5/qt5webengine/Config.in +3 -0
index 6b68d1b2a8..d40b58062e 100644
@@ -3,6 +3,9 @@ config BR2_PACKAGE_QT5WEBENGINE_ARCH_SUPPORTS
 	default y if BR2_aarch64 || BR2_arm || \
 		BR2_i386 || BR2_x86_64 || \
 		BR2_mips || BR2_mips64
+	# -m32 flag is used for 32bit builds and host tools have
+	# limited architecture support
+	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
 	depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE # qt5declarative
 	depends on !BR2_BINFMT_FLAT # qt5base-icu
 	depends on BR2_USE_MMU # libglib2, qt5base-dbus
Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
author
#18 lore raw

cover Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues

In reply to Peter Korsgaard

Hmm, this apparently never made it to the list.

Quoted 8 lines · Peter Korsgaard

Hi,

The following patch series fixes various autobuilder issues from packages selecting BR2_HOSTARCH_NEEDS_IA32_* without ensuring hostarch is x86(-64), breaking the build on the gcc112 ppc64le autobuilder.

--
Bye, Peter Korsgaard

Signature · 1 line
Bye, Peter Korsgaard
#19 lore raw

cover Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues

Hi Peter,

Quoted 1 line · Peter Korsgaard

Hmm, this apparently never made it to the list.

I got the entire set.

It's archived at
http://lists.busybox.net/pipermail/buildroot/2017-November/205961.html.

Quoted 9 lines · Peter Korsgaard
Quoted 8 lines

Hi,

The following patch series fixes various autobuilder issues from packages selecting BR2_HOSTARCH_NEEDS_IA32_* without ensuring hostarch is x86(-64), breaking the build on the gcc112 ppc64le autobuilder.

--
Bye, Peter Korsgaard

Signature · 3 lines
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
author
#20 lore raw

cover Fix BR2_HOSTARCH_NEEDS_IA32_* autobuilder issues

Quoted 10 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Baruch" == Baruch Siach <[email protected]> writes:

Hi Peter,

Quoted 1 line · Peter Korsgaard

Hmm, this apparently never made it to the list.

I got the entire set.

It's archived at
http://lists.busybox.net/pipermail/buildroot/2017-November/205961.html.

Indeed it is, somehow I didn't see it.

Signature · 1 line
Bye, Peter Korsgaard