Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4

2009-10-03 Thread Hanspeter Niederstrasser
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

Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4

2009-10-02 Thread Jack Howarth
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 b

Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4

2009-10-02 Thread Hanspeter Niederstrasser
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, th

Re: [Fink-devel] Fink update all failed compiling gcc 4.4.4

2009-10-01 Thread Jack Howarth
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 str