From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] no keyboard no mouse
Date: Fri, 24 Jun 2011 16:57:05 +0200 [thread overview]
Message-ID: <6358552.mjGuFfGUtd@nazgul> (raw)
In-Reply-To: <20110624144224.GC7217@acm.acm>
On Friday 24 June 2011 14:42:24 Alan Mackenzie did opine thusly:
> Hi, Adam.
>
> On Fri, Jun 24, 2011 at 10:07:02PM +1000, Adam Carter wrote:
> > >> No you just need to rebuild it, so emerge xf86-input-evdev
> > >
> > > This problem hit me too. Can you give us an explanation for
> > > needing to rebuild evdev? Was there some missing
> > > dependency in an ebuild, or something?
> >
> > If you update xorg (which OP didnt list, but a new version just
> > went stable) you need to rebuild its drivers (unless they were
> > automatically rebuilt due to version bump).
>
> Hmm. Recompiling the same source code produces a different binary?
Not quite:
Rebuilding the same sources against different headers produces a
different binary.
> Presumably, it uses C macros in a .h file which is part of xorg. Or
> something like that.
>
> So evdev depends on xorg. Isn't there a way of expressing this in
> evdev's ebuild? Something like the DEPEND variable?
It's already there, but doesn't help as the update trigger never
happens.
Actually, you have the depend the wrong way round - evdev depends on
xorg-server; to have the driver and for it to be useful, the xorg-
server must be present, otherwise there is nothing for the drivers to
build against.
You want to force a rebuild that is the opposite of the DEPEND, but
portage does not support that (it's a circular dependency). It will
also not rebuild the driver as part of a regular update as there is
not a new version of the driver, hence according to normal portage
logic there is no need to do so.
Make sense?
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-24 15:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 8:47 [gentoo-user] no keyboard no mouse alain.didierjean
2011-06-24 8:59 ` Sebastian Beßler
2011-06-24 8:59 ` Adam Carter
2011-06-24 11:43 ` Alan Mackenzie
2011-06-24 12:03 ` Dale
2011-06-24 12:07 ` Adam Carter
2011-06-24 14:42 ` Alan Mackenzie
2011-06-24 14:57 ` Alan McKinnon [this message]
2011-06-25 9:50 ` Alan Mackenzie
2011-06-25 18:53 ` Alan McKinnon
2011-06-25 12:01 ` Volker Armin Hemmann
2011-06-25 17:36 ` Alan Mackenzie
2011-06-25 17:48 ` Dale
2011-06-25 20:23 ` Volker Armin Hemmann
2011-06-24 9:05 ` Matthew Finkel
2011-06-24 9:34 ` Neil Bothwick
2011-06-24 13:36 ` Mick
[not found] <658292104.5336901308919354379.JavaMail.root@spooler5n-g27.priv.proxad.net>
2011-06-24 12:43 ` Alain DIDIERJEAN
2011-06-24 12:53 ` Adam Carter
2011-06-26 6:08 ` Jonathan
2011-06-26 6:34 ` Alain DIDIERJEAN
2011-06-26 7:38 ` Jonathan
2011-06-24 22:00 ` Neil Bothwick
2011-06-24 22:22 ` Dale
2011-06-25 4:31 ` Pandu Poluan
2011-06-25 6:52 ` Alan McKinnon
2011-06-25 7:37 ` Alain DIDIERJEAN
2011-06-25 11:50 ` Neil Bothwick
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=6358552.mjGuFfGUtd@nazgul \
--to=alan.mckinnon@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