[pacman-dev] Build issues with the maint branch of pacman

newer
[pacman-dev] [PATCH] makepkg: fix...

Ciprian Dorin, Craciun

20 Oct 2009 20 Oct '09

6:27 a.m.

Hello all! While trying to build (a patched version) of the latest maint branch in the Git repository I get the following error: ~~~~ $ autoconf configure.ac:60: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:128: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:132: error: possibly undefined macro: AM_GNU_GETTEXT configure.ac:133: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION configure.ac:155: error: possibly undefined macro: AM_CONDITIONAL ~~~~ (My patch is only adding a git-dlagent script, and is not touching otherwise the configure.ac file.) Any ideas? (I'm using the latest up-to-date version of ArchLinux.) Thanks, Ciprian.

Show replies by date

Xavier

20 Oct 20 Oct

6:30 a.m.

On Tue, Oct 20, 2009 at 8:27 AM, Ciprian Dorin, Craciun wrote:

...

Hello all!

While trying to build (a patched version) of the latest maint branch in the Git repository I get the following error:

~~~~ $ autoconf

configure.ac:60: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:128: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:132: error: possibly undefined macro: AM_GNU_GETTEXT configure.ac:133: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION configure.ac:155: error: possibly undefined macro: AM_CONDITIONAL ~~~~

(My patch is only adding a git-dlagent script, and is not touching otherwise the configure.ac file.)

Any ideas? (I'm using the latest up-to-date version of ArchLinux.)

Did you install the base-devel group ? This contains automake, which might be what you are missing here. But you should install base-devel to build stuff.

Ciprian Dorin, Craciun

6:32 a.m.

On Tue, Oct 20, 2009 at 9:30 AM, Xavier wrote:

...

On Tue, Oct 20, 2009 at 8:27 AM, Ciprian Dorin, Craciun wrote:

...
Hello all!

While trying to build (a patched version) of the latest maint branch in the Git repository I get the following error:

~~~~ $ autoconf

configure.ac:60: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:128: error: possibly undefined macro: AC_PROG_LIBTOOL configure.ac:132: error: possibly undefined macro: AM_GNU_GETTEXT configure.ac:133: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION configure.ac:155: error: possibly undefined macro: AM_CONDITIONAL ~~~~

(My patch is only adding a git-dlagent script, and is not touching otherwise the configure.ac file.)

Any ideas? (I'm using the latest up-to-date version of ArchLinux.)

Did you install the base-devel group ? This contains automake, which might be what you are missing here. But you should install base-devel to build stuff.

Yes they are installed. (I've reinstalled them to the same outcome.)

Xavier

6:34 a.m.

On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...

Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran. What if you run autogen.sh ?

Ciprian Dorin, Craciun

6:37 a.m.

On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...

On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...
Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed: ~~~~ $ ./autogen.sh + aclocal + autoheader + automake --foreign + autoconf ~~~~ (Any idea why?) Thanks, Ciprian.

Ciprian Dorin, Craciun

6:42 a.m.

On Tue, Oct 20, 2009 at 9:37 AM, Ciprian Dorin, Craciun wrote:

...

On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...
Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed:

~~~~ $ ./autogen.sh

+ aclocal + autoheader + automake --foreign + autoconf ~~~~

(Any idea why?)

Thanks, Ciprian.

Now it fails during build by not finding the `a2x` application... Any missing dependency? (I'm using the PKGBUILD recepie from ABS, but for the 3.3.2 version, not 3.3.1.) Thanks' again.

Allan McRae

7:25 a.m.

Ciprian Dorin, Craciun wrote:

...

On Tue, Oct 20, 2009 at 9:37 AM, Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...
Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed:

~~~~ $ ./autogen.sh

+ aclocal + autoheader + automake --foreign + autoconf ~~~~

(Any idea why?)

Thanks, Ciprian.

Now it fails during build by not finding the `a2x` application... Any missing dependency? (I'm using the PKGBUILD recepie from ABS, but for the 3.3.2 version, not 3.3.1.)

If you posted the actual build output it might be helpful.... you probably need to install asciidoc or use --disable-docs on configrue.

Ciprian Dorin, Craciun

7:44 a.m.

On Tue, Oct 20, 2009 at 10:25 AM, Allan McRae wrote:

...

Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:37 AM, Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...
Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed:

~~~~ $ ./autogen.sh

+ aclocal + autoheader + automake --foreign + autoconf ~~~~

(Any idea why?)

Thanks, Ciprian.

Now it fails during build by not finding the `a2x` application... Any missing dependency? (I'm using the PKGBUILD recepie from ABS, but for the 3.3.2 version, not 3.3.1.)

If you posted the actual build output it might be helpful.... you probably need to install asciidoc or use --disable-docs on configrue.

Thanks, it builds now. Thus the problem was that inside the PKGBUILD for pacman, asciidoc was not specified as a make-dependency. After adding it there (and installing it), everything was completed successfully.

Allan McRae

7:48 a.m.

Ciprian Dorin, Craciun wrote:

...

On Tue, Oct 20, 2009 at 10:25 AM, Allan McRae wrote:

...
Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:37 AM, Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

...
Yes they are installed. (I've reinstalled them to the same outcome.)

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed:

~~~~ $ ./autogen.sh

+ aclocal + autoheader + automake --foreign + autoconf ~~~~

(Any idea why?)

Thanks, Ciprian.

Now it fails during build by not finding the `a2x` application... Any missing dependency? (I'm using the PKGBUILD recepie from ABS, but for the 3.3.2 version, not 3.3.1.)

If you posted the actual build output it might be helpful.... you probably need to install asciidoc or use --disable-docs on configrue.

Thanks, it builds now.

Thus the problem was that inside the PKGBUILD for pacman, asciidoc was not specified as a make-dependency. After adding it there (and installing it), everything was completed successfully.

It is not needed for building for the release tarballs. Hence it is not in the PKGBUILD. Allan

Ciprian Dorin, Craciun

7:50 a.m.

On Tue, Oct 20, 2009 at 10:48 AM, Allan McRae wrote:

...

Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 10:25 AM, Allan McRae wrote:

...
Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:37 AM, Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 9:34 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 8:32 AM, Ciprian Dorin, Craciun wrote:

> > Yes they are installed. (I've reinstalled them to the same outcome.) > > > >

I failed to see which commands you ran.

What if you run autogen.sh ?

Well this time (with `./autogen.sh`) it worked without even a warning. Just displayed:

~~~~ $ ./autogen.sh

+ aclocal + autoheader + automake --foreign + autoconf ~~~~

(Any idea why?)

Thanks, Ciprian.

Now it fails during build by not finding the `a2x` application... Any missing dependency? (I'm using the PKGBUILD recepie from ABS, but for the 3.3.2 version, not 3.3.1.)

If you posted the actual build output it might be helpful.... you probably need to install asciidoc or use --disable-docs on configrue.

Thanks, it builds now.

Thus the problem was that inside the PKGBUILD for pacman, asciidoc was not specified as a make-dependency. After adding it there (and installing it), everything was completed successfully.

It is not needed for building for the release tarballs. Hence it is not in the PKGBUILD.

Allan

But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Xavier

8:04 a.m.

On Tue, Oct 20, 2009 at 9:50 AM, Ciprian Dorin, Craciun wrote:

...

But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Why are you doing that ? And how did you get the source code of 3.3.2 ? With this link : ftp://ftp.archlinux.org/other/pacman/pacman-3.3.2.tar.gz ?

Ciprian Dorin, Craciun

8:17 a.m.

On Tue, Oct 20, 2009 at 11:04 AM, Xavier wrote:

...

On Tue, Oct 20, 2009 at 9:50 AM, Ciprian Dorin, Craciun wrote:

...
But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Why are you doing that ?

Because I've made a small patch to pacman that allows to "download" tars from a Git repository. See the related bug, and my Git repository (if interested): * http://bugs.archlinux.org/task/7816 * http://gitorious.org/~ciprian.craciun/pacman/ciprian-craciun-patches Thus after making the patch I've wanted to install it localy, test and use it. (I'm using it now.)

...

And how did you get the source code of 3.3.2 ? With this link : ftp://ftp.archlinux.org/other/pacman/pacman-3.3.2.tar.gz ?

From the Pacman git repository at: git://projects.archlinux.org/pacman.git

Allan McRae

8:20 a.m.

Ciprian Dorin, Craciun wrote:

...

On Tue, Oct 20, 2009 at 11:04 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 9:50 AM, Ciprian Dorin, Craciun wrote:

...
But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Why are you doing that ?

Because I've made a small patch to pacman that allows to "download" tars from a Git repository. See the related bug, and my Git repository (if interested): * http://bugs.archlinux.org/task/7816 * http://gitorious.org/~ciprian.craciun/pacman/ciprian-craciun-patches

Thus after making the patch I've wanted to install it localy, test and use it. (I'm using it now.)

...
And how did you get the source code of 3.3.2 ? With this link : ftp://ftp.archlinux.org/other/pacman/pacman-3.3.2.tar.gz ?

From the Pacman git repository at: git://projects.archlinux.org/pacman.git

So that brings us full circle to thae top of this message:

...

...
Thus the problem was that inside the PKGBUILD for pacman, asciidoc was not specified as a make-dependency. After adding it there (and installing it), everything was completed successfully.

...

It is not needed for building for the release tarballs. Hence it is not in the PKGBUILD.

Allan

But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Ciprian Dorin, Craciun

10:04 a.m.

On Tue, Oct 20, 2009 at 11:20 AM, Allan McRae wrote:

...

Ciprian Dorin, Craciun wrote:

...
On Tue, Oct 20, 2009 at 11:04 AM, Xavier wrote:

...
On Tue, Oct 20, 2009 at 9:50 AM, Ciprian Dorin, Craciun wrote:

...
But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Why are you doing that ?

Because I've made a small patch to pacman that allows to "download" tars from a Git repository. See the related bug, and my Git repository (if interested): * http://bugs.archlinux.org/task/7816 * http://gitorious.org/~ciprian.craciun/pacman/ciprian-craciun-patches

Thus after making the patch I've wanted to install it localy, test and use it. (I'm using it now.)

...
And how did you get the source code of 3.3.2 ? With this link : ftp://ftp.archlinux.org/other/pacman/pacman-3.3.2.tar.gz ?

From the Pacman git repository at: git://projects.archlinux.org/pacman.git

So that brings us full circle to thae top of this message:

...
...
Thus the problem was that inside the PKGBUILD for pacman, asciidoc was not specified as a make-dependency. After adding it there (and installing it), everything was completed successfully.

...
It is not needed for building for the release tarballs. Hence it is not in the PKGBUILD.

Allan

But then why does it fail when building it from PKGBUILD? (I've used an unmodified version of PKGBUILD from ABS (for version 3.3.1), with the soure code from 3.3.2.)

Ok.

5295

Age (days ago)

5295

Last active (days ago)

List overview

Download

13 comments

3 participants

participants (3)

Allan McRae
Ciprian Dorin, Craciun
Xavier