| 1 |
On 2020-10-12 00:42, Neil Bothwick wrote: |
| 2 |
> On Sun, 11 Oct 2020 22:44:45 +0200, n952162 wrote: |
| 3 |
> |
| 4 |
>>> I don't know why it's written in such an opaque manner (a simple |
| 5 |
>>> `if` would suffice), but it seems like this error is printed only if |
| 6 |
>>> x86 is used and SSE2 is disabled, which doesn't make sense to me? |
| 7 |
>>> Is SSE2 required for building/ running NodeJS on x86 machines? |
| 8 |
>>> |
| 9 |
>> But how can my CPU be mistaken for a 32-bit machine? |
| 10 |
>> |
| 11 |
>> /Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz/ |
| 12 |
> It's not your CPU type but the type of CPU you are building for. The key |
| 13 |
> information from emerge --info is |
| 14 |
> |
| 15 |
> CHOST="i686-pc-linux-gnu" |
| 16 |
> |
| 17 |
> when it should be |
| 18 |
> |
| 19 |
> CHOST="x86_64-pc-linux-gnu" |
| 20 |
|
| 21 |
|
| 22 |
!!! wow. I'm dumbfounded. |
| 23 |
|
| 24 |
This is one of the machines I've been trying to get updated for awhile. |
| 25 |
It seemed this time that I'd found the proper incantation, because it |
| 26 |
got farther than before. But I discover now that I have NO saved |
| 27 |
emerge output from a system*.out or world*.out file that has "Emerging" |
| 28 |
lines in it (portage is very frugal with its unequivocal progress |
| 29 |
markers). Perhaps I have indeed used the wrong stage 3. |
| 30 |
|
| 31 |
Thank you for the tip. |
Archives