Mailing List Archive

autoconf upgrade problem
Hi,
I need autoconf 2.6 or higher so I downloaded m4-1.4.11 and autconf-2.62 and
got all of them built and installed using prefix=/usr.
However, even after that I try to compile pulseaudio, I get the following
error:

+ aclocal
/usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of
AM_PATH_AUDIOFILE
run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending%20aclocal
configure.ac:25: error: Autoconf version 2.60 or higher is required
configure.ac:25: the top level
autom4te: /usr/bin/m4 failed with exit status: 63
aclocal: autom4te failed with exit status: 63
./autogen.sh: line 24: /home/kwan/pulseaudio/configure: No such file or
directory
./autogen.sh: line 24: exec: /home/kwan/pulseaudio/configure: cannot
execute: No such file or directory


What do I have to do for autogen to use the latest autoconf I installed?

Thank you!

-kwan
--
http://www.media.mit.edu/~kwan/info.html
RE: autoconf upgrade problem [ In reply to ]
Kwan Hong Lee wrote:
> What do I have to do for autogen to use the latest autoconf I
> installed?

Probably depends on your environment.

lrwxrwxrwx 1 root root 19 Mar 31 08:52 /scratchbox/tools/bin/autoconf
-> sb_autoconf_wrapper
--
if ($force eq '2.13') {
ac213 ();
} elsif ($force eq '2.50' || $force eq '2.59') {
ac250 ();

if ($mode eq 'autoreconf' && $arg eq '--install') {
ac250 ();

# Default to 2.13.
ac213 ();

sub ac213 {
run_autoconf ("/scratchbox/tools/bin/${mode}2.13");

sub ac250 {
run_autoconf ("/scratchbox/tools/bin/${mode}2.50");
--

[sbox-test-arm: ~] > ls /scratchbox/tools/bin/autoconf
autoconf autoconf-2.13 autoconf2.13 autoconf2.50

Personally, I'd probably just manually run autconf2.62 or however it's
spelled.

Instead of installing in /usr, you could install in ~/ and have your
path be of the form:

~/bin:~/usr/bin:$PATH

If ~/usr/bin/autoconf2.62 exists, you could ln -s ~/usr/bin/autoconf2.62
~/bin

And then move on with life.

Installing things to / are imo one of the most foolish things people can
do. For fun just look at all the problems people have w/ /usr/bin/python
(which might be /usr/bin/python: symbolic link to `python2.5', or
/usr/bin/python: symbolic link to `python2.4' or /usr/bin/python:
symbolic link to `python2.3' or ..., where different versions of python
are fairly incompatible, and you never know which things will break if
you change the symlink).
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: autoconf upgrade problem [ In reply to ]
Kwan Hong Lee wrote:
> For some reason, even if I have the new autoconf directory
> added to the beginning of the directory, when I call
> pulseaudio/autogen.sh it uses the older autoconf, currently
> 2.59. I can't modify sb_autoconf_wrapper because it's read only.
>
> What can I do?

Please don't reply to individuals. This is a list for a reason.

timeless@koku:/scratchbox/tools/bin$ echo *2.50*
autoconf2.50 autoheader2.50 autoreconf2.50
timeless@koku:/scratchbox/tools/bin$ ls -l autoconf2.50
lrwxrwxrwx 1 root root 38 2008-03-31 18:52 autoconf2.50 ->
../autotools/autoconf2.59/bin/autoconf
timeless@koku:/scratchbox/tools/bin$ cd ../autotools/
timeless@koku:/scratchbox/tools/autotools$ ls
autoconf2.13 autoconf2.59 automake-1.4 automake-1.7 automake-1.8
automake-1.9
timeless@koku:/scratchbox/tools/autotools$ mkdir ~/ac262
timeless@koku:/scratchbox/tools/autotools$ pushd ~/ac262/
~/ac262 /scratchbox/tools/autotools
timeless@koku:~/ac262$ wget
http://ftp.gnu.org/gnu/autoconf/autoconf-2.62.tar.bz2 2> /dev/null >
/dev/null
timeless@koku:~/ac262$ tar jxf autoconf-2.62.tar.bz2
timeless@koku:~/ac262$ cd autoconf-2.62/
timeless@koku:~/ac262$ ./configure
--prefix=/scratchbox/tools/autotools/autoconf2.62
timeless@koku:~/ac262/autoconf-2.62$ make -s

root@koku:~# cd /home/timeless/ac262/autoconf-2.62
root@koku:/home/timeless/ac262/autoconf-2.62# make install 2> /dev/null
> /dev/null
root@koku:/home/timeless/ac262/autoconf-2.62# cd /scratchbox/tools/bin
root@koku:/scratchbox/tools/bin# ls -l autoconf2.50
lrwxrwxrwx 1 root root 38 2008-03-31 18:52 autoconf2.50 ->
../autotools/autoconf2.59/bin/autoconf
root@koku:/scratchbox/tools/bin# ln -s
../autotools/autoconf2.62/bin/autoconf autoconf2.60
root@koku:/scratchbox/tools/bin# ln -s
../autotools/autoconf2.62/bin/autoheader autoheader2.60
root@koku:/scratchbox/tools/bin# ln -s
../autotools/autoconf2.62/bin/autoreconf autoreconf2.60
root@koku:/scratchbox/tools/bin# patch < /dev/stdin
--- sb_autoconf_wrapper 2008-05-05 09:40:45.000000000 +0300
+++ sb_autoconf_wrapper 2008-05-05 09:42:47.000000000 +0300
@@ -26,2 +26,4 @@
ac250 ();
+ } elsif ($force eq '2.60' || $force eq '2.62') {
+ ac260 ();
} else {
@@ -158,2 +160,9 @@
-# Default to 2.13.
-ac213 ();
+my $force = $ENV{'SBOX_DEFAULT_AUTOCONF'};
+if ($force eq '2.50' || $force eq '2.59') {
+ ac250 ();
+} elsif ($force eq '2.60' || $force eq '2.62') {
+ ac260 ();
+} else {
+ # Default to 2.13.
+ ac213 ();
+}
@@ -222 +223,5 @@
+sub ac260 {
+ run_autoconf ("/scratchbox/tools/bin/${mode}2.60");
+}
+
sub run_autoconf {
^D
patching file sb_autoconf_wrapper
Hunk #2 succeeded at 161 (offset 1 line).
Hunk #3 succeeded at 224 with fuzz 1 (offset 1 line).

sbox-arm@koku:~$ scratchbox
[sbox-test-arm: ~] > SBOX_DEFAULT_AUTOCONF=2.60
[sbox-test-arm: ~] > export SBOX_DEFAULT_AUTOCONF
[sbox-test-arm: ~] > autoconf
autoconf2.60: no input file
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers