Re: glibtool question
Re: glibtool question
- Subject: Re: glibtool question
- From: plumber Idraulico <email@hidden>
- Date: Tue, 6 Dec 2005 10:12:30 +0100
Hi, Peter
I just committed changes to gnu libtool to allow the -isysroot flag
through
to gcc unmolested. However I did do some work on older libtool-1.5.x
...
CC="cc -arch ppc -arch i386 -isysroot=/path"
CXX="c++ -arch ppc -arch i386 -isysroot=/path"
CPP="cc -E"
CXXCPP="g++ -E"
Note that you need an automake newer than Apple ships. Latest is
1.9.6, I
think 1.8.2 or so started adding the --tag argument for glibtool.
yes i'm right with u but it's not yet very useful ( i've already
updated )
(and many projects are not well maintained missing makefile.am
configure.in ..... ( not in CVS ???))
imagine something like this
$SDK_DARWIN8
here libSystem.dylib with _newsymbol
$SDK_DARWIN7
here libSystem.dylib
now you have an application configure that tests _newsymbol or not
(conditionnal)
if don't want that your configure script catchs _newsymbol
you have to make something like that
./configure CC="${CC} $SDK_DARWIN7/usr/lib/libSystem.dylib"
to force configure-test to catch only the symbols in this lib
there are many others examples it's for that i said "it's not yet
very useful"
(
i don't explain here the problems with the linkage of some lib like
that ../../../libmy.dylib ...
CC="${CC} $PROJECT_SDK/usr/lib/libSystem.dylib $PROJECT_SDK/usr/lib/
libmx.dylib ${LD_X86}"
)
i've made my own tool
now i can compile against these targets from (Tiger-ppc)
gcc-3.5 ( without lmx )
-> /Developer/SDKs/Darwin7u.sdk arch x86
-> /Developer/SDKs/Darwin7u.sdk arch ppc
(including X11 FAT)
gcc-4
-> /Developer/SDKs/Darwin8u.sdk arch x86
-> /Developer/SDKs/Darwin8u.sdk arch ppc
(including X11 FAT)
gcc-4
-> /Developer/SDKs/Darwin8u.sdk arch x86
-> /Developer/SDKs/Darwin8u.sdk arch ppc
in fact is useful for me because i've stopped to run darwin-x86
with my freeBSD ( i need it for my work )
so i can compile in local from the OSX-ppc and test on the gnu-
darwinx86 server
_m.o foo.c
imac:~/foo peter$ cc -fno-pic -c -o foo_nopic.o foo.c
...
ld: foo_nopic.o has local relocation entries in non-writable section
yes i've tested but it wasn't clear
i've misunderstood about PIC (position independent code)
in fact, i made this (automatically without really understand)
it's for my culture :)
ok , so i can sum like that
--NOT NEED PIC--
ar rc libMy.a *.non-pic.o
gcc -dynamiclib *.pic.o \
-install_name /usr/local/lib/ libMyOther.1.dylib \
-compatibility_version 1
-current_version 1.3
-o libMyOther.1.0.dylib \
-lz ./libMy.a
--NEED PIC--
ar rc libMy.a *.pic.o
gcc \
-dynamiclib \
-undefined suppress \
-flat_namespace \
-single_module \
-all_load ./libMy.a \
-install_name /usr/local/lib/libMy.1.dylib \
-compatibility_version 1
-current_version 1.3
-o libMy.1.0.dylib \
-lz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden