You are not logged in.

#1 2007-02-17 16:20:02

kinton
Member
Registered: 2007-02-17
Posts: 9

Something wrong with autoreconf?

Hello,everyone!
Today i got a PKGBUILD file,when i ran "makepkg",it output the errors:

==> Starting make...
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal 
autoreconf: configure.in: tracing
autoreconf: running: libtoolize --copy
Putting files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
libtoolize: `ltmain.sh' exists: use `--force' to overwrite
autoreconf: running: /usr/bin/autoconf
configure.in:74: error: possibly undefined macro: AC_DEFINE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: Build Failed.  Aborting...

sad


----Asus A6Tseries----
    AMD Turion 64 x2 TL52
    Nvidia GeForce Go 7300
    Memory 512MB

Offline

#2 2007-02-17 16:36:42

kinton
Member
Registered: 2007-02-17
Posts: 9

Re: Something wrong with autoreconf?

PKGBUILD:

# Maintainer: jotapesan <lord_jotape@yahoo.com.ar>

pkgname=kiba-dock-cvs
pkgver=20070211
pkgrel=1
pkgdesc="kiba-dock is a dock with physics. The author describes kibadock
like silly dock demo of akamaru."
url="http://www.kiba-dock.org/"
license=
depends=(gconf libglade librsvg gnome-python gnome-python-extras
libgtop)
replaces=()
conflicts=()
makedepends=('cvs')
options=('NOSTRIP')
source=()
md5sums=()

_cvsroot=":pserver:anonymous@metascape.afraid.org:/cvsroot"
_cvsmod="kiba-dock"

build() {
  cd $startdir/src
  msg "Connecting to metascape.afraid.org CVS server...."
  cvs -z3 -d $_cvsroot co -D $pkgver -f $_cvsmod
  cd $_cvsmod
   msg "CVS checkout done or server timeout"
   msg "Starting make..."
   cp -r ../$_cvsmod ../$_cvsmod-build
   cd ../$_cvsmod-build
   sed -i 's|AM_GCONF_SOURCE_2|#|' configure.in
   ./autogen.sh --prefix=/usr
   make || return 1
   make install-schemas
   make DESTDIR=$startdir/pkg install || return 1
   rm -r $startdir/src/$_cvsmod-build
}

----Asus A6Tseries----
    AMD Turion 64 x2 TL52
    Nvidia GeForce Go 7300
    Memory 512MB

Offline

#3 2007-02-17 19:26:03

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

As of today, I'm having the same problem with basically all packages that use autoconf. I have no idea why that is? I don't remember my last updates...

Offline

#4 2007-02-17 19:28:52

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

Here's a variation of that error message:

Checking for forbidden M4 macros...
***Error***: some autoconf macros required to build Package
  were not found in your aclocal path, or some forbidden
  macros were found.  Perhaps you need to adjust your
  ACLOCAL_FLAGS?

Offline

#5 2007-02-17 21:18:32

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

Hm... I'm building quite a few subversion packages so I really need this in order. I've been googling alot but haven't found anything helpful. What I've found out so far is that 

echo $ACLOCAL_FLAGS 
-I /opt/gnome/share/aclocal -I /opt/gnome/share/aclocal

but even macros defined in that there are claimed to be not defined.

Here's when trying to build compiz-git:

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal 
/usr/share/aclocal/xdelta.m4:7: warning: underquoted definition of AM_PATH_XDELTA
/usr/share/aclocal/xdelta.m4:7:   run info '(automake)Extending aclocal'
/usr/share/aclocal/xdelta.m4:7:   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.ac:140: warning: macro `AM_GCONF_SOURCE_2' not found in library
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy
Putting files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
libtoolize: `ltmain.sh' exists: use `--force' to overwrite
/usr/share/aclocal/xdelta.m4:7: warning: underquoted definition of AM_PATH_XDELTA
/usr/share/aclocal/xdelta.m4:7:   run info '(automake)Extending aclocal'
/usr/share/aclocal/xdelta.m4:7:   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.ac:140: warning: macro `AM_GCONF_SOURCE_2' not found in library
autoreconf: running: /usr/bin/autoconf
configure.ac:140: error: possibly undefined macro: AM_GCONF_SOURCE_2
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

Help anyone?

Offline

#6 2007-02-18 10:59:56

kinton
Member
Registered: 2007-02-17
Posts: 9

Re: Something wrong with autoreconf?

Is there anyone can help me?


----Asus A6Tseries----
    AMD Turion 64 x2 TL52
    Nvidia GeForce Go 7300
    Memory 512MB

Offline

#7 2007-02-18 15:24:05

noriko
Member
From: In My Mind
Registered: 2006-06-09
Posts: 535
Website

Re: Something wrong with autoreconf?

you could try export ACLOCAL_FLAGS="-I /opt/gnome/share/aclocal -I /usr/share/aclocal"
the majority of the m4 macros are in usr share.


The.Revolution.Is.Coming - - To fight, To hunger, To Resist!

Offline

#8 2007-02-19 02:13:17

kinton
Member
Registered: 2007-02-17
Posts: 9

Re: Something wrong with autoreconf?

Thank you,noriko.It works now!:)


----Asus A6Tseries----
    AMD Turion 64 x2 TL52
    Nvidia GeForce Go 7300
    Memory 512MB

Offline

#9 2007-02-19 13:09:04

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

This is still not working for me. I've narrowed down the problem to autogen.sh-scripts that call gnome-autogen.sh. This is what I get

Checking for required M4 macros...
  libtool.m4 not found
  glib-gettext.m4 not found
  intltool.m4 not found
  pkg.m4 not found
Checking for forbidden M4 macros...
***Error***: some autoconf macros required to build avant-panel-menu
  were not found in your aclocal path, or some forbidden
  macros were found.  Perhaps you need to adjust your
  ACLOCAL_FLAGS?

./PKGBUILD: line 35: ./configure: No such file or directory
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: Build Failed.  Aborting...
==> ERROR: Reverting pkgver...

If I export ACLOCAL_FLAGS="-I /opt/gnome/share/aclocal -I /usr/share/aclocal", I simply get

Checking for required M4 macros...
Checking for forbidden M4 macros...

./PKGBUILD: line 35: ./configure: No such file or directory
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: Build Failed.  Aborting...
==> ERROR: Reverting pkgver...

Offline

#10 2007-02-20 18:33:14

fredp
Member
From: Italy
Registered: 2005-08-11
Posts: 30

Re: Something wrong with autoreconf?

I solved downgrading to automake 1.9.6, but this actually isn't a solution hmm

Offline

#11 2007-02-20 22:02:19

noriko
Member
From: In My Mind
Registered: 2006-06-09
Posts: 535
Website

Re: Something wrong with autoreconf?

i added a more complete list of sources to the thread > http://bbs.archlinux.org/viewtopic.php?id=30125 ;;; if u still have issues, maybe check it out...
i have had no issues so i dunno if it fixes anything..


The.Revolution.Is.Coming - - To fight, To hunger, To Resist!

Offline

#12 2007-02-21 15:17:44

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

Thanks for the suggestion. It's still not working here:

ch_actual_version=
ch_cur=21
ch_min=14
ch_min_version=1.7
ch_save_IFS=' 
'
ch_status=0
cm_macrodirs=
configure_ac=./configure.in
configure_files=./configure.in
normal=''
srcdir=.
vc_actual_version=0.21
vc_checkprog=pkg-config
vc_checkprogs=pkg-config
vc_comparator='>='
vc_min_version=0.14.0
vc_package=pkg-config
vc_source=''\''http://www.freedesktop.org/software/pkgconfig/releases/pkgconfig-0.14.0.tar.gz'
vc_status=0
vc_variable=PKG_CONFIG
want_gettext=false
want_glib_gettext=true
want_gnome_doc_utils=false
want_gtk_doc=false
want_intltool=true
want_libtool=true
want_pkg_config=true
Checking for required M4 macros...
Checking for forbidden M4 macros...
./PKGBUILD: line 46: ./configure: No such file or directory
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: Build Failed.  Aborting...
==> ERROR: Reverting pkgver...

It's really starting to annoy me... I'm gonna see if it helps downgrading automake...

Offline

#13 2007-02-21 15:20:11

JGC
Developer
Registered: 2003-12-03
Posts: 1,664

Re: Something wrong with autoreconf?

It can't find all m4 files, it complains about intltool.m4 and glib-gettext.m4, AFAIK both are in the intltool package (we're getting rid of intltool makedepends nowadays, packages with a pregenerated configure file can do it with just perlxml).

Offline

#14 2007-02-21 15:23:38

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

fredp wrote:

I solved downgrading to automake 1.9.6, but this actually isn't a solution hmm

Yep, this worked for me too. Bugreport here: http://bugs.archlinux.org/task/6466

Offline

#15 2007-02-21 15:28:23

nightfrost
Member
From: Sweden
Registered: 2005-04-16
Posts: 647

Re: Something wrong with autoreconf?

JGC wrote:

It can't find all m4 files, it complains about intltool.m4 and glib-gettext.m4, AFAIK both are in the intltool package (we're getting rid of intltool makedepends nowadays, packages with a pregenerated configure file can do it with just perlxml).

I have intltool installed. The script does seem to find all the m4 files, but it gives up anyway. I think this can been seen in the last output I've posted.

Offline

#16 2007-02-22 04:19:34

thebombjoe2
Member
Registered: 2007-02-18
Posts: 4

Re: Something wrong with autoreconf?

so i downgrade and it get pasts the error if i makepkg twice
but then i get

[root@myhost kiba-dock-cvs]# makepkg
==> Making package: kiba-dock-cvs 20070220-1 (Wed Feb 21 22:21:01 EST 2007)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==> Validating source files with MD5sums
==> Extracting Sources...
==> Removing existing pkg/ directory...
==> Starting build()...
==> Connecting to metascape.afraid.org CVS server....
cvs checkout: warning: failed to open /root/.cvspass for reading: No such file or directory
? kiba-dock/INSTALL
? kiba-dock/Makefile.in
? kiba-dock/aclocal.m4
? kiba-dock/autom4te.cache
? kiba-dock/config
? kiba-dock/config.h.in
? kiba-dock/config.log
? kiba-dock/configure
? kiba-dock/libtool
? kiba-dock/po
? kiba-dock/akamaru/Makefile.in
? kiba-dock/dock/Makefile.in
? kiba-dock/files/Makefile.in
? kiba-dock/gset-kiba/Makefile.in
? kiba-dock/icons/Makefile.in
? kiba-dock/plugins/Makefile.in
? kiba-dock/utils/Makefile.in
cvs checkout: Updating kiba-dock
cvs checkout: Updating kiba-dock/akamaru
cvs checkout: Updating kiba-dock/bin
cvs checkout: Updating kiba-dock/dock
cvs checkout: Updating kiba-dock/files
cvs checkout: Updating kiba-dock/gset-kiba
cvs checkout: Updating kiba-dock/icons
cvs checkout: Updating kiba-dock/plugins
cvs checkout: Updating kiba-dock/utils
==> CVS checkout done or server timeout
==> Starting make...
sed: -e expression #1, char 0: no previous regular expression
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.in: tracing
autoreconf: running: libtoolize --copy
Putting files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: `config.guess' exists: use `--force' to overwrite
libtoolize: `config.sub' exists: use `--force' to overwrite
libtoolize: `ltmain.sh' exists: use `--force' to overwrite
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for ANSI C header files... (cached) yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
./configure: line 21846: ./po/POTFILES.in: No such file or directory
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for gconftool-2... /opt/gnome/bin/gconftool-2
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for gettimeofday... yes
checking for memset... yes
checking for sqrt... no
checking for strrchr... yes
checking for strstr... yes
checking whether byte ordering is bigendian... no
./configure: line 22959: syntax error near unexpected token `KIBA_DOCK,'
./configure: line 22959: `PKG_CHECK_MODULES(KIBA_DOCK, "$KIBA_DOCK_REQUIRES")'
make: *** No targets specified and no makefile found.  Stop.
==> ERROR: Build Failed.  Aborting...

any help?

Last edited by thebombjoe2 (2007-02-22 04:23:39)

Offline

Board footer

Powered by FluxBB