On Wednesday 12 November 2008 22:25:31 Matthias Bethke wrote: > Hi Peter, > > on Mon, Nov 10, 2008 at 10:50:32AM +0000, you wrote: > > I'm still having a bit of bother with crossdev. If I emerge -upDvtN > > world I get this warning (omitting the N makes no difference): > > > > !!! The following installed packages are masked: > > - cross-i686-pc-linux-gnu/linux-headers-2.6.23-r3 (masked by: ~amd64 > > keyword) > > I had a similar issue just recently when I built a crossdev environment > for ARM on an amd64 system. I'm not exactly sure how it happened any > more but I suppose it has to do with a later version of linux-headers > being stable for the platform you want to crosscompile for than for your > native one. Which isn't the case when I look now, perhaps the keywords > have just been updated?
Mysterious. It isn't happening any more; updating the system is straightforward once again. Searching for cross* on the whole file-system turns nothing up either, so I suppose I should just be thankful that the problem's gone away (pro tem, at least). I do notice though that I have a new file: /etc/portage/categories, which contains "cross-i686-pc-linux-gnu". (Well, it has a January date, so it isn't new - I just hadn't noticed it before.) And the only linux-headers I have are the standard kernel headers - nothing to do with cross-compiling. > For me, installing crossdev with -s1 helped, I don't know what you mean there. > I'm only compiling for an embedded system anyway so I don't need the > headers. Maybe just try again after an rsync? I run emerge --sync most days, so I wasn't incurring penalties by running an out-of-date system. Thanks for the help anyway. -- Rgds Peter
