Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
02-07-2005, 03:15 PM
|
#1
|
LQ Newbie
Registered: Feb 2005
Distribution: Redhat9
Posts: 4
Rep:
|
Automake upgrade problem
I was trying to install the mod_jk connector source on a fresh redhat9 system and the .so file was not getting created. Some research suggested that I needed to update the version of automake I was using so I upgrade from 1.6 to 1.9 via rpm. No errors, no force.
When I went back to start the configure process with the buildconf.sh script I got this response:
rm autom4te.cache
libtoolize --force --automake --copy
aclocal
/usr/share/aclocal/vorbis.m4:9: warning: underquoted definition of XIPH_PATH_VORBIS
run info '(automake)Extending aclocal'
or see sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES
/usr/share/aclocal/ogg.m4:8: warning: underquoted definition of XIPH_PATH_OGG
/usr/share/aclocal/freetype2.m4:7: warning: underquoted definition of AC_CHECK_FT2
autom4te: unknown language: Autoconf-without-aclocal-m4
aclocal: autom4te failed with exit status: 1
autoheader
automake -a --foreign --copy
configure.in:16: version mismatch. This is Automake 1.9.1,
configure.in:16: but the definition used by this AM_INIT_AUTOMAKE
configure.in:16: comes from Automake 1.7.2. You should recreate
configure.in:16: aclocal.m4 with aclocal and run automake again.
autoconf
rm autom4te.cache
running the aclocal command I then got this:
/usr/share/aclocal/vorbis.m4:9: warning: underquoted definition of XIPH_PATH_VORBIS
run info '(automake)Extending aclocal'
or see sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/pkg.m4:5: warning: underquoted definition of PKG_CHECK_MODULES
/usr/share/aclocal/ogg.m4:8: warning: underquoted definition of XIPH_PATH_OGG
/usr/share/aclocal/freetype2.m4:7: warning: underquoted definition of AC_CHECK_FT2
autom4te: unknown language: Autoconf-without-aclocal-m4
aclocal: autom4te failed with exit status: 1
Any help would be greatly appreciated.
|
|
|
02-07-2005, 03:17 PM
|
#2
|
Senior Member
Registered: Dec 2004
Distribution: Slackware, ROCK
Posts: 1,973
Rep:
|
try:
automake --version
in a console and see what version is reports
|
|
|
02-07-2005, 03:18 PM
|
#3
|
LQ Newbie
Registered: Feb 2005
Distribution: Redhat9
Posts: 4
Original Poster
Rep:
|
Automake Version
automake (GNU automake) 1.9.1
Written by Tom Tromey <tromey@redhat.com>.
|
|
|
02-07-2005, 03:29 PM
|
#4
|
Senior Member
Registered: Dec 2004
Distribution: Slackware, ROCK
Posts: 1,973
Rep:
|
what version of autoconf?
|
|
|
02-07-2005, 03:31 PM
|
#5
|
LQ Newbie
Registered: Feb 2005
Distribution: Redhat9
Posts: 4
Original Poster
Rep:
|
Version of Autoconf
# autoconf --version
autoconf (GNU Autoconf) 2.57
Written by David J. MacKenzie and Akim Demaille.
|
|
|
02-07-2005, 03:33 PM
|
#6
|
Senior Member
Registered: Dec 2004
Distribution: Slackware, ROCK
Posts: 1,973
Rep:
|
`aclocal-1.8' is running `autom4te --language Autoconf-without-aclocal-m4'.
`autom4te' understands Autoconf-without-aclocal-m4 only since Autoconf 2.58.
So that would be the symptom of an older version of Autoconf being in PATH
somethin I found with a google, worth a shot.
EDIT: disregard that PATH statement, just try to upgrade the one you have installed.
|
|
|
02-07-2005, 03:37 PM
|
#7
|
LQ Newbie
Registered: Feb 2005
Distribution: Redhat9
Posts: 4
Original Poster
Rep:
|
symptom of older autoconf
Thanks a ton for your help here.
Please excuse the newbie nature of this question, but what specifically should I do with that? Do I upgrade autoconf?
|
|
|
02-07-2005, 03:42 PM
|
#8
|
Senior Member
Registered: Dec 2004
Distribution: Slackware, ROCK
Posts: 1,973
Rep:
|
yes, according to that, only autoconf >= 2.58 understands the command:
Autoconf-without-aclocal-m4
which is your problelm.
|
|
|
All times are GMT -5. The time now is 10:02 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|