[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9829 [Tor bundles/installation]: Firefox ESR 24 does need a newer compiler than gcc 4.2

#9829: Firefox ESR 24 does need a newer compiler than gcc 4.2
------------------------------------------+-------------------------------
     Reporter:  gk                        |      Owner:  erinn
         Type:  defect                    |     Status:  new
     Priority:  normal                    |  Milestone:
    Component:  Tor bundles/installation  |    Version:
   Resolution:                            |   Keywords:  tbb-3.0, ff24-esr
Actual Points:                            |  Parent ID:  #9827
       Points:                            |
------------------------------------------+-------------------------------

Comment (by gk):

 Replying to [comment:36 gk]:
 > Replying to [comment:35 mingwandroid]:
 > > I also tested compiling just this .cc file (outside of the gitian
 build system, in fact, just a basic test from the commandline:
 > > {{{
 > > /c/x/dx-i686-3_3/bin/i686-apple-darwin11-clang++
 /home/ubuntu/ESR24-work/mozilla-esr24/toolkit/crashreporter/google-
 breakpad/src/common/mac/arch_utilities.cc --sysroot ~/MacOSX10.6.sdk
 -I/home/ubuntu/ESR24-work/mozilla-esr24/toolkit/crashreporter/google-
 breakpad/src/ -c
 > > }}}
 > > .. and that worked. You'll notice I used a GCC built as darwin11, but
 that *shouldn't* matter.
 >
 > Well, the files are there. The problem is that this particular file is
 compiled with the host C++ compiler. And passing the proper include path
 to it seems harder than I thought. I need to look deeper at the problem...

 I found a workaround: I disabled compiling that part of the code. That is
 fine for now as we already disable building the crashreporter and the
 (problematic) parts that are even build in this case are used for
 profiling which is not enabled in TBB. If I manage to include the path to
 the missing header files at all other parts of the build are blowing up
 complaining about missing symbols when linkning. I probably talk to some
 Mozilla build folks about this in order to get it solved properly. But
 what worries me more is the next failure: linking libxul fails with
 {{{
 ld: in ../../dom/bindings/SVGFilterElementBinding.o, can't map file,
 errno=12 for architecture i386
 i686-apple-darwin10-clang: error: linker command failed with exit code 1
 (use -v to see invocation)
 }}}
 First, that fails both in gitian and without a VM with the same error
 message. Second, I still have enough memory for linking (startpaging a bit
 it was suggested that 'errno=12' occurs if memory is missing; not sure
 about that, though). Third, the build with a clang 3.3 on a Mac with half
 of the memory my build machine has is completing properly. Thus, that
 might be an issue with the cross-compiling toolchain. Anyway, pointers for
 debugging this further (and fixing it) are greatly appreciated.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9829#comment:37>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs