Fix for 638056 breaks MeeGo armv7 build

RESOLVED FIXED in mozilla6

Status

defect
--
major
RESOLVED FIXED
8 years ago
Last year

People

(Reporter: lokesh.kumar.goel, Assigned: glandium)

Tracking

Trunk
mozilla6
ARM
MeeGo
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 3 obsolete attachments)

Posted file Full Error Log
PACKAGE VERSION:
mozilla-central 68416:59771590e920

ENVIRONMENT:
MeeGo(rpmbuild) armv7el

Looks like the patch for bug#638056 breaks the armel build for MeeGo. See the errors below:

/usr/bin/python2.6 /home/abuild/rpmbuild/BUILD/mozilla-central/js/src/config/pythonpath.py -I../config /home/abuild/rpmbuild/BUILD/mozilla-central/js/src/config/expandlibs_exec.py --uselist --  c++ -o js  -frtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -fmessage-length=0 -march=armv7-a -mtune=cortex-a8 -mlittle-endian -mfpu=vfpv3 -mfloat-abi=softfp -D__SOFTFP__ -fno-strict-aliasing -pthread -march=armv5te -mthumb-interwork -msoft-float -pipe  -DNDEBUG -DTRIMMED -g -g -O2 -fno-tree-ter -fno-ipa-reference -fno-tree-switch-conversion  js.o jsworkers.o   -lpthread -Wl,--no-keep-memory,-rpath-link,/home/abuild/rpmbuild/BUILD/release/dist/bin/:/usr/lib:/lib   -Wl,-rpath-link,/bin -Wl,-rpath-link,/home/abuild/rpmbuild/BUILD/release/dist/lib  -L../../../dist/bin -L../../../dist/lib -L/usr/lib -lplds4 -lplc4 -lnspr4 -lpthread -ldl ../editline/libeditline.a ../libjs_static.a -ldl     
../libjs_static.a(jsapi.o): In function `~ExecutablePool':
/home/abuild/rpmbuild/BUILD/mozilla-central/js/src/assembler/jit/ExecutableAllocator.h:128: undefined reference to `JSC::ExecutablePool::systemRelease(JSC::ExecutablePool::Allocation const&)'

Also find attached the full rawlog of the build and the mozconfig used.
Posted file Mozconfig used
Reversing 68416:59771590e920 fixes the issue.
Severity: normal → major
What is TARGET_CPU on meego ? armel ?
(In reply to comment #3)
> What is TARGET_CPU on meego ? armel ?

YES
Assignee: nobody → mh+mozilla
Attachment #528272 - Flags: review?(cdleary)
(In reply to comment #5)
> Created attachment 528272 [details] [diff] [review]
> Add armel in the opt-in for the nitro assembler
I am sorry, but this fix doesn't solve the problem. I tried this and it doesn't fix the issue.

We build for two arm architectures in MeeGo armv7el(softfp) and armv8el(hardfp), the TARGET_CPU for MeeGo armv7el target seems to be "armv7l".
"armv7l" is the TARGET_CPU for both armv7el and armv8el. armv8el is actually armv7el + hardfp.
Even better
Attachment #528272 - Attachment is obsolete: true
Attachment #528429 - Attachment is obsolete: true
Attachment #528435 - Attachment is obsolete: true
Attachment #528272 - Flags: review?(cdleary)
Attachment #528437 - Flags: review?(cdleary)
Attachment #528437 - Flags: review?(cdleary) → review+
http://hg.mozilla.org/mozilla-central/rev/c833fb1623ca
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla6
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.