Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4
The issue of build failures from development libraries in /usr/local seems to come up endlessly. I have wondered if there is some way that a 'strict' build mode could be introduced into fink. The idea would be for packages known to commonly suffer from this issue, the info file could invoke a strict mode during the fink build process where fink would first look for headers or static libraries in /usr/local. If found, the build would abort with a clear message that /usr/local needs to be moved aside. Unless the package maintainer included the strict build keyword in the info file, this check would not normally occur. Jack -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4
Jack Howarth wrote: > The issue of build failures from development libraries > in /usr/local seems to come up endlessly. I have wondered > if there is some way that a 'strict' build mode could be > introduced into fink. The idea would be for packages known > to commonly suffer from this issue, the info file could > invoke a strict mode during the fink build process where > fink would first look for headers or static libraries in > /usr/local. If found, the build would abort with a clear > message that /usr/local needs to be moved aside. Unless > the package maintainer included the strict build keyword > in the info file, this check would not normally occur. Can't the package itself just do this on its own during CompileScript? if -e /usr/local/include/evil.h ; echo "you need to move /usr/local" ; exit 1 No need to add extra code to fink and have it maintain an ever growing list of possibly offending headers/libraries. Hanspeter -- Hanspeter Niederstrasser hanspeter AT snaggledworks DOT com -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4
Hanspeter, I wasn't proposing a check for a specific list of files but rather as simple option of a strict build mode which would abort if any *.h or *.a files existed inside of /usr/local. Jack -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4
Jack Howarth wrote: >I wasn't proposing a check for a specific list > of files but rather as simple option of a strict > build mode which would abort if any *.h or *.a > files existed inside of /usr/local. Jack Howarth earlier wrote: > The idea would be for packages known > to commonly suffer from this issue, the info file could > invoke a strict mode during the fink build process where > fink would first look for headers or static libraries in > /usr/local That's what I read this as, but regardless, instead of doing "if -e /usr/local/include/evil.h", a package could just as easily just see if there' _a_ file in /usr/local and crash out. The end result is the same, though. The possibilities mentioned so far are 1) add code into Fink to have a 'strict' tag, followed by 2) have packages susceptible to bad files be marked 'Strict: true', or A) have packages susceptible to bad files add a quick check into CompileScript. The 2nd path seems a heck of a lot easier and can be done by any maintainer, plus it's probably more flexible. Hanspeter -- Hanspeter Niederstrasser hanspeter at snaggledworks.com -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
