Hey Thierry, Ccing gentoo-alt, Schoopy <[email protected]> writes:
> You will find the modification I brought to the bootstrap script to > have it working under both a synology and a standard > gentoo. Great! > Everything is available at the following URL: > http://lausanne.isb-sib.ch/˜tschuepb/rap The url redirects me to http://www.isb-sib.ch/groups/lausanne.html anything wrong? > Currently I am trying to figure out how to install it fast from a > binary package server. Files can be found under > rap/binpkg/software/amdfam10. It is not yet working and still needs > some modifications inside the bootstrap_portage function especially to > set the correct profile (make.profile) and other portage config files. > Standart procedure as described on the gentoo wiki is not correct in > this case as one needs to first apply bootstrap tree and then > portage. Which procedure on gentoo wiki are you referring exactly? > After that I am a bit stuck as the binary packages are linked together > to glibc, readline, gdbm, etc... Not sure of this, I've never tried binary package. I only used distcc-pump to help weak boxes compiling. > Maybe you can help on that one. Feel free to test from the above > mentionned URL. > At last I would like your expertise on how one may deploy a prefix > with possibility to have it configure for many kinds of CFLAGS. Our > cluster currently has many kinds of intel and AMD models and I would > like to find the easiest way of having it deployed. I myself have many variants of Intel and arm boxes. The way of me is to keep a central directory of make.conf.HOST via unison, and symlink make.conf.HOST to EPREFIX/etc/portage/make.conf. use "include make.conf.common" in make.conf to manage common settings, too. > I could of course do a prefix per architecture and have it mounted on > the same path but I figured that using crossdev within prefix libc > could be more interesting to create binary packahes without the burden > to always change prefix. Crossdev on Prefix and cross compiling Prefix packages is explored by me to some extent, while limited to toolchain packages only. https://wiki.gentoo.org/wiki/Project:Android/build#Cross_Build Going beyond toolchain, even within @system would be too difficult, the smart build systems of perl and python will always drive you crazy trying to cross compile. I am not sure what "change prefix" means. But if you want to maintain Prefix instances with different EPREFIX, recompiling is inevitable AFAIK. > At last I intent to deploy module environment, and was thinking about > creating an eclass to overload some functions so that sci-biology for > example, may automatically be going through the creation of module > config files and placed in an environment variable path. Do you mean a ebuild built into a directory prefix other than EPREFIX? It can be readily achieved by emerge --prefix='/some/other/prefix' sci-biology/nice-package expect bugs though. Hope it helps, Benda
