Closed
Bug 1212362
Opened 9 years ago
Closed 6 years ago
Broken toolchain on emulator-x86-l
Categories
(Firefox OS Graveyard :: Emulator, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: tzimmermann, Unassigned)
References
Details
Attachments
(1 file)
7.88 KB,
text/x-log
|
Details |
Trying to build emulator-x86-l results in
> configure: error: installation or configuration problem: C compiler cannot create executables.
Building emulator-l (i.e., the same for ARM) works.
Reporter | ||
Updated•9 years ago
|
Blocks: b2g-emulator
Reporter | ||
Comment 1•9 years ago
|
||
Hi Juan, do you have an idea what might be wrong here? (I'm asking you because you work on toolchains.)
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(jgomez)
Comment 3•9 years ago
|
||
Well, this usually happens when trying to build for an architecture but mixing different architectures in the process. I've never built x86 emulator in any of his flavors (jb,kk,lollipop), but I'll assume that we are trying to build a 32 bit emulator, but using a toolchain which is targeted to build for x86-64 bit architecture by default, so is mixing both architectures in the process. I'll try to build it by myself and figure out where the problem is.
Flags: needinfo?(jgomez)
Comment 4•9 years ago
|
||
Yeah, confirmed. Looks like we need a -m32 flag anywhere in the configure.in script.
Reporter | ||
Comment 5•9 years ago
|
||
I tried to follow the advice in bug 1173590 and set -m32 in .userconfig, but this didn't help.
Comment 6•9 years ago
|
||
Oh, it should work. CXXFLAGS=-m32 ASFLAGS=-m32 CFLAGS=-m32 LDFLAGS=-m32 It's working for me. Anyway, this is just a workaround. I think that we should include these flags into the configure scripts depending on the target - i686-android-linux in this case.
Reporter | ||
Comment 7•9 years ago
|
||
Thanks, I'll try again. Maybe I forgot to set LDFLAGS.
Comment 8•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•