On Tue, Jun 12, 2018 at 1:31 PM, Ian Zimmerman <[email protected]> wrote:
> I have had it with compiling stuff from source on my laptop. It is just
> too slow. So I would like to create binary packages on my desktop and
> then just tell the laptop to use them.
>
> Simple enough, except that the desktop is AMD Phenom, and the laptop is
> Intel 64 bit Atom. Up to now, each system had unique CFLAGS to squeeze
> as much performance as possible.
>
> On the desktop:
> CFLAGS="-march=barcelona --param l1-cache-size=64 --param
> l1-cache-line-size=64 --param l2-cache-size=512 -O2 -pipe"
>
> On the laptop:
> CFLAGS="-march=ivybridge --param l1-cache-size=32 --param
> l1-cache-line-size=64 --param l2-cache-size=4096 -O2 -pipe"
>
> I don't want to give up these tunings, but from the wiki page [1] I can
> see no straightforward way to have different CFLAGS when compiling binary
> packages, from the normal CFLAGS when installing directly from source on
> the host system. Is the only way of doing this to set up a full-blown
> cross-development environment?
>
> [1]
> https://wiki.gentoo.org/wiki/Binary_package_guide
>
Use crossdev to generate an x86_64-pc-linux-gnu (or x86) toolchain.
You can specify something in place of "pc" to identify the system and
be fairly compliant, or you can invent your own naming and specify the
architecture manually. This will create a root in /usr with the name
given that will have a make.conf in /usr/${name}/etc/portage and
generated packages in /usr/${name}/usr/portage/packages.
Cheers,
R0b0t1
