| 1 |
On Friday 24 June 2011 14:42:24 Alan Mackenzie did opine thusly: |
| 2 |
> Hi, Adam. |
| 3 |
> |
| 4 |
> On Fri, Jun 24, 2011 at 10:07:02PM +1000, Adam Carter wrote: |
| 5 |
> > >> No you just need to rebuild it, so emerge xf86-input-evdev |
| 6 |
> > > |
| 7 |
> > > This problem hit me too. Can you give us an explanation for |
| 8 |
> > > needing to rebuild evdev? Was there some missing |
| 9 |
> > > dependency in an ebuild, or something? |
| 10 |
> > |
| 11 |
> > If you update xorg (which OP didnt list, but a new version just |
| 12 |
> > went stable) you need to rebuild its drivers (unless they were |
| 13 |
> > automatically rebuilt due to version bump). |
| 14 |
> |
| 15 |
> Hmm. Recompiling the same source code produces a different binary? |
| 16 |
|
| 17 |
Not quite: |
| 18 |
|
| 19 |
Rebuilding the same sources against different headers produces a |
| 20 |
different binary. |
| 21 |
|
| 22 |
> Presumably, it uses C macros in a .h file which is part of xorg. Or |
| 23 |
> something like that. |
| 24 |
> |
| 25 |
> So evdev depends on xorg. Isn't there a way of expressing this in |
| 26 |
> evdev's ebuild? Something like the DEPEND variable? |
| 27 |
|
| 28 |
It's already there, but doesn't help as the update trigger never |
| 29 |
happens. |
| 30 |
|
| 31 |
Actually, you have the depend the wrong way round - evdev depends on |
| 32 |
xorg-server; to have the driver and for it to be useful, the xorg- |
| 33 |
server must be present, otherwise there is nothing for the drivers to |
| 34 |
build against. |
| 35 |
|
| 36 |
You want to force a rebuild that is the opposite of the DEPEND, but |
| 37 |
portage does not support that (it's a circular dependency). It will |
| 38 |
also not rebuild the driver as part of a regular update as there is |
| 39 |
not a new version of the driver, hence according to normal portage |
| 40 |
logic there is no need to do so. |
| 41 |
|
| 42 |
Make sense? |
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
alan dot mckinnon at gmail dot com |
Archives