[Protux-devel] autostuff migration : almost there

[Luciano Giordana]

everything going fine, but 

address@hidden head]$ autoconf
configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:13: error: possibly undefined macro: AC_ENABLE_SHARED
configure.ac:14: error: possibly undefined macro: AC_ENABLE_STATIC

so configure does not work yet.. I runned libtoolize primer than other steps, 
but nothing changes..

also , I tried a clean checkout and runned configure directly. same error

any ideas ?

ps - please, If you can, help me solve this ASAP because my only internet 
connection will also be cut off in 1 or 2 days, and I want to commit my 
changes before that (I need to compile them to test). I will stay checking 
the emails each hour today until 5 am GMT

thanks again





On Wednesday 12 February 2003 05:20 am, Martin Herren wrote:
> On Tue, 11 Feb 2003 22:06:27 -0200
>
> Luciano Giordana <address@hidden> wrote:
> > address@hidden head]$ aclocal -I
> > /home/giordana/Documents/alsa/alsa-lib-0.9.0rc5/utils/
> > seems to work
> > address@hidden head]$ autoheader -I /usr/local/share/aclocal
> > seems to work
>
> now the first 2 steps run fine
>
> > address@hidden head]$ libtoolize --force
> > You should update your `aclocal.m4' by running aclocal.
> > (again this message (I already runned aclocal))
>
> perhaps just run
> aclocal -I /home/giordana/Documents/alsa/alsa-lib-0.9.0rc5/utils/
> again...
>
> > address@hidden head]$ autoconf
> > configure.ac:11: error: possibly undefined macro: AC_PROG_LIBTOOL
> >       If this token and others are legitimate, please use
> > m4_pattern_allow. See the Autoconf documentation.
> > configure.ac:13: error: possibly undefined macro: AC_ENABLE_SHARED
> > configure.ac:14: error: possibly undefined macro: AC_ENABLE_STATIC
> >
> > (these are new)
>
> this is due to the problem with libtoolize... i would try to run aclocal
> (and perhaps autoheader again after liboolize)
>
> > address@hidden head]$ automake
> > seems to work
>
> fine
>
> > address@hidden head]$ ./configure
> > checking for a BSD-compatible install... /usr//bin/install -c
> > checking whether build environment is sane... yes
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking for g++... g++
> > checking for C++ compiler default output... 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 g++ accepts -g... yes
> > checking for style of include used by make... GNU
> > checking dependency style of g++... gcc3
> > checking for a BSD-compatible install... /usr//bin/install -c
> > ./configure: line 2379: AC_PROG_LIBTOOL: command not found
> > ./configure: line 2381: syntax error near unexpected token `yes'
> > ./configure: line 2381: `AC_ENABLE_SHARED(yes)'
> > address@hidden head]$
> >
> > seems worse than before :-(
>
> no... configure script hangs sooner, but autotool suite when further...
>
> > I will try a clean checkout (hard to me due the slow connection, but I
> > will try),
>
> that would be good... but first try to run aclocal again after libtoolize
>
> > meanwhile, could you explan in few words what is aclocal, autoheader, and
> > each one of the new compilation process steps ?
>
> aclocal generates the aclocal.m4 file, which contains used macros like
> AM_PATH_ALSA (from alsa.m4) and AC_PATH_MUSTUX (from mustux.m4), so the end
> user doesn't need to have these m4 files installed...
>
> autoheader generates the config.h.in file, which is used  by ./configure to
> create config.h... config.h defines among other the VERSION and
> RESOURCES_DIR
>
> automake generates the Makefile.in's from all the Makefile.am's
>
> autoconf generates the configure from configure.ac (or previously
> configure.in).
>
> ./configure takes all .in files (Makefile.in, config.h.in, ...) and
> generates the output files (Makefile, config.h,...)
>
> libtoolize is required for libraries... it generates the libtool file,
> which is used for compilation. but i'm not really sure was it does exactly.
>
> BTW, did someone else have problems with the upgrade to current cvs ? or
> did noone try it else ?
>
> /Martin

-- 
Best Regards
--
Luciano Giordana - Musician - Certified Java/GNU C++ Developer - Free Software 
Evangelist
Project Mustux - http://www.freesoftware.fsf.org/mustux
-- Once Palladium is up and running , I will become a hacker --