[PD-dev] Mac OS X 10.5 vs zexy's autogen.sh

[Hans-Christoph Steiner]

On Wed, 2011-10-05 at 22:42 +0200, IOhannes m zmölnig wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 10/05/2011 10:04 PM, Hans-Christoph Steiner wrote:
> > On Wed, 2011-10-05 at 21:42 +0200, IOhannes m zmölnig wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> On 10/05/2011 09:18 PM, Hans-Christoph Steiner wrote:
> >>>
> >>> On Oct 5, 2011, at 12:45 PM, IOhannes m zmoelnig wrote:
> >>>
> >>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>> Hash: SHA1
> >>>>
> >>>> On 2011-10-05 18:16, Hans-Christoph Steiner wrote:
> >>>>>
> >>>>> On Oct 5, 2011, at 4:05 AM, IOhannes m zmoelnig wrote:
> >>>>>
> >>>>> The logfile I see says its set to:
> >>>>>
> >>>>> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin
> >>>>>
> >>>>> http://autobuild.puredata.info/auto-build/2011-10-05/logs/2011-10-05_03.15.09_darwin_macosx105-i386_pd-extended.txt
> >>>>>
> >>>>
> >>>> the same logfiles also says:
> >>>> PATH: /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin
> >>>
> >>> Ah, I see, where you post it in zexy/autogen.sh.  But the build
> >>> environment has:
> >>>
> >>> PATH=/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin
> >>>
> >>
> >> yes, i was trying to explain that (zexy's, but also Pd's) autogen.sh
> >> prepends the /sw/bin/ to the path manually.
> >>
> >>
> >>>> which suggests that your libtool setup is broken :-)
> >>>>
> >>>> you could try comparing the ./libtool generated on your machine and the
> >>>> one generated on the PdLab machine.
> >>>
> >>> seems so, I did a reinstall and 'svn up' and it now builds on my machine.
> >>
> >>
> >> ah cool
> >> so at least OSX world is happy again :-)
> > 
> > Its closer, but not quite there, the build this afternoon failed again
> > on the same thing:
> > 
> 
> not quite.
> zexy finished fine!
> but it failed when building Gem (from which zexy inherited its
> autogen.sh script)
> 
> it's fixed in Gem's git, though not in Gem's svn.
> 
> i really wonder why the problems appear now, as the relevant script has
> been in use for several months now)

Perhaps your zexy scripts are modifying the build environment?  It first
calls "make all" on everything, which would run the ./autogen.sh
scripts, then it runs "make install".  Just a guess.

.hc