warning: object file compiled with -mlong-branch
warning: object file compiled with -mlong-branch
- Subject: warning: object file compiled with -mlong-branch
- From: Stephen Kay <email@hidden>
- Date: Tue, 27 Nov 2012 19:00:08 -0500
- Thread-topic: warning: object file compiled with -mlong-branch
Using Xcode 3.2.6 on 10.6.8 intel, building against the 10.4u SDK, for a
universal binary. I'm receiving the following two warnings when linking:
ld: warning: object file compiled with -mlong-branch which is no longer
needed. To remove this warning, recompile without -mlong-branch:
/Xcode3.2.6/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o
ld: warning: object file compiled with -mlong-branch which is no longer
needed. To remove this warning, recompile without -mlong-branch:
/Xcode3.2.6/usr/bin/../lib/gcc/powerpc-apple-darwin10/4.0.1/crt3.o
Searching for info, I came across this advice:
=============================
http://lists.apple.com/archives/xcode-users/2009/Sep/msg00209.html
The Snow Leopard version of the 10.4u SDK seems to contain an outdated
version of crt1.o. You can fix the linker warning on your own by recompiling
the Csu package from the Tiger sources; the 10.4.11 x86 sources already have
the correct compiler flags (without -mlong_branch):
Download http://www.opensource.apple.com/release/mac-os-x-10411x86 => Csu-71
(http://www.opensource.apple.com/tarballs/Csu/Csu-71.tar.gz).
Unzip the archive.
In the Csu-71 directory, execute make RC_ARCHS="ppc ppc64 i386 x86_64"
Replace /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o with the newly
created version.
=============================
OK, even though that would only deal with one of the errors, I tried that.
Now when linking it gives this error:
ld: bl out of range (36908448 max is +/-16M) from __start at 0x00020E38 in
__text of /Xcode3.2.6/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o to
___darwin_gcc3_preregister_frame_info at 0x02353CBC in __common of
/Xcode3.2.6/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o in __start from
/Xcode3.2.6/SDKs/MacOSX10.4u.sdk/usr/lib/crt1.o
So, I put the old file back and I'm back where I was. Do I need to worry
about these two warnings, and is there any way to fix them and make them go
away?
Thanks,
- Stephen
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Stephen Kay
Karma-Lab :: developers of KARMA
http://www.karma-lab.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden