| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
|
| 6 |
What about per package environment variable declarations? I have been |
| 7 |
experiencing problems similar to Anton's: I compile my system using GCC, but |
| 8 |
I use ICC for some packages I use in intensive calculations. To do so, I must |
| 9 |
check every "world" update and manually set env variables such as CC. |
| 10 |
Additionnally, I do not use the same "CFLAGS" for these packages as for the |
| 11 |
rest of my system. I am not aware of any mechanism allowing me to automate |
| 12 |
this process with the current Portage system. |
| 13 |
|
| 14 |
What about having a file such as /etc/portage/package.env, that we could use |
| 15 |
to set per package compilers, "CFLAGS" and such? It would be pretty nice to |
| 16 |
be able to configure something along those lines: |
| 17 |
|
| 18 |
=app-sci/emboss-2.9* CC="icc" CFLAGS="IWantFastSequenceAlignments" |
| 19 |
|
| 20 |
... and not have to worry about manually setting environment variables |
| 21 |
whenever these packages are updated. |
| 22 |
|
| 23 |
This would certainly not solve all issues related to alternative compilers, |
| 24 |
but it would make many things easier, and we could get rid of silly "USE" |
| 25 |
flags like "icc", that are not related to the packages' content (the ebuilds |
| 26 |
could simply check their environment and adapt the build process or report a |
| 27 |
compiler incompatibility). |
| 28 |
|
| 29 |
What do you think? |
| 30 |
|
| 31 |
- -- |
| 32 |
Olivier Fisette (ribosome) |
| 33 |
Gentoo Linux Developer |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v1.2.5 (GNU/Linux) |
| 36 |
|
| 37 |
iD8DBQFBLSTgr/GGfYtwOqoRAnpoAJ9cUHhIXXIn9ViLKDrIy1QoADS3/gCeNGV6 |
| 38 |
I1BLY6gTmq8V/8to8V1eoYY= |
| 39 |
=/M8O |
| 40 |
-----END PGP SIGNATURE----- |
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives