1 |
I'm open to any suggestions to get me past this point. I'll look into disabling the darwin7 patch from the m4 ebuild and see if that helps. |
2 |
|
3 |
Thanks very much for taking the time to help me out, I sincerely appreciate it. |
4 |
|
5 |
--Marshall |
6 |
|
7 |
----- Original Message ----- |
8 |
From: "Matt Michalowski" <me@××××××××.au> |
9 |
To: gentoo-alt@l.g.o |
10 |
Sent: Thursday, November 1, 2007 7:27:47 PM (GMT-0600) America/Chicago |
11 |
Subject: Re: [gentoo-alt] [AIX] emerge autoconf-2.61-r1 fails |
12 |
|
13 |
Marshall McMullen wrote: |
14 |
> *sigh* Well, I can't install m4 because it requires autoconf and |
15 |
> automake, but I can't install autoconf and automake because they |
16 |
> require m4. This sounds like a pretty nasty situation.... why does m4 |
17 |
> require autoconf/automake ? Any ideas or thoughts on how to get around |
18 |
> this would be appreciated. |
19 |
> |
20 |
> Thanks! |
21 |
|
22 |
I think you can configure & make m4 without requiring autotool stuff. I |
23 |
think the prefix portage version triggers a regen (not intentionally) |
24 |
because the m4-1.4.8-darwin7.patch touches configure.ac. |
25 |
|
26 |
So maybe you could bootstrap m4, try emerging the autotools, then |
27 |
emerging m4. Or perhaps you could disable the m4-1.4.8-darwin7.patch |
28 |
patch in the m4 ebuild? |
29 |
|
30 |
|
31 |
Matt. |
32 |
-- |
33 |
gentoo-alt@g.o mailing list |