On Sat, May 01, 2004 at 11:02:23PM -0700, Darkwing wrote: > >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. > > > > I modified set_env and have limited success. What I need to know now is > how do I tell if the package I'm compiling is a lib or not?
Heh. Env vars during ./configure are a pretty coarse-grained control anyway. A lot of packages are both shared libs and a user-land programs, but they all share a single configuration. To a first approximation, could you just detect the presence of various libtool support programs (ltmain.sh in the top-level directory perhaps)? > I don't want to use -fPIC unless I need it, and -fast includes > -mdynamic-no-pic. Or, if -fPIC has no performance hit, then I might > as well just turn it back on. Test it, man. We can hand-wave all day about what is *supposed* to happen and what we'd *expect* to matter or not... dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- 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
