On Wed, Nov 04, 2009 at 12:36:01PM -0700, Nathaniel Echols wrote: > On Wed, Nov 4, 2009 at 11:58 AM, Daniel Macks <[email protected]> wrote: > > > Fink has an internal setting to allow propagation of the MAKEFLAGS > > shell environment variable into the build process (fink usually blanks > > this field as part of its environment-consistency policy). That way a > > user can decide what to do, but has to do it explicitly (and with > > knowledge that some packages may have build problems (but if they are > > reported, those packages can expliticly re-set -j1)). There's info on > > Fink Wiki I think. > > > > The first reply I got said that Fink wipes out all environment variables. > Whether or not this is the case, setting MAKEFLAGS has no impact on the > compilation of gcc44.
Yes, that's exactly what I said: you have to tweak the internal "wipe env vars" setting to allow MAKEFLAGS to propagate. First google hit for: fink makeflags tells you all about it (check the cached copy). However, IIRC, gcc* is a little special in its build system, not sure it's the best test case. dan -- Daniel Macks [email protected] http://www.netspace.org/~dmacks ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
