On 02 Dec 2008, at 21:11, Hanspeter Niederstrasser wrote:
> Jean-François Mertens wrote:
>> Woke up, and checked again:
>> (In addition to previous amendments) :
>> 1)
>> Reduce the PatchScript to the single line:
>> sed -i.bak -e '\X/usr/libXd' SConstruct
>> (thus get in particular rid of the patch file _ that is what
>> caused your trouble
>> with libiconv _ once -L/usr/lib was removed)
>> 2) Add, in the beginning of the CompileScript :
>> export CPATH=%p/include
>
> Exporting CPATH now successfully links to /sw/lib/
> {libbz2,libiconv,libxml2}.dylib. However, there are still links
> to /usr/X11/lib/libcairo.2.dylib and /usr/X11/lib/libfontconfig.
> 1.dylib on 10.5.
>
> The list of linked packages is: atk1-shlibs bzip2-shlibs
> freetype219-shlibs glib2-shlibs gtk+2-shlibs libgettext3-shlibs
> libglade2-shlibs libiconv libxml2-shlibs pango1-xft2-ft219-shlibs
> (same list as yours except for cairo-shlibs and fontconfig2-shlibs).
>
> If instead of putting -L/usr/X11R6/lib -lX11 into LDFLAGS I use the
> previous editing of SConstruct to add fontconfig and x11 via
> pkgconfig, then I do link to /sw/lib/libcairo.dylib as we should
> (but not /sw/lib/fontconfig2/lib/fontconfig.dylib because that's
> there only for compat reasons on 10.5).
Right, this seems a question of pkgconfig _ too bad I can't test on
10.5 (and don't know exactly what's there..)
Before seeing if and what needs to be patched, could you try to get
paths completely safe :
1) In the beginning of the compilescript, add :
export PKG_CONFIG_PATH="%p/lib/pango-ft219/lib/pkgconfig:%p/lib/
fontconfig2/lib/pkgconfig:$PKG_CONFIG_PATH"
(as in almost all gnome-dependent pkgs since pangocairo)
2) Right that the "-L/usr/X11R6/lib" in LDFLAGS is a bit unsafe _
nothing guarantees it'll come at the end ..
Safer would be to remove it there (but not the -lX11), and to add for
full safety
SetLIBRARY_PATH:"%p/lib/pango-ft219/lib:%p/lib/fontconfig2/lib:%p/lib:
$/usr/X11R6/lib"
This comes then as a fallback at the end.
Best,
Jean-Francois
PS: I suppose that if CFLAGS are used it is because the buildsystem
doesn't respect CPPFLAGS,
or puts them in the wrong place ?
You could then use them, when all other issues are settled, to set
also some genuine CFLAGS
and CXXFLAGS _ like eg '-Os -Wall'
(The buildsystem seems to want to use '-O3' for a release, so to use
no optimisation at all looks
a bit extreme..)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
