On Tue, Oct 06, 2020 at 02:34:22AM -0400, Jude DaShiell wrote:
> Hi Ashley,

Hi Jude,

> Changing -j2 to -j1 in /etc/portage/make.conf is doing the trick!  The
> amd64 southbridge system I use was built in 2007 so I maybe also ought to
> have used noapic in my boot parameters too since this system is old enough

Ah, I was hoping it was as simple as that!  Parallelism with Make can  spit  out
the most opaque and peculiar problems; they really  should  have  a  small  note
appended to emerge's failure message regarding this, as it causes  so  many  odd
issues.

As for disabling APIC, I'm not certain whether it will serve as a more permanent
solution for this particular issue or not. It's worth a try, I suppose, although
I am gravely doubtful.  Which motherboard and CPU do  you  have?   AMD  licenced
Intel's APIC for their Athlon series and onwards, the debut of which was over an
entire decade after your 2007 processor.

> it owes nobody a thing.

Despite what seems to be the modern consensus, electronic components should  not
break beyond repair for no reason.  I have an original 1974 rotary telephone sat
next to me and it still works perfectly (until British Telecom turns off support
for pulse dialling in 2025, the bastards); albeit, it is slightly more straight-
forward than a processor. ;-)

Anyway, try disabling APCI, re-enable Make parallelism, and get back to  us.   I
doubt it will do much with regards to compilation, although you never know  with
"-j N". LOL.

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA

Attachment: signature.asc
Description: PGP signature

Reply via email to