public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Need ebuild no longer in Portage
Date: Fri, 4 Jan 2008 15:53:37 -0800	[thread overview]
Message-ID: <49bf44f10801041553t672a8c9bi5deaeed766757156@mail.gmail.com> (raw)
In-Reply-To: <flmdec$t7b$1@ger.gmane.org>

> >> ISTR that "make prepare" isn't sufficient.  You have to do a
> >> "make".  IIRC, you can kill it once it starts compiling "real
> >> code".
> >
> > I can't keep up with the acronyms
>
> I seem to recall. :)
>
> > but I did a full make and I still get the same error.  Should
> > I be booted into the same kernel that /usr/src/linux points to
> > when compiling nvidia-modules?
>
> I didn't think that was required, but that's probably how I've
> always done it, so it's worth a shot.

Same result unfortunately.  Is it possible that this version of
nvidia-drivers isn't compatible with 2.6.23?

- Grant
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2008-01-05  0:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04  6:22 [gentoo-user] Need ebuild no longer in Portage Grant
2008-01-04  6:29 ` Dirk Heinrichs
2008-01-04  6:57   ` William Kenworthy
2008-01-04 15:58     ` Grant
2008-01-04 18:46       ` Jesús Guerrero
2008-01-04 19:01         ` Grant
2008-01-04 19:10           ` Grant
2008-01-04 21:04             ` [gentoo-user] " Grant Edwards
2008-01-04 22:39               ` Grant
2008-01-04 22:54                 ` Grant Edwards
2008-01-04 23:42                   ` Dale
2008-01-04 23:53                   ` Grant [this message]
2008-01-04 23:57                   ` Grant
2008-01-05  2:04           ` [gentoo-user] " Renat Golubchyk
2008-01-05  9:11             ` Alan McKinnon

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=49bf44f10801041553t672a8c9bi5deaeed766757156@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --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