| 1 |
On Mon, 20 Feb 2017 18:34:47 -0500, Walter Dnes wrote: |
| 2 |
|
| 3 |
> Reading https://wiki.gentoo.org/wiki/Binary_package_guide still leaves |
| 4 |
> me uncertain. I have an ancient 32-bit Atom netbook. I've installed |
| 5 |
> uclibc-ng Gentoo on it. Building big packages on it is a pain. I can |
| 6 |
> do an identical install in a QEMU VM, and distcc into it. But that |
| 7 |
> doesn't catch all compiling work. |
| 8 |
> |
| 9 |
> What I'd like to do is build binaries in a chroot on my desktop, |
| 10 |
> assuming a 32-bit uclibc-ng chroot on a 64-bit glibc host is possible. |
| 11 |
> Because the cpus are different, I would need to use different CFLAGS |
| 12 |
> (and CXXFLAGS) variables for when the host updates its own files, versus |
| 13 |
> when it builds files for the netbook. |
| 14 |
|
| 15 |
If the chroot is identical to your netbooks's install in terms of |
| 16 |
*FLAGS, USE, @world etc, then yes. I used to do it this way when I had an |
| 17 |
Atom netbook. I even build for a low memory 486 system in the same way. |
| 18 |
|
| 19 |
> Finally, is it possible for the client (the netbook) to notify the |
| 20 |
> host that it needs certain packages built? I plan to run with |
| 21 |
> "--getbinpkgonly" on the netbook. |
| 22 |
|
| 23 |
You don't need to if the systems are the same. Set both systems to use |
| 24 |
the same $PKGDIR, set FEATURES=buildpkg in the chroot and do a world |
| 25 |
update. Then do the same update on the netbook but with -K. |
| 26 |
|
| 27 |
I used a script to control this that basically synced world and most |
| 28 |
of /etc/portage before entering the chroot, although I later switched to |
| 29 |
using containers as they make life so much easier. |
| 30 |
|
| 31 |
Oh, and you don't need a package server, just export PKGDIR via NFS and |
| 32 |
mount it on the netbook. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Neil Bothwick |
| 37 |
|
| 38 |
Artificial Intelligence usually beats real stupidity. |
Archives