[tor-bugs] #4263 [Tor bundles/installation]: TBB on Mac OS X 10.5.8 fails to run
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Wed Mar 21 14:58:42 UTC 2012
#4263: TBB on Mac OS X 10.5.8 fails to run
--------------------------------------+-------------------------------------
Reporter: ioerror | Owner: erinn
Type: defect | Status: assigned
Priority: blocker | Milestone:
Component: Tor bundles/installation | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------------------------+-------------------------------------
Changes (by Sebastian):
* status: needs_review => assigned
Comment:
Replying to [comment:17 mijk]:
> Thanks for quick reply, Sebastian.
>
> Replying to [comment:16 Sebastian]:
> > Replying to [comment:15 mijk]:
> > > It is obvious that Vidalia is the cause of the problem. If is latest
Vidalia compiled different way, why not to compile it again - the same way
as it was compiled for TBB 2.2.35-5?
> >
> > Because it's not obvious what the problem is. It looks like the old
build options together with new Vidalia code produce the problematic
behaviour.
> >
>
> I think it '''is''' pretty obvious what's going on (ie machine used for
compiling got upgraded from 10.5 to 10.6+). It's common problem, check out
those articles for possible solutions:
> http://grauonline.de/wordpress/?p=71
> and
> http://software.intel.com/en-us/articles/running-an-intel-compiled-
binary-on-older-mac-os-x-system-gives-dyld-unknown-required-load-command-
0x80000022/
I can't comment on this. The build maintainer claims (and I have no reason
to not believe her) that the last working bundle was also built on 10.6.
> > > And another question: is this problem persisting for OS X 10.6 and
10.7 users or is it only 10.5.8 anomally?
> >
> > Yes, only 10.5 is affected.
>
>
> In this case, it is obvious that the application was incorrectly built
on OS X 10.6 (or newer) machine for a 10.5 machine. A developer can fix
this by considering three things:
>
> 1. Using the correct compiler parameters:
> {{{gcc-4.2 -mmacosx-version-min=10.5 -isysroot
/Developer/SDKs/MacOSX10.5.sdk}}}...
>
> 2. Using the correct linker settings (setting environment variable
'''before''' link command). This is required, so that the OS X 10.6 linker
will not use the loader command {{{'LC_DYLD_INFO_ONLY' (=0x80000022)}}},
because OS X 10.5 does not understand it.
>
> {{{
> export MACOSX_DEPLOYMENT_TARGET=10.5
> (or setenv MACOSX_DEPLOYMENT_TARGET=10.5)
> }}}
>
> #. When this is done, one can check if the application was correctly
built for OS X 10.5 by running 'otool':
>
> {{{otool -l binary}}}
>
> The correct binary should not contain any '{{{LC_DYLD_INFO_ONLY}}}' load
commands (only '{{{LC_DYLD_INFO}}}' commands).
>
> (see the rest in blog article http://grauonline.de/wordpress/?p=71)
Thanks for the lesson. Maybe instead of putting random bugs in
needs_review without actually providing patches, you could've checked out
the current way things are getting built? We do set backwards
compatibility options for 10.5.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4263#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list