[oe] bitbake base-image: gmp-native: ERROR: function do_configure failed: configure: error: Oops, mp_limb_t is 32 bits, but the assembler code
Paul Menzel
paulepanter at users.sourceforge.net
Mon Nov 23 21:19:45 UTC 2009
Am Donnerstag, den 19.11.2009, 11:45 +0000 schrieb Richard Purdie:
> On Thu, 2009-11-19 at 12:10 +0100, Paul Menzel wrote:
> > Am Donnerstag, den 19.11.2009, 00:17 +0000 schrieb Richard Purdie:
> > > On Thu, 2009-11-19 at 00:21 +0100, Paul Menzel wrote:
> > > [...]
> > > > well, unfortunately my search results did not include any hits from the
> > > > OE bug tracker. I looked there a moment ago and found bug #3470 which
> > > > seems to be related to my problem [5].
> > > >
> > > > I will try to update it with the information from my messages to the
> > > > list in the next days.
> > > [...]
> > > > > > [2] oe/angstrom-dev/work/x86_64-linux/gmp-native-4.2.4-r0/temp$ less log.do_configure.29183
> > >
> > > I saw this recently, I wish I could remember how I fixed it :/.
> > >
> > > I looked back at the above log and it says:
> > >
> > > checking whether to build shared libraries... yes
> > > checking whether to build static libraries... yes
> > > checking for ld used by g++... ld -m elf_i386
> > > checking if the linker (ld -m elf_i386) is GNU ld... yes
> > > checking whether the g++ linker (ld -m elf_i386) supports shared libraries... yes
> > > checking for g++ option to produce PIC... -fPIC -DPIC
> > > checking if g++ PIC flag -fPIC -DPIC works... yes
> > >
> > > and the i386 references above show configure is off the rails before it
> > > hits the fatal error.
> > >
> > > Do you have the config.log file from the broken builds?
> >
> > Here you go.
>
> So just to be clear, you don't have any 64 bit userspace, just a 32 bit
> one? Running gcc to compile something gives you a 32 bit binary, not a
> 64 bit one?
That is correct.
$ dpkg --print-architecture
i386
> I'd try adding:
>
> BUILD_ARCH = "i686"
> BUILD_OS = "linux"
>
> to your local.conf
That worked perfectly. Thank you!
I do not know how to proceed with #3470 though. Can it be closed as
won’t fix and a note added to the FAQ?
Bests,
Paul
[5] http://bugs.openembedded.net/show_bug.cgi?id=3470
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20091123/4c8ef9c2/attachment-0002.sig>
More information about the Openembedded-devel
mailing list