Universal binary and dynamic lib problem
Universal binary and dynamic lib problem
- Subject: Universal binary and dynamic lib problem
- From: Mike Cooper <email@hidden>
- Date: Wed, 19 Jul 2006 14:28:10 -0700
I'm trying to convert our app to be a Universal binary and are seeing some
weird problem with the dynamic libraries we generate. They all have bogus
references to a library file "/var/tmp//XXXXXXX.out".
Here's a simple test case:
% cat xxx1.c
#include <stdio.h>
extern void SayHello(void)
{
printf("Say Hi\n");
}
% cc -c -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386 xxx1.c
-o xxx1.o
% cc -dynamiclib -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc
-g -o xxx1.dylib xxx1.o
% otool -L xxx1.dylib
xxx1.dylib:
/var/tmp//ccrOogGC.out (compatibility version 0.0.0, current version
0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.1.3)
% cc xxx1main.c xxx1.dylib -o xxx1
xxx1main.c: In function 'main':
xxx1main.c:7: warning: incompatible implicit declaration of built-in function
'exit'
% otool -L xxx1
xxx1:
/var/tmp//cc8uRO3z.out (compatibility version 0.0.0, current version
0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 88.1.6)
The /var/tmp//....out file is obviously some kind of temporary compiler file,
but I have no idea why it's being left as a reference. The above is based on
our reading of various apple.com docs like "Porting UNIX/Linux Applications to
Mac OS X".
Our app is make based and runs on numerous platforms so converting it to an
Xcode project is not an option.
This is all using Xcode 2.3 on MacOS 10.4.7 on an Intel mac.
Any suggestions would be most appreciated!
mike
_______________________________________________
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