| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
W dniu 17.06.2011 18:41, Mike Frysinger pisze: |
| 5 |
> On Friday, June 17, 2011 05:01:10 Kacper Kowalik wrote: |
| 6 |
>> W dniu 17.06.2011 05:03, Mike Frysinger pisze: |
| 7 |
>>>> DEPEND="virtual/fortran" |
| 8 |
>>>> |
| 9 |
>>>>> RDEPEND="${DEPEND}" |
| 10 |
>>> |
| 11 |
>>> i'm not sure that RDEPEND is correct. do all fortran compilers |
| 12 |
>>> additionally require the fortran compiler to be available at runtime ? |
| 13 |
>> |
| 14 |
>> They require fortran runtime library if they don't link it statically. |
| 15 |
> |
| 16 |
> *if* there is a fortran runtime library in the first place. gcc provides one, |
| 17 |
> but does that mean all fortran compilers do ? |
| 18 |
|
| 19 |
At least all that I've used have it. Gcc, path64/open64/ekopath-bin, |
| 20 |
solstudio use shared lib. Pgi by default links statically, but have |
| 21 |
shared too. Ifort has only static, but has "ugliness" called Portability |
| 22 |
Library, which can be linked dynamically: |
| 23 |
|
| 24 |
xarth@aiur:~$ ifort -fpscomp nolibs unlink.F90 -lifport |
| 25 |
xarth@aiur:~$ ldd a.out | grep ifport |
| 26 |
libifport.so.5 => |
| 27 |
/opt/intel/Compiler/11.1/072/lib/intel64/libifport.so.5 (0x00007f0e05968000) |
| 28 |
|
| 29 |
It *really* makes things easier if virtual/fortran is in RDEPEND. Is it |
| 30 |
serious obstacle? |
| 31 |
Cheers, |
| 32 |
Kacper |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 35 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 36 |
|
| 37 |
iJwEAQECAAYFAk37n1oACgkQIiMqcbOVdxTt+AP7BCeC8Aru8otXmquDy1RcAg8j |
| 38 |
Cue952ty2FBn9R+O8P8p7H+FckP/qBcXIuSGdSq1tFR/0HNDlYjwZDIHliY/tUkm |
| 39 |
RQV4qY5nMp11yemI/VXnwFXZ1qwjpIoUypj2e3JnjozV3hfSCBdm3FQQYhi0ROls |
| 40 |
2ohZThxgrEL1Noq844A= |
| 41 |
=ISqo |
| 42 |
-----END PGP SIGNATURE----- |
Archives