public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: staticsafe <me@staticsafe.ca>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] nvidia-drivers-304.64 build failure against vanilla linux-3.7.4
Date: Sat, 26 Jan 2013 19:06:45 -0500	[thread overview]
Message-ID: <51046F95.7000605@staticsafe.ca> (raw)

I just grabbed vanilla 3.7.4 from kernel.org, the kernel build itself
went fine but when I did a modules-rebuild, the nvidia module failed to
build. As requested by the error message:

output of `emerge --info '=x11-drivers/nvidia-drivers-304.64'`:
http://sprunge.us/QLUN

output of `emerge -pqv '=x11-drivers/nvidia-drivers-304.64'`
http://sprunge.us/PfcV

complete build log:
http://sprunge.us/AQfS

Anyone have any ideas?

-- 
staticsafe
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
Please don't top post - http://goo.gl/YrmAb


             reply	other threads:[~2013-01-27  0:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27  0:06 staticsafe [this message]
2013-01-27  1:08 ` [gentoo-user] Re: nvidia-drivers-304.64 build failure against vanilla linux-3.7.4 walt
2013-01-30  6:51 ` [gentoo-user] " Raffaele BELARDI
2013-01-30 15:14 ` [gentoo-user] " Nikos Chantziaras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51046F95.7000605@staticsafe.ca \
    --to=me@staticsafe.ca \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox