FYI:
http://autobuild.puredata.info/auto-build/2011-10-02/logs/2011-10-02_03.15.2...
cd /Users/pd/auto-build/pd-extended/externals/zexy && ./autogen.sh PATH: /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:4: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:4: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:4: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:4: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: /usr/bin/autoconf failed with exit status: 63 make[2]: *** [/Users/pd/auto-build/pd-extended/externals/zexy/ configure] Error 63
.hc
----------------------------------------------------------------------------
You can't steal a gift. Bird gave the world his music, and if you can hear it, you can have it. - Dizzy Gillespie
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-02 22:27, Hans-Christoph Steiner wrote:
FYI:
http://autobuild.puredata.info/auto-build/2011-10-02/logs/2011-10-02_03.15.2...
hmm, i cannot reach this machine anymore...
cd /Users/pd/auto-build/pd-extended/externals/zexy && ./autogen.sh PATH: /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to.
hmm, very weird. we are using autoreconf to (re)generate the files. autoreconf calls aclocal and autoconf, and it seems it calls an aclocal that is not compatible with the autoconf it uses. could this be a find vs apple problem?
If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:4: error: Autoconf version 2.62 or higher is required
i don't know why autoconf>=2.62 is required. the minimum required version of autoconf has never been specified within zexy.
anyhow, to get rid of some other nastities, i have updated my configure.ac and now it generates and configures without problems on my 10.5.8-ppc machine, which comes with autoconf-2.61
fgmasdr IOhannes
On Oct 3, 2011, at 5:06 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-02 22:27, Hans-Christoph Steiner wrote:
FYI:
http://autobuild.puredata.info/auto-build/2011-10-02/logs/2011-10-02_03.15.2...
hmm, i cannot reach this machine anymore...
Yeah, it seems to be down, I'll check it tomorrow.
cd /Users/pd/auto-build/pd-extended/externals/zexy && ./autogen.sh PATH: /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to.
hmm, very weird. we are using autoreconf to (re)generate the files. autoreconf calls aclocal and autoconf, and it seems it calls an aclocal that is not compatible with the autoconf it uses. could this be a find vs apple problem?
If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:4: error: Autoconf version 2.62 or higher is required
i don't know why autoconf>=2.62 is required. the minimum required version of autoconf has never been specified within zexy.
anyhow, to get rid of some other nastities, i have updated my configure.ac and now it generates and configures without problems on my 10.5.8-ppc machine, which comes with autoconf-2.61
I don't really know why this is happening, but I do know that the ./ autogen.sh in pure-data.git and pd-extended.git works everywhere since it is used in the builds every night. Why not just use that one?
.hc
----------------------------------------------------------------------------
"[T]he greatest purveyor of violence in the world today [is] my own government." - Martin Luther King, Jr.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
I don't really know why this is happening, but I do know that the ./autogen.sh in pure-data.git and pd-extended.git works everywhere since it is used in the builds every night. Why not just use that one?
it's virtually the same.
fgmasdr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-03 19:19, IOhannes m zmoelnig wrote:
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
I don't really know why this is happening, but I do know that the ./autogen.sh in pure-data.git and pd-extended.git works everywhere since it is used in the builds every night. Why not just use that one?
it's virtually the same.
esp. in the trivial case, where there is autoreconf (and not mingw), where both scripts just call: $ autoreconf -fiv
so it's not that autogen.sh script that causes trouble, but autoreconf. i'm not saying that it is broken, i'm only saying that i find it weird that autoreconf generates a file for autoconf and then complains that it is has been generated for another version of autoconf.
fgmasdr IOhannes
On Oct 3, 2011, at 1:22 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-03 19:19, IOhannes m zmoelnig wrote:
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
I don't really know why this is happening, but I do know that the ./autogen.sh in pure-data.git and pd-extended.git works everywhere since it is used in the builds every night. Why not just use that one?
it's virtually the same.
esp. in the trivial case, where there is autoreconf (and not mingw), where both scripts just call: $ autoreconf -fiv
so it's not that autogen.sh script that causes trouble, but autoreconf. i'm not saying that it is broken, i'm only saying that i find it weird that autoreconf generates a file for autoconf and then complains that it is has been generated for another version of autoconf.
MinGW does have autoreconf, it was just giving me troubles, that's why I made that special case. It might no longer be necessary with the new MinGW.
.hc
----------------------------------------------------------------------------
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
On Oct 3, 2011, at 5:06 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-02 22:27, Hans-Christoph Steiner wrote:
FYI:
http://autobuild.puredata.info/auto-build/2011-10-02/logs/2011-10-02_03.15.2...
hmm, i cannot reach this machine anymore...
Yeah, it seems to be down, I'll check it tomorrow.
thanks. now that it is online again, i did a little test:
<snip> macosx105-i386:~ pddev$ cd tmp/externals/ macosx105-i386:externals pddev$ make /Users/pddev/tmp/externals/zexy/configure
grep: /Users/pddev/tmp/externals/loaders/pdlua/src/config.h: No such file or directory cd /Users/pddev/tmp/externals/zexy && ./autogen.sh PATH: /sw/bin:/Users/pddev/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:5: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:5: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:5: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:5: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: /usr/bin/autoconf failed with exit status: 63 make: *** [/Users/pddev/tmp/externals/zexy/configure] Error 63
macosx105-i386:externals pddev$ . /sw/bin/init.sh macosx105-i386:externals pddev$ make /Users/pddev/tmp/externals/zexy/configure
grep: /Users/pddev/tmp/externals/loaders/pdlua/src/config.h: No such file or directory cd /Users/pddev/tmp/externals/zexy && ./autogen.sh PATH: /sw/bin:/sw/bin:/sw/sbin:/Users/pddev/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/X11R6/bin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' autoreconf: running: /sw/bin/autoconf-2.68 --force autoreconf: running: /sw/bin/autoheader-2.68 --force autoreconf: running: automake --add-missing --copy --force-missing configure.ac:6: installing `./config.guess' configure.ac:6: installing `./config.sub' configure.ac:5: installing `./install-sh' configure.ac:5: installing `./missing' src/Makefile.am: installing `./depcomp' autoreconf: Leaving directory `.' </snip>
this basically indicates, that zexy's autogen.sh is working fine, as long as we have "Fink support" (by running: sourcing /sw/bin/init.sh) actually, only /sw/bin has to be added to the PATH
the logfiles reveal that PATH is set to /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/sw/bin:/sw/sbin which seems to be OK but obviously isn't: bummer #1: the leading /sw/bin is set in zexy's autogen.sh, but actually it is set too late (after AUTORECONF has been evaluated to /usr/bin/autoreconf)) - indeed that was a difference between puredata.git/autogen.sh and the one used in zexy :-) fixed in current SVN, so zexy should build on OSX from now on
bummer #2: the path settings for building Pd-extended make sure that fink installed replacements are only fallbacks for the system installed programmes. e.g. fink comes with autoconf-2.68 while the system comes with autoconf-2.61; the path settings make sure that the older one is used. is there a compelling reason to append /sw/bin rather than to prepend it (as is done by /sw/bin/init.s)?
mfgasdr IOhannes
On Oct 5, 2011, at 4:05 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-03 18:48, Hans-Christoph Steiner wrote:
On Oct 3, 2011, at 5:06 AM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-10-02 22:27, Hans-Christoph Steiner wrote:
FYI:
http://autobuild.puredata.info/auto-build/2011-10-02/logs/2011-10-02_03.15.2...
hmm, i cannot reach this machine anymore...
Yeah, it seems to be down, I'll check it tomorrow.
thanks. now that it is online again, i did a little test:
<snip> macosx105-i386:~ pddev$ cd tmp/externals/ macosx105-i386:externals pddev$ make /Users/pddev/tmp/externals/zexy/configure
grep: /Users/pddev/tmp/externals/loaders/pdlua/src/config.h: No such file or directory cd /Users/pddev/tmp/externals/zexy && ./autogen.sh PATH: /sw/bin:/Users/pddev/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/X11/bin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:5: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:5: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force aclocal.m4:20: warning: this file was generated for autoconf 2.68. You have another version of autoconf. It may work, but is not guaranteed to. If you have problems, you may need to regenerate the build system entirely. To do so, use the procedure documented by the package, typically `autoreconf'. configure.ac:5: error: Autoconf version 2.62 or higher is required aclocal.m4:8945: AM_INIT_AUTOMAKE is expanded from... configure.ac:5: the top level autom4te: /usr/bin/gm4 failed with exit status: 63 autoreconf: /usr/bin/autoconf failed with exit status: 63 make: *** [/Users/pddev/tmp/externals/zexy/configure] Error 63
macosx105-i386:externals pddev$ . /sw/bin/init.sh macosx105-i386:externals pddev$ make /Users/pddev/tmp/externals/zexy/configure
grep: /Users/pddev/tmp/externals/loaders/pdlua/src/config.h: No such file or directory cd /Users/pddev/tmp/externals/zexy && ./autogen.sh PATH: /sw/bin:/sw/bin:/sw/sbin:/Users/pddev/bin:/usr/bin:/bin:/usr/sbin:/ sbin:/usr/local/bin:/usr/X11/bin:/usr/X11R6/bin running autoreconf autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' autoreconf: running: /sw/bin/autoconf-2.68 --force autoreconf: running: /sw/bin/autoheader-2.68 --force autoreconf: running: automake --add-missing --copy --force-missing configure.ac:6: installing `./config.guess' configure.ac:6: installing `./config.sub' configure.ac:5: installing `./install-sh' configure.ac:5: installing `./missing' src/Makefile.am: installing `./depcomp' autoreconf: Leaving directory `.'
</snip>
this basically indicates, that zexy's autogen.sh is working fine, as long as we have "Fink support" (by running: sourcing /sw/bin/init.sh) actually, only /sw/bin has to be added to the PATH
the logfiles reveal that PATH is set to /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/ sw/bin:/sw/sbin which seems to be OK but obviously isn't:
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.0...
Its set in run-automated-builder here:
# On Mac OS X, there are some handy things in Fink, but don't override the # built-in tools PATH="${PATH}:/sw/bin:/sw/sbin" export PATH
This is set like this so that we can ensure that Fink is not required for building things that use autotools. Most Mac OS X users do not have Fink, MacPorts, Brew, etc. installed, so things like libraries really should build without Fink. Obviously, when talking about libraries not included in Mac OS X, then Fink is required.
bummer #1: the leading /sw/bin is set in zexy's autogen.sh, but actually it is set too late (after AUTORECONF has been evaluated to /usr/bin/autoreconf)) - indeed that was a difference between puredata.git/autogen.sh and the one used in zexy :-) fixed in current SVN, so zexy should build on OSX from now on
bummer #2: the path settings for building Pd-extended make sure that fink installed replacements are only fallbacks for the system installed programmes. e.g. fink comes with autoconf-2.68 while the system comes with autoconf-2.61; the path settings make sure that the older one is used. is there a compelling reason to append /sw/bin rather than to prepend it (as is done by /sw/bin/init.s)?
I don't really know what the issue here. This is why I generally avoid autotools. They end up making a nice ./configure interface, and the Makefile.am is quite nice, but often, you suffer way too much to get there.
And don't forget, in every build, it runs ./autogen.sh && ./configure in pd/ and that is working. Following that hunch, I copied the pd/ autogen.sh into zexy/autogen.sh and it works fine in the auto-build 'pd' acccount. Also, on my 10.5 machine, I load Fink using . ". /sw/ bin/init.sh", so the path is prepended, and it still doesn't work, but with a different error:
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. - I.. -I/Users/hans/code/pure-data.git/src -g -O2 -mms-bitfields -MT 0x260x260x7e.lo -MD -MP -MF .deps/0x260x260x7e.Tpo -c -o 0x260x260x7e.lo 0x260x260x7e.c ../libtool: line 832: X--tag=CC: command not found ../libtool: line 865: libtool: ignoring unknown tag : command not found ../libtool: line 832: X--mode=compile: command not found ../libtool: line 998: *** Warning: inferring the mode of operation is deprecated.: command not found ../libtool: line 999: *** Future versions of Libtool will require -- mode=MODE be specified.: command not found ../libtool: line 1142: Xgcc: command not found ../libtool: line 1142: X-DHAVE_CONFIG_H: command not found ../libtool: line 1142: X-I.: command not found ../libtool: line 1142: X-I..: command not found ../libtool: line 1142: X-I/Users/hans/code/pure-data.git/src: No such file or directory ../libtool: line 1142: X-g: command not found ../libtool: line 1142: X-O2: command not found ../libtool: line 1142: X-mms-bitfields: command not found ../libtool: line 1142: X-MT: command not found ../libtool: line 1142: X0x260x260x7e.lo: command not found ../libtool: line 1142: X-MD: command not found ../libtool: line 1142: X-MP: command not found ../libtool: line 1142: X-MF: command not found ../libtool: line 1142: X.deps/0x260x260x7e.Tpo: No such file or directory ../libtool: line 1142: X-c: command not found ../libtool: line 1193: X0x260x260x7e.lo: command not found ../libtool: line 1198: libtool: compile: cannot determine name of library object from `': command not found
.hc
----------------------------------------------------------------------------
Mistrust authority - promote decentralization. - the hacker ethic
-----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.0...
the same logfiles also says: PATH: /sw/bin:/usr/bin:/bin:/usr/sbin:/sbin:/sw/bin:/sw/sbin
Its set in run-automated-builder here:
# On Mac OS X, there are some handy things in Fink, but don't override the # built-in tools PATH="${PATH}:/sw/bin:/sw/sbin" export PATH
This is set like this so that we can ensure that Fink is not required for building things that use autotools. Most Mac OS X users do not have Fink, MacPorts, Brew, etc. installed, so things like libraries really should build without Fink.
if there is no fink at all, then this shouldn't be a problem either. the way zexy's autogen.sh script worked, it might mix up the two.
but as i said, that is supposed to be fixed.
I don't really know what the issue here.
i set the PATH too late, resulting in using the system's autoreconf, but the system's autoreconf would then (eventually) use (some of) the autoconf tools from fink.
And don't forget, in every build, it runs ./autogen.sh && ./configure in pd/ and that is working.
i think i already got that part.
Following that hunch, I copied the pd/autogen.sh into zexy/autogen.sh and it works fine in the auto-build
not needed any more, see above
'pd' acccount. Also, on my 10.5 machine, I load Fink using . ". /sw/bin/init.sh", so the path is prepended, and it still doesn't work, but with a different error:
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.
fgmasdr IOhannes
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.0...
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
Its set in run-automated-builder here:
# On Mac OS X, there are some handy things in Fink, but don't override the # built-in tools PATH="${PATH}:/sw/bin:/sw/sbin" export PATH
This is set like this so that we can ensure that Fink is not required for building things that use autotools. Most Mac OS X users do not have Fink, MacPorts, Brew, etc. installed, so things like libraries really should build without Fink.
if there is no fink at all, then this shouldn't be a problem either. the way zexy's autogen.sh script worked, it might mix up the two.
but as i said, that is supposed to be fixed.
I don't really know what the issue here.
i set the PATH too late, resulting in using the system's autoreconf, but the system's autoreconf would then (eventually) use (some of) the autoconf tools from fink.
And don't forget, in every build, it runs ./autogen.sh && ./ configure in pd/ and that is working.
i think i already got that part.
Following that hunch, I copied the pd/autogen.sh into zexy/autogen.sh and it works fine in the auto- build
not needed any more, see above
'pd' acccount. Also, on my 10.5 machine, I load Fink using . ". /sw/bin/init.sh", so the path is prepended, and it still doesn't work, but with a different error:
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.
.hc
----------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
-----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.0...
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 :-)
vmadf IOhannes
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.0...
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:
http://autobuild.puredata.info/auto-build/2011-10-05/logs/2011-10-05_15.06.4...
But running this manually in the 'pd' account works:
cd ~pd/auto-build/pd-extended/externals make DESTDIR=/tmp zexy_clean zexy_install
.hc