View previous topic :: View next topic |
Author |
Message |
Mike81 n00b
Joined: 05 Jan 2011 Posts: 39
|
Posted: Sun Apr 28, 2013 3:02 pm Post subject: CFlags and Binhost |
|
|
Hi,
I have 10 systems with Intel Xeon E5405 CPUs and 6 systems with Intel Xeon E3-1270 CPUs.
One E5405 box should be the binhost for all the other boxes.
I am not sure if I understand CFlags right:
The E5405 doesn't support SSE4.x, AVX and AES which the E3-1270 does.
- What will now happen, when I build OpenSSL or the kernel on the binhost which doesn't support AES (gcc will set the "-noaes" flag)?
When I install the created binpackages on a AES-capable box, will these box use AES or will I be unable to use AES-NI on any box, because while compiling, AES wasn't available and therefore it wasn't activated?
- Some people recommend to run the binhost for multiple configurations in chroot. Can I create a binpackage with "-avx -aes" CFlags (=march=corei7-avx) on a box, which is actual a nocona/core2 box?
Thanks. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54237 Location: 56N 3W
|
Posted: Sun Apr 28, 2013 9:34 pm Post subject: |
|
|
Mike81,
Run one binhost with two optimised sets of code and have all 16 systems contribute to the builds.
distcc is a wonderful tool.
The binhost box need not do all the building.
In your case, a chroot won't help as you need to be able to execute the code in the chroot ... or at least the toolchain. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Mike81 n00b
Joined: 05 Jan 2011 Posts: 39
|
Posted: Mon Apr 29, 2013 10:33 pm Post subject: |
|
|
How would I run one binhost with multiple sets without chroots? Do you have a link where I can read more about that?
Next week I'll also add some AMD opterons to the lab, would be nice to support this architecture, too (then it should be 3 sets, 2 intel + 1 amd?). |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54237 Location: 56N 3W
|
Posted: Mon Apr 29, 2013 10:48 pm Post subject: |
|
|
Mike81,
A BINHOST is just a directory on a server you point your clients to.
To keep the explaination simple, lets say ome machine of each type serves as a BINHOST for its type, now you have the same directory structure on both machines.
By default, your packages would be in /usr/portage/packages on each BINHOST.
However, you can put your packages anywhere, so on one arch they could be in /usr/portage/packages/E5405 and on the other /usr/portage/packages/E3-1270
Having fixed the namespace collision for the packages, there is no reason why they cannot all be hosted on the same machine if you wish.
You can even add /usr/portage/packages/opteron to the mix.
Again they can all build for each other, with distcc you have a single compile farm, with one system from each arch leading the build for that arch.
For a working example, look at tinderbox.dev.gentoo.org
Hmm ... maybe thats not a good example as its almost empty but the directory structure is there. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|