View previous topic :: View next topic |
Author |
Message |
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Sun Sep 21, 2008 11:58 pm Post subject: aclocal failure on older vers of hal |
|
|
Recently decided to upgrade hal and udev to the latest stable versions. Of course now automount ceases to function on my usb devices.
As per others with similar problem went ahead and updated to the latest stable kernel (2.6.25-r7)l figuring that would fix things. No luck.
So the last time this happened (usb memory sticks would not auto-mount), I had to revert back to an older combo of hal and udev.
Trouble is, I can not get past a aclocal failure when I attempt to install anything less than hal-0.5.11-r1 (I need hal-0.5.9.1-r1).
Code: | * Messages for package sys-apps/hal-0.5.9-r1:
* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/sys-apps/hal-0.5.9-r1/temp/aclocal-21895.out
*
* ERROR: sys-apps/hal-0.5.9-r1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_unpack
* environment, line 3724: Called eautoreconf
* environment, line 1316: Called eaclocal
* environment, line 1255: Called autotools_run_tool 'src_unpack'
* environment, line 579: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
* The die message:
* Failed Running aclocal !
|
contents of aclocal-21895.out:
Code: | GNU nano 2.1.2 File: ...ys-apps/hal-0.5.9-r1/temp/aclocal-21895.out
/usr/share/aclocal/libtool.m4:785: _LT_LANG is expanded from...
/usr/share/aclocal/libtool.m4:768: LT_LANG is expanded from...
../../lib/autoconf/c.m4:769: AC_LANG_COMPILER(C++) is expanded from...
../../lib/autoconf/lang.m4:271: AC_LANG_COMPILER_REQUIRE is expanded from...
../../lib/autoconf/general.m4:2518: AC_LINK_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:505: AS_IF is expanded from...
../../lib/autoconf/general.m4:1974: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1994: AC_CACHE_CHECK is expanded from...
../../lib/autoconf/libs.m4:121: AC_CHECK_LIB is expanded from...
configure.in:345: the top level
autom4te-2.63: /usr/bin/m4 failed with exit status: 1
aclocal-1.10: autom4te failed with exit status: 1 |
I've tried re-emerging m4 (1.4.11) however same error persists. Unfort., I see that all vers of m4 <1.4.11 have been removed so there are no other options to try here.
Additionally the aclocal error occurs with either autoconf-2.61-r2 (stable) installed, or the ~x86 ver., autoconf-2.6.3.
Any ideas?
-psk31 |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Mon Sep 22, 2008 12:04 pm Post subject: |
|
|
While I know exactly, what your problem is (and no, it's not m4),
I'll start with a simple question: why do you think you need such an old hal ? |
|
Back to top |
|
|
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Mon Sep 22, 2008 5:08 pm Post subject: |
|
|
The reason I tried reverting back to an older ver of hal was because it worked in the past when all other options have failed. I've tried various recent combinations of hal/udev including the unstable side and its not happening (usb stick mount). As mentioned above I also moved to latest stable kernel as well figuring that would resolve the issue.
So no I'm not stuck on the older hal but unless someone can help me fix the automount failure I'm right out of options.
-psk31 |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Mon Sep 22, 2008 7:44 pm Post subject: |
|
|
I've seen some noise about it in bugzilla.
Check the udev bugs yourself, maybe you'll find a solution there
(but there's nothing conclusive neither about the problem nor solution,
only things that work for some of the people).
I've a mix of stable and unstable here and udev 128 is not yet here,
so I don't know if I'll get those problems too.
BTW, what are you using to automount ? |
|
Back to top |
|
|
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Mon Sep 22, 2008 8:07 pm Post subject: |
|
|
I've been letting kde automount the various usb devices. Worked fine until all hell broke loose with recent versions of hal/udev/dbus.
So you mentioned you have a solution to my aclocal errors, can you elaborate?
psk31 |
|
Back to top |
|
|
VoidMage Watchman
Joined: 14 Oct 2006 Posts: 6196
|
Posted: Mon Sep 22, 2008 9:16 pm Post subject: |
|
|
That was libtool 2 related,
configure.in needs AC_PROG_CXX.
I'm not using KDE, so no guesses here. |
|
Back to top |
|
|
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Tue Sep 23, 2008 2:43 am Post subject: |
|
|
Extremely frustrating to say the least. Tried everything from hal-0.5.10 on up, and while they compile don't allow the machine to automount.
As soon as I try to emerge anything below hal-0.5.10 the thing croaks on this aclocal error. I know hal-0.5.9-r1 works but it won't build any more. What am I missing here |
|
Back to top |
|
|
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Thu Sep 25, 2008 1:56 am Post subject: |
|
|
..still digging on this one. Let me ask though, am I the only one having trouble with aclocal (autoconf?) errors on older builds of hal (< hal-0.5.11)?
-psk31 |
|
Back to top |
|
|
TinheadNed Guru
Joined: 05 Apr 2003 Posts: 339 Location: Farnborough, UK
|
Posted: Mon Oct 06, 2008 6:53 pm Post subject: |
|
|
I've just encountered this problem. I'm limiting hal's upgrades as this is on my server which also runs MythTV. Allowing hal to upgrade breaks x input, as when I had a go at upgrading I couldn't see the obvious problems in the input that stopped my remote working. |
|
Back to top |
|
|
psk31 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 143 Location: Calgary, AB, Canada
|
Posted: Mon Oct 06, 2008 10:20 pm Post subject: |
|
|
Yes, I wish I had done the same. I've been unable to resolve this problem, nor can I downgrade back to the older hal due to some inexplicable autoconf issues building these older packages.
Its looking more and more like Gentoo has reached "end of life" on my end.
psk31 |
|
Back to top |
|
|
|