|
From: Yeshurun, M. <mei...@in...> - 2005-07-10 13:08:31
|
When I run autogen.sh I get =20 running: aclocal /opt/gnome/share/aclocal/libIDL.m4:6: warning: underquoted definition of AM_PATH_LIBIDL run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending%20aclocal /opt/gnome/share/aclocal/ORBit.m4:4: warning: underquoted definition of AM_PATH_ORBIT /usr/local/share/aclocal/gimp.m4:8: warning: underquoted definition of AM_PATH_GIMP autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 error: while running 'aclocal' =20 aclocal works on Red Hat, but I need to build Valgrind on SUSE. Is it supposed to work on SUSE (64-bit)?=20 =20 =20 Thanks, =20 Meir =20 =20 =20 |
|
From: Nicholas N. <nj...@cs...> - 2005-07-10 15:12:07
|
On Sun, 10 Jul 2005, Yeshurun, Meir wrote: > When I run autogen.sh I get > > running: aclocal > /opt/gnome/share/aclocal/libIDL.m4:6: warning: underquoted definition of > AM_PATH_LIBIDL > run info '(automake)Extending aclocal' > or see > http://sources.redhat.com/automake/automake.html#Extending%20aclocal > /opt/gnome/share/aclocal/ORBit.m4:4: warning: underquoted definition of > AM_PATH_ORBIT > /usr/local/share/aclocal/gimp.m4:8: warning: underquoted definition of > AM_PATH_GIMP > autom4te: unknown language: Autoconf-without-aclocal-m4 > aclocal: autom4te failed with exit status: 1 > error: while running 'aclocal' > > aclocal works on Red Hat, but I need to build Valgrind on SUSE. Is it > supposed to work on SUSE (64-bit)? Yes. Those warnings are for files already no your system, not files in Valgrind. Maybe your automake/autoconf installation is broken? N |
|
From: Tim M. <ti...@se...> - 2005-07-11 14:24:55
|
Nicholas Nethercote wrote: > On Sun, 10 Jul 2005, Yeshurun, Meir wrote: > >> When I run autogen.sh I get >> >> running: aclocal >> /opt/gnome/share/aclocal/libIDL.m4:6: warning: underquoted definition of >> AM_PATH_LIBIDL >> run info '(automake)Extending aclocal' >> or see >> http://sources.redhat.com/automake/automake.html#Extending%20aclocal >> /opt/gnome/share/aclocal/ORBit.m4:4: warning: underquoted definition of >> AM_PATH_ORBIT > > > Yes. Those warnings are for files already no your system, not files > in Valgrind. Maybe your automake/autoconf installation is broken? Did you read the web page that the error report links to? It explains why the error message occurs. I had a similar problem building Valgrind 3.0 on SuSE and it was fixed by modifying a couple of macro definitions as the web page describes. Tim |
|
From: Nicholas N. <nj...@cs...> - 2005-07-11 14:43:26
|
On Mon, 11 Jul 2005, Tim Martin wrote: >>> running: aclocal >>> /opt/gnome/share/aclocal/libIDL.m4:6: warning: underquoted definition of >>> AM_PATH_LIBIDL >>> run info '(automake)Extending aclocal' >>> or see >>> http://sources.redhat.com/automake/automake.html#Extending%20aclocal >>> /opt/gnome/share/aclocal/ORBit.m4:4: warning: underquoted definition of >>> AM_PATH_ORBIT > > Did you read the web page that the error report links to? It explains why the > error message occurs. I had a similar problem building Valgrind 3.0 on SuSE > and it was fixed by modifying a couple of macro definitions as the web page > describes. So is this a problem with Valgrind's configure/build system? If so, patches to fix the problem would be greatly appreciated -- none of the developers are automake/autoconf gurus. Thanks. N |
|
From: Tom H. <to...@co...> - 2005-07-11 14:51:10
|
In message <Pin...@ch...>
Nicholas Nethercote <nj...@cs...> wrote:
> On Mon, 11 Jul 2005, Tim Martin wrote:
>
>>>> running: aclocal
>>>> /opt/gnome/share/aclocal/libIDL.m4:6: warning: underquoted definition of
>>>> AM_PATH_LIBIDL
>>>> run info '(automake)Extending aclocal'
>>>> or see
>>>> http://sources.redhat.com/automake/automake.html#Extending%20aclocal
>>>> /opt/gnome/share/aclocal/ORBit.m4:4: warning: underquoted definition of
>>>> AM_PATH_ORBIT
>>
>> Did you read the web page that the error report links to? It
>> explains why the error message occurs. I had a similar problem
>> building Valgrind 3.0 on SuSE and it was fixed by modifying a couple
>> of macro definitions as the web page describes.
>
> So is this a problem with Valgrind's configure/build system? If so,
> patches to fix the problem would be greatly appreciated -- none of the
> developers are automake/autoconf gurus. Thanks.
The warnings are a result of third party macro files that need
updating as described on that web page.
I'm not sure why it is failing though - those warnings are usually
harmless but the report didn't seem to include any significant errors
so I don't know why the build failed.
I don't think there is any valgrind problem here anyway.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <to...@co...> - 2005-07-11 14:53:16
|
In message <yek...@de...>
Tom Hughes <to...@co...> wrote:
> The warnings are a result of third party macro files that need
> updating as described on that web page.
>
> I'm not sure why it is failing though - those warnings are usually
> harmless but the report didn't seem to include any significant errors
> so I don't know why the build failed.
Actually there is another error, the invalid language one:
autom4te: unknown language: Autoconf-without-aclocal-m4
I have no idea what that means, but I think it is the problem.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <to...@co...> - 2005-07-11 14:57:26
|
In message <yek...@de...>
Tom Hughes <to...@co...> wrote:
> In message <yek...@de...>
> Tom Hughes <to...@co...> wrote:
>
>> The warnings are a result of third party macro files that need
>> updating as described on that web page.
>>
>> I'm not sure why it is failing though - those warnings are usually
>> harmless but the report didn't seem to include any significant errors
>> so I don't know why the build failed.
>
> Actually there is another error, the invalid language one:
>
> autom4te: unknown language: Autoconf-without-aclocal-m4
>
> I have no idea what that means, but I think it is the problem.
Googling suggests that the usual cause for this is the version of
autoconf on the path is too old - recent versions of aclocal try to
use a feature that was only added to autoconf in version 2.58 and
if autoconf is older than that you get this error.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Dirk M. <dm...@gm...> - 2005-07-11 14:54:30
|
On Monday 11 July 2005 16:37, Tim Martin wrote: > Did you read the web page that the error report links to? It explains > why the error message occurs. I had a similar problem building Valgrind > 3.0 on SuSE and it was fixed by modifying a couple of macro definitions > as the web page describes. Those are warnings, not errors. The error is something different. Dirk |
|
From: Maurice v. d. P. <gri...@ge...> - 2005-07-11 16:06:36
|
On Mon, Jul 11, 2005 at 03:57:21PM +0100, Tom Hughes wrote: > Googling suggests that the usual cause for this is the version of > autoconf on the path is too old - recent versions of aclocal try to > use a feature that was only added to autoconf in version 2.58 and > if autoconf is older than that you get this error. Maybe AC_PREREQ(2.58) can help? --=20 Maurice van der Pot Gentoo Linux Developer gri...@ge... http://www.gentoo.org Creator of BiteMe! gri...@kf... http://www.kfk4ever.com |
|
From: Tom H. <to...@co...> - 2005-07-11 23:02:18
|
In message <200...@kf...>
Maurice van der Pot <gri...@ge...> wrote:
> On Mon, Jul 11, 2005 at 03:57:21PM +0100, Tom Hughes wrote:
> > Googling suggests that the usual cause for this is the version of
> > autoconf on the path is too old - recent versions of aclocal try to
> > use a feature that was only added to autoconf in version 2.58 and
> > if autoconf is older than that you get this error.
>
> Maybe AC_PREREQ(2.58) can help?
The user only needs autoconf 2.58 if he uses a version of aclocal
that requires - nothing that valgrind itself requires it.
The problem here is that the user has a version of aclocal installed
that is not compatible with the version of autoconf that is installed
on the machine.
Requiring recent versions of autoconf just seems to get us complaints
from people using older systems.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Olly B. <ol...@su...> - 2005-07-11 22:37:49
|
On 2005-07-11, Maurice van der Pot <gri...@ge...> wrote: > Maybe AC_PREREQ(2.58) can help? Autoconf 2.58 was superseded by 2.59 the same day (!) due to a problem with absolute path variables not being absolute so it's probably better to required 2.59 instead. Valgrind 2's configure.in already has this (at my suggestion): http://article.gmane.org/gmane.comp.debugging.valgrind/2436 I guess valgrind 3 had forked already and this only got applied to the 2.4 sources... Cheers, Olly |
|
From: Tom H. <to...@co...> - 2005-07-11 23:00:20
|
In message <slr...@ms...>
Olly Betts <ol...@su...> wrote:
> On 2005-07-11, Maurice van der Pot <gri...@ge...> wrote:
> > Maybe AC_PREREQ(2.58) can help?
>
> Autoconf 2.58 was superseded by 2.59 the same day (!) due to a problem
> with absolute path variables not being absolute so it's probably better
> to required 2.59 instead.
>
> Valgrind 2's configure.in already has this (at my suggestion):
>
> http://article.gmane.org/gmane.comp.debugging.valgrind/2436
Oh no it doesn't ;-) It did for a while but it got taken out again
because we got too many complaint from people with old versions of
autoconf. We got rid of whatever new feature was causing the problem
instead.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|