Skip to contentSkip to conversation

New: libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

Buildroot bugzilla at busybox.net 1 participant 6 messages Nov 29, 2015 – Nov 30, 2015

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=8491

Summary: libglib2 2.46.1 not Building for armv5 on 2015.11-rc3
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: brandurs at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0

When configure runs..
configure: WARNING: unrecognized options: --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6

when building..
CC libglib_2_0_la-gthread.lo
/tmp/.private/root/ccSdfBdl.s: Assembler messages:
/tmp/.private/root/ccSdfBdl.s:1010: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#3' /tmp/.private/root/ccSdfBdl.s:1010: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#13' /tmp/.private/root/ccSdfBdl.s:1011: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#29' /tmp/.private/root/ccSdfBdl.s:1011: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#19' /tmp/.private/root/ccSdfBdl.s:1012: Error: lo register required -- `orr r10,r10,r10'
Makefile:2087: recipe for target 'libglib_2_0_la-gslice.lo' failed

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 8491] libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

https://bugs.busybox.net/show_bug.cgi?id=8491

Yann E. MORIN <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |yann.morin.1998 at free.fr

--- Comment #1 from Yann E. MORIN <[email protected]> 2015-11-29 21:31:18 UTC --- Hello,

Thanks for your report!

However, I can not reproduce that build failure.
Here's my defconfig:

BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_LIBGLIB2=y

This selects an arm926t CPU, which is an armv5. And libglib2 builds correctly here.

Care to share your defconfig, please?

Regards,
Yann E. MORIN.

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#2 lore raw

[Buildroot] [Bug 8491] libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=8491

--- Comment #2 from Peter Korsgaard <[email protected]> 2015-11-29 21:52:14 UTC --- (In reply to comment #1)

Quoted 7 lines

Hello,

Thanks for your report!

However, I can not reproduce that build failure.
Here's my defconfig:

Quoted 6 lines

BR2_arm=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_NONE=y
BR2_SYSTEM_BIN_SH_NONE=y
# BR2_PACKAGE_BUSYBOX is not set
BR2_PACKAGE_LIBGLIB2=y

Based on the error message, the reporter was most likely building with thumb1 mode.

And indeed, it fails here as well with that config + BR2_ARM_INSTRUCTIONS_THUMB=y

CC libglib_2_0_la-gstringchunk.lo
/tmp/ccSVEXME.s: Assembler messages:
/tmp/ccSVEXME.s:587: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#3'
/tmp/ccSVEXME.s:587: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#13'
/tmp/ccSVEXME.s:588: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#29'
/tmp/ccSVEXME.s:588: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- `mov r12,r12,ror#19'
/tmp/ccSVEXME.s:589: Error: lo register required -- `orr r10,r10,r10' Makefile:2087: recipe for target 'libglib_2_0_la-gslice.lo' failed

I guess we'll need to force -marm for libglib2.

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#3 lore raw

[Buildroot] [Bug 8491] libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=8491

--- Comment #3 from Peter Korsgaard <[email protected]> 2015-11-29 21:54:09 UTC --- (In reply to comment #0)

Quoted 4 lines

When configure runs..
configure: WARNING: unrecognized options: --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6

Quoted 12 lines

when building..
CC libglib_2_0_la-gthread.lo
/tmp/.private/root/ccSdfBdl.s: Assembler messages:
/tmp/.private/root/ccSdfBdl.s:1010: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#3' /tmp/.private/root/ccSdfBdl.s:1010: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#13' /tmp/.private/root/ccSdfBdl.s:1011: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#29' /tmp/.private/root/ccSdfBdl.s:1011: Error: shifts in CMP/MOV instructions are only supported in unified syntax -- mov r12,r12,ror#19' /tmp/.private/root/ccSdfBdl.s:1012: Error: lo register required -- `orr

That TMPDIR seems to indicate that you are building as root. PLEASE don't do that. One of the most basic features of Buildroot is that you don't need to be root (and no guarantees are given that it will behave sanely if you DO run it as root).

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#4 lore raw

[Buildroot] [Bug 8491] libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=8491

--- Comment #4 from Thomas Petazzoni <[email protected]> 2015-11-29 22:59:21 UTC --- (In reply to comment #2)

Quoted 1 line

I guess we'll need to force -marm for libglib2.

The assembly code in question comes from glib/valgrind.h, but unfortunately, I don't see a way of disabling valgrind "support" from glib.

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
#5 lore raw

[Buildroot] [Bug 8491] libglib2 2.46.1 not Building for armv5 on 2015.11-rc3

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=8491

Peter Korsgaard <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #5 from Peter Korsgaard <[email protected]> 2015-11-30 07:24:17 UTC --- Fixed in git by:

commit 26013972ce568e55a121c21a55afce45bc0675e9

Author: Peter Korsgaard <[email protected]>
Date:   Mon Nov 30 08:19:59 2015 +0100

libglib2: force arm mode when building with thumb1

Fixes #8491

glib/valgrind.h contains inline asm not compatible with thumb1, so build it in arm mode:

CC libglib_2_0_la-gstringchunk.lo
/tmp/ccSVEXME.s: Assembler messages:
/tmp/ccSVEXME.s:587: Error: shifts in CMP/MOV instructions are only
supported
in unified syntax -- `mov r12,r12,ror#3' /tmp/ccSVEXME.s:587: Error: shifts in CMP/MOV instructions are only
supported
in unified syntax -- `mov r12,r12,ror#13' /tmp/ccSVEXME.s:588: Error: shifts in CMP/MOV instructions are only
supported
in unified syntax -- `mov r12,r12,ror#29' /tmp/ccSVEXME.s:588: Error: shifts in CMP/MOV instructions are only
supported
in unified syntax -- mov r12,r12,ror#19' /tmp/ccSVEXME.s:589: Error: lo register required -- orr r10,r10,r10' Makefile:2087: recipe for target 'libglib_2_0_la-gslice.lo' failed

Signature · 3 lines
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.