On Thu, 23 Apr 2009 00:04:13 +0200, Alan McKinnon <alan.mckin...@gmail.com>
wrote:
> On Wednesday 22 April 2009 23:45:19 Peter Humphrey wrote:
>> On Wednesday 22 April 2009 11:30:27 Xavier Parizet wrote:
>> > Can you repost emerge output using MAKEOPTS="-j1" to see what make
>> > command is launched.
>> > Try also to run make prepare in your kernel source tree before.
>>
>> # cd /usr/src/linux
>> # make prepare
>> # MAKEOPTS="-j1" emerge nvidia-drivers
>>
>> This time it compiled just fine.
>
> I reckon the maintainer of the nvidia-driver ebuild would be *very*
> interested
> in this. "-j" is well known for causing weird faults.
>
> I recommend submitting a bug along with all build logs etc
I think the MAKEOPTS was not the problem, but only the make prepare... I
remember to see before that "sometimes", the kernel source tree is no more
up-to-date with the last kernel build, so when i see that problems, the
first thing to do is to make mrproper && make oldconfig && make prepare to
get a clean up-to-date kernel build tree.
Cheers.
--
Xavier Parizet
YaGB : http://gentooist.com
GPG : DC81 6FEE 6EBE FCE4
1C18 202F E575 4A5D 036D 1408
