Since I inadvertently blew away Xcode 3.0 while installing the
iPhoneSDK, I'm interested in potential drawbacks. On an intel MBP,
ld -v gives:
@(#)PROGRAM:ld PROJECT:ld64-82.5
compared to ld-64-77 on my Xcode 3.0 ppc G5
For me the results are:
xCode3:
@(#)PROGRAM:ld PROJECT:ld64-77
Koen van der Drift wrote:
Hi,
I get the following error (after a fink selfupdate):
...
tree-inline.o dummy-checksum.o main.o libbackend.a ../libcpp/
libcpp.a ../libdecnumber/libdecnumber.a ../libcpp/libcpp.a -lintl -L/
sw/lib -liconv ../libiberty/libiberty.a ../libdecnumber/
On Mar 14, 2008, at 3:14 AM, Martin Costabel wrote:
Not sure if relevant, but I recently installed the iPhone SDK with
an updated xCode.
This could very well be the case. What do you get from ld -v?
As recommended by Jack (offline), I deleted xCode for iPhone, and
reinstalled xCode 3
On Mar 14, 2008, at 3:14 AM, Martin Costabel wrote:
Koen van der Drift wrote:
Hi,
While I agree with your ld that this linker line is redundant, because
it includes tree-inline.o twice, once directly and once via
libbackend.a, my ld does not complain about duplicate symbols.
[]
Not sure
Hi,
I get the following error (after a fink selfupdate):
...
cp/cp-lang.o stub-objc.o cp/call.o cp/decl.o cp/expr.o cp/pt.o
cp/typeck2.o cp/class.o cp/decl2.o cp/error.o cp/lex.o cp/parser.o cp/
ptree.o cp/rtti.o cp/typeck.o cp/cvt.o cp/except.o cp/friend.o cp/
init.o
