| 1 |
Hi people, |
| 2 |
|
| 3 |
I just got hold of a Toshiba laptop, (P166MMX, 48MB ram.. so so small :) |
| 4 |
|
| 5 |
Naturally Gentoo had to go on it, no matter what the recommended spec |
| 6 |
for Gentoo was. |
| 7 |
|
| 8 |
Booting off 1.2 gave me the pcmcia networking I needed to get the 1.4 |
| 9 |
stage3 on it. Install went fine, and I was left with a bare bones, but |
| 10 |
networked, weakling of a laptop. |
| 11 |
|
| 12 |
So I need to build it's software on another machine... this I learned |
| 13 |
after updating glibc took 10 hours :) |
| 14 |
|
| 15 |
It so happens that the wonderous portage has already conceived this |
| 16 |
need, and 'ebuild <file.ebuild> package' on my desktop, will create |
| 17 |
binary packages I can install on my laptop. |
| 18 |
|
| 19 |
All I need to do in addition to this, is have a second make.conf on my |
| 20 |
desktop pc, with USE and compiler settings for the laptop. I simply |
| 21 |
switch to the laptop's make.conf when I build packages for it. |
| 22 |
|
| 23 |
There is however a problem that this setup doesn't address. |
| 24 |
If I build, (for example), xchat, on my desktop box, using the laptop |
| 25 |
make.conf, it will link the binary to a gnome library that exists on my |
| 26 |
desktop. This is even though I have -gnome in the laptop's make.conf |
| 27 |
USE variable. |
| 28 |
|
| 29 |
I am guessing that the writer of the xchat ebuild assumed that if a user |
| 30 |
had gnome, why not use it... it just wasn't worth checking a USE variable. |
| 31 |
|
| 32 |
Bad news for me, because short of unmerging gnome from my desktop box, |
| 33 |
building xchat for my laptop, then re-emerging gnome, there is no way my |
| 34 |
desktop machine can build xchat for my laptop. |
| 35 |
|
| 36 |
And no, I don't want gnome libs on the laptop :) |
| 37 |
|
| 38 |
For this trivial example, I built xchat on the laptop itself, (taking 25 |
| 39 |
odd mins), but for something meatier this presents a problem. |
| 40 |
|
| 41 |
Is there any way I can specify certain libraries to be excluded from a |
| 42 |
build, or even better somehow inform portage of what is available. I |
| 43 |
guess this would require portage to check for a library's package every |
| 44 |
time it is referenced, and make sure it is in the list of packages to |
| 45 |
use.. so not likely. |
| 46 |
|
| 47 |
Cheers people, |
| 48 |
MAL |
| 49 |
|
| 50 |
|
| 51 |
-- |
| 52 |
gentoo-dev@g.o mailing list |
Archives