I am one of the developers for MPQC (Massively Parallel Quantum Chemistry). MPQC supports x86, amd64, ppc, and ia64 architectures, but the current mpqc-2.2.2.ebuild only lists the x86 architecture. Committing this change for the amd64 and ppc architectures should be rather trivial. I'm uncertain as to whether Gentoo-IA64 currently supports blas and lapack which MPQC requires. Reproducible: Always Steps to Reproduce: 1. 2. 3. MPQC has been fully tested on the x86, amd64, ppc, and ia64 architectures.
I won't add ~amd64 atm, cause lapack-{atlas,config} still isn't (hard-)unmasked. Please leave this BUG open until this is done. ~x86 and ~ppc already seems to be in there. George: If your read: Can you tell me when you will be unmasking lapack-atlas ? I'm _really_ looking forward on that... ;-)
May wery well be pretty soon. We just caught what is hopefully the last check bug for recent g77 useflag stuff. Other than that it seems fine. I'll wait a few days and then pull it off the package.mask if nothing else turns up. Although on the amd64 front there might be a problem. The thing is that this package takes ifc useflag to have some libs compiled with ifc, which is binary ia32. I cannot add ~amd64 atm because of this optional functionality (I *can* test on amd64 btw since recently :)), as I am not sure how to handle this situation. It might be that it is possible to link amd64 and x86 code produced by ifc together, at least I briefly read something to that effect somewhere. Anybody has any decent info or pointers on that? George
Matt: moving your personal reply here, for easier future reference. I hope you don't mind ;), after all there was anything touchy here :) >The Intel compilers will be supporting amd64 (or EM64T in Intel >lingo). I believe either the latest Intel 8.0 compilers, or the latest >beta versions have this support. Good to know that. I tried to look at the "new features" on intell's site wrt 8.0, but it only mentions itanium-2, which is, well, 64 bit as well, so this may imply x86_64, but I am not sure. In any case ifc-8 is not in the tree yet, so we will have to wait for the version that has amd64 support before adding ~amd64 to the bunch of ebuilds that need ifc. Jared: added you to CC so that you are aware of the situation with other arches. It looks like you were the last to be taking care of ifc ebuilds, but please feel free to "reassign" to appropriate dev. George
> Although on the amd64 front there might be a problem. The thing is that this > package takes ifc useflag to have some libs compiled with ifc, which is binary > ia32. I cannot add ~amd64 atm because of this optional functionality (I *can* > test on amd64 btw since recently :)), as I am not sure how to handle this > situation. George, can't amd64 people just add ifc to their use.mask in profile?
Ok, lapack-config and lapack-atlas were just unmasked (both are ~arch at the moment). Added ~amd64 as well, after adding ifc to use.mask on both amd64 profiles (Donnie: thanks! Having not done multiple arches before I wasn't really sure how to proceed with these.) George
ia64 ppl: you're still missing ;-) All others have joined the party already...
Removing ppc from list
Looks like ia64 has unmasked the appropriate packages. mpqc-2.2.2 now ~amd64
