According to what I've read, position-independent code is the default (and maybe only?) mode supported by PPC/Darwin, so -fPIC may be a no-op. But I'm not a gcc expert.
If you use -fast, then you need to use -fPIC to build shared libraries. That is in man gcc.
There's no way (and we're probably not going to design a way) to have users pass arbitrary flags into the package compiling routine. That's because one of our basic tenets is "the result of compiling a given package name/version/revision must always be the same".
I think that's lame, but it isn't as lame as me starting my own porting project. So, I guess I'll take it! :)
There are, of course, many ways you can do it. Easiest would be to run a script on the .info files to add the SetCFLAGS line (or append to a pre-existing one). Less easy (but avoids having to merge your changes with newer .info releases) is to hack your local fink itself. It's "just" a perl script...visit /sw/lib/perl5/Fink/PkgVersion.pm, the set_env() method around line 2418. Maybe you'd want to not clean certain vars from the env, or pass via fink-specific env vars (FINK_CFLAGS?) or just hard-code your prefs.
Thanks for the tips! I will take that to heart and get back to you on how it works out.
Steve
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
