Re: [Fink-devel] broken autogen

2015-01-31 Thread David Fang
Jack, Ahh, I responded too soon. Thanks for triaging this issue. Your fix looks like something I would have done. You have my permission to commit this fix. Fang > David, > I have posted packaging on fink tracking for autogen-5.18.4-1 > which passes 'fink -m' and properly generates fix

Re: [Fink-devel] broken autogen

2015-01-31 Thread David Fang
Jack, Odd. __scm.h should come from guile20-dev, which is listed as a bdep. Can you confirm its presence? Fang > David, > The current autogen-5.18.2-6 packaging produces a broken > autogen. While trying to regenerate the fix includes for a gcc > patch... > > https://gcc.gnu.org/ml

Re: [Fink-devel] broken autogen

2015-01-31 Thread Jack Howarth
David, I have posted packaging on fink tracking for autogen-5.18.4-1 which passes 'fink -m' and properly generates fixincludes in the gcc source tree. https://sourceforge.net/p/fink/package-submissions/4467/ The additional patchlet was required... Index: autogen.patch =

Re: [Fink-devel] broken autogen

2015-01-31 Thread Jack Howarth
David, So it appears that the coding.. -I* ) f=${1#-I} ends up setting $f to "/sw/include/guile/2.0 -I/sw/include -D_THREAD_SAFE" rather than the desired "/sw/include/guile/2.0". Jack On Sat, Jan 31, 2015 at 8:02 PM, Jack Howarth wrote: > David, > The autogen

Re: [Fink-devel] broken autogen

2015-01-31 Thread Jack Howarth
David, The autogen build on fink fails on this code in autoopts/mk-tpl-config.sh... scan_cflags() { libguiledir= while test $# -gt 0 do case "$1" in -I ) test -f $2/libguile/__scm.h && { libguiledir=$2 return 0

[Fink-devel] broken autogen

2015-01-31 Thread Jack Howarth
David, The current autogen-5.18.2-6 packaging produces a broken autogen. While trying to regenerate the fix includes for a gcc patch... https://gcc.gnu.org/ml/gcc-bugs/2015-01/msg03659.html I found that the fink autogen produces a broken fixincl.x while the MacPorts autogen 5.18.4 works fin

Re: [Fink-devel] xmlto-0.0.26-1

2015-01-31 Thread Dustin Cartwright
Jack, sorry for the slow reply. I haven't had time to look at the patch in detail, but the changes you suggest seem fine, so feel free to commit them. Dustin On Wed, Jan 28, 2015 at 4:24 PM, Jack Howarth wrote: > Dustin, > The recent giflib7 update created a circular dependency in the > bui

[Fink-devel] xerces-c31-3.1.1-1

2015-01-31 Thread Jack Howarth
Baba, The current xerces-c31 packaging fails to validate on Yosemite due to the Puma linkage bug in configure. I've checked in the following which fixes this issue, bumps the package to the newer 3.1.1 release from upstream and adds the missing InfoTest. Tested with 'fink -m' on 10.10.

[Fink-devel] libspatialite vs Puma linkage

2015-01-31 Thread Jack Howarth
Baba, I checked in the following to fix the fink validation error about -flat_namespace linkage being incorrectly used on Yosemite. Index: libspatialite5.info === RCS file: /cvsroot/fink/dists/10.7/stable/main/finkinfo/database/

Re: [Fink-devel] libdap11-shlibs-3.11.7-1 validation failure

2015-01-31 Thread Alexander Hansen
Yeah, they’ll need fixing. Thanks. > On Jan 31, 2015, at 9:04 AM, Jack Howarth wrote: > > Alexander, > The current libdap11-shlibs-3.11.7-1 packaging is failing fink > validation with... > > Error: > /sw/src/fink.build/root-libdap11-shlibs-3.11.7-1/sw/opt/libdap11/lib/libdap.11.dylib > ap

[Fink-devel] libdap11-shlibs-3.11.7-1 validation failure

2015-01-31 Thread Jack Howarth
Alexander, The current libdap11-shlibs-3.11.7-1 packaging is failing fink validation with... Error: /sw/src/fink.build/root-libdap11-shlibs-3.11.7-1/sw/opt/libdap11/lib/libdap.11.dylib appears to have been linked using a flat namespace. If this package BuildDepends on libtool2, make s

Re: [Fink-devel] transitioning python packages to framework builds

2015-01-31 Thread Daniel Johnson
> On Jan 30, 2015, at 9:18 PM, Jack Howarth wrote: > >if wx.Platform == "__WXMAC__": >msg = """This program needs access to the screen. > Please run with a Framework build of python, and only when you are > logged in on the main display of your Mac.""" This message i