On Tuesday, Nov 5, 2002, at 01:54 Europe/Brussels, Ben Hines wrote:
Thanks for the useful tips.On Monday, November 4, 2002, at 02:18 PM, Max Horn wrote:The fix that should be applied for now (if possible) is to make the package *not* use -Werror. After all, the source is the same everywhere and known to work (at least in theory :-), so there is no point in doing extensive compile time checking anyway.Or, if possible get the packages not to pass -I/sw/include at all. Then it will only be a system directory, and no warning will occur.
For nget that came out tonight, the build broke at the configure stage because of conftests
that relied explicitly on putting themselves '-Werror' (in 'checking recv ARG2'), so the
first fix couldn't be used, but replacing "--with-pcre-prefix=%p" by "--with-pcre" in the
ConfigureParams solved the problem by getting rid of all -I/sw/include flags.
(Also, the BuildDepends autoconf25 seems superfluous...)
As an organisational matter, what to do with such package-specific notes ? Clearly a
large number of maintainers don't use cvs-fink. Just send the notes to the maintainer
so he can keep them for when (and if..) fink changes? Might lead to some duplication
of efforts among those that do. On the other hand, one should probably not clutter the
list with such notes. Maybe systematically cc'ing to .... the reports to maintainers ?
Jean-Francois
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
