To pd-dev -
I might be missing something... under Fedora 17 (the newest I believe), when I try to build Pd using the "new build system" I get:
[msp@fuzz pd]$ ./autogen.sh autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4/generated -I m4 autoreconf: configure.ac: tracing autoreconf: configure.ac: creating directory m4/config autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force configure.ac:91: error: possibly undefined macro: AC_LIBTOOL_DLOPEN If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:92: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.ac:93: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:114: error: possibly undefined macro: AC_CHECK_LIBM autoreconf: /usr/bin/autoconf failed with exit status: 1 [msp@fuzz pd]$
This is off a clean git checkout. Are there build-system patches out there that I should be applying first, or anyway, what am I missing?
thanks Miller
On 11/22/2012 04:31 AM, Miller Puckette wrote:
To pd-dev -
I might be missing something... under Fedora 17 (the newest I believe), when I try to build Pd using the "new build system" I get:
This is off a clean git checkout. Are there build-system patches out there that I should be applying first, or anyway, what am I missing?
intall "libtool". (this is only needed on people using the git-version; for any releases, configure should be pre-generated by the other, so libtool is no longer needed)
fgmasr IOhannes
On Nov 22, 2012, at 9:16 AM, IOhannes m zmölnig wrote:
On 11/22/2012 04:31 AM, Miller Puckette wrote:
To pd-dev -
I might be missing something... under Fedora 17 (the newest I believe), when I try to build Pd using the "new build system" I get:
This is off a clean git checkout. Are there build-system patches out there that I should be applying first, or anyway, what am I missing?
intall "libtool". (this is only needed on people using the git-version; for any releases, configure should be pre-generated by the other, so libtool is no longer needed)
The new build system provides the very handy 'make dist' which generates a proper source tarball for release. It should handle generating the ./configure and whatever else needs doing.
By following the autotools style rather than hacking our own, we get a lot of extra goodies like this.
.hc