| 1 |
FWIW, while bringinging up a new dual AMD64 box last night, I got the exact |
| 2 |
same abort on autoconf during an emerge system. I solved it the same way, by |
| 3 |
manualy emerging autoconf and restarting the emerge with the -newuse flag. I |
| 4 |
didn't run into the aclocal problem, instead the emerge of samba caused a |
| 5 |
second abort for me. That appeared to be a genuine compile error, so I |
| 6 |
removed the samba use flag and continued the emerge system which completed |
| 7 |
without further error. |
| 8 |
|
| 9 |
On a side note, bringing this box up has been very frustrating. By default |
| 10 |
the kernel on the install CD enables both CPUs, I spent a week starting and |
| 11 |
restarting the install from various points. The problem was that the |
| 12 |
compiles would just stop in the middle of compiling some random package. No |
| 13 |
error message, no indicated system malfunction of any kind, the compiler |
| 14 |
just stopped doing anything. It appeared to be just the compiler that was |
| 15 |
hung, as a ctrl-c would return me to the command prompt. Forcing "nosmp" and |
| 16 |
"noapic" on the boot command line of the install CD resolved that hang. |
| 17 |
Unfortunately that was after trying a *lot* of other things and command line |
| 18 |
options. |
| 19 |
|
| 20 |
Regards, |
| 21 |
Bob Young |
| 22 |
|
| 23 |
|
| 24 |
-----Original Message----- |
| 25 |
From: Erwin Lang [mailto:lang.erwin@×××.at] |
| 26 |
Sent: Thursday, October 06, 2005 6:16 AM |
| 27 |
To: gentoo-user@l.g.o |
| 28 |
Subject: [gentoo-user] portage bugs? |
| 29 |
|
| 30 |
hi! |
| 31 |
During installation of a new system I recognised two things: |
| 32 |
1) `emerge -e system' aborted two times. |
| 33 |
* The first time the command autoconf was missing so I manually installed |
| 34 |
the package autoconf. |
| 35 |
* The second time the command aclocal was missing so I manually installed |
| 36 |
the package automake (which contains aclocal) |
| 37 |
I tried `emerge -ep system' an the two packages (autoconf and automake) are |
| 38 |
mentioned in the list of packages which portage will install. But it seems |
| 39 |
that portage installs them to late. |
| 40 |
2) after `emerge -e system' I tried to install the following packages: |
| 41 |
`emerge -va reiserfsprogs lvm2 syslog-ng vixie-cron postfix' |
| 42 |
vixie-cron needs an mta and tries to install ssmtp - which conflicts with |
| 43 |
postfix. portage didn't recognised that I mentioned an mta on command line. |
| 44 |
I worked around by mentioning postfix before vixie-cron on command line: |
| 45 |
`emerge -va reiserfsprogs lvm2 syslo-ng postfix vixie-cron' |
| 46 |
Then portage recognised postfix and didn't try to install another mta. |
| 47 |
Shouldn't portage be smart enough to solve this by itself? |
| 48 |
greetings |
| 49 |
erwin |
Archives