R-1.9.1 depends on these 2 , they compile, but I would not know how to test them more than having a working R-1.9.1
now marked as ~ppc64
dev-libs/libf2c/libf2c-20021004-r1.ebuild: x86 ['sys-devel/gcc']
dev-libs/libf2c/libf2c-20021004-r1.ebuild: sparc ['sys-devel/gcc']
dev-libs/libf2c/libf2c-20021004.ebuild: x86 ['sys-devel/gcc']
this prevents me from repoman commit, anyone ??
I added --ignore-other-arches, but it might still be a good thing to fix...
f2c itself works great, the generated source code is valid for 64bit archs.
If you want to test f2c thoroughly then use it to compile R, blas, lapack or whatever else application that features the f2c useflag.
However, on amd64 we experienced problems with f2c.h and gcc. (BUG #61042, gcc generates bad assembler code when using -O2 CFLAG). A bug report has already been
sent to the gcc-team.
Regarding the Repoman output: i don't get any DEPEND.bad.
I've done some small tests and f2c seems to work. As it is now marked ~ppc64 for
quite some while, I marked it stable.
Did you test it on ppc64 by compiling R-2.0.0 ?
see BUG #61042...
Yes, I have R installed, but as far as I can see only R versions <2.0.0 have the f2c useflag.
Therefor R was marked stable before f2c.
Maybe I'm missing an argument, that would have prevented me from marking f2c stable. If I did so, please tell me. :-)