Compiling Ebuilds on another machine

rmsousa · n00b Joined: 21 Mar 2003 Posts: 4

I happen to run a pretty slow machine at home, and a pretty fast machine at university, both with CDRW access. I want to "prepare" the sources to the apps I will later emerge, so that I can:

1. Prepare the sources at home, with my CFLAGS and stuff, leaving them one 'make' away from being built
2. Transfer them to university computers, run make _there_ (with my home CFLAGS)
3. Transfer the compiled programs back home
4. Finally emerge the compiled programs
5. ...
6. Profit!!!

Even if there is a way to do that, I'd like to suggest (if there isn't such a thing already) a --prepare-sources flag to emerge, to do the first step on a single command line.

Qvantamon

PS: Forgot to say, yes, both machines run the same GCC (3.2.2). Gotta take a look at GLIBC though...

M.A. · Posted: Fri Mar 21, 2003 9:25 pm Post subject:

Maybe you can try this:

On your fast machine:
- Create a new directory wherever you want and untar there a stage 3 tarball optimized for your fast machine.
- Copy the original portage tree to the new one (so you will not need to do an 'emerge sync' after doing chroot).
- Do chroot to the new directory.
- Change make.conf and set de CFLAGS and USES desired for your slow machine.
- Now, you can emerge the packages with the option --buildpkgonly (this creates binary packages), and take them to your machine at home. Maybe it will be more convenient to use --buildpkg for not building usual dependencies each time. I will test it, as I have very similar problem, but I have no time by now (probably next week...).
On your slow machine you only have to do 'emerge --usepkg package.tbz2' (set $PKGDIR before to the path to the packages). See man emerge, or emerge --help.
That is probably a bit tricky. Maybe another posibility is to write a little script that changes make.conf to the desired for the slow machine, do the emerge, and restores the original make.conf. But I doubt it would work fine...

Hope it helps a bit...

rmsousa · n00b Joined: 21 Mar 2003 Posts: 4

Sorry, I forgot something essential on the previous post.
It is not "my" fast computer, it is "the university's" fast computer. Unfortunately chroot requires the root password, which is not an option in this case.
I was thinking about emerge -<download and extract and patch and configure>, and only _compiling_ at the university...
btw, 6 hours compiling XFree86 and it is still going...