configure output contains: checking for Kerberos (/usr/kerberos)... checking for AFS (/usr/afsws)... checking for afs/kauth.h... no checking for afs/kautils.h... no checking for afs/auth.h... no no
Judging from your configure output, you have the /usr/afsws directory in place, and do not have /usr/include/afs/{kauth.h,kautils.h,auth.h}. On my system, I get: checking for Kerberos (/usr/kerberos)... checking for AFS (/usr/afsws)... checking for afs/kauth.h... yes checking for afs/kautils.h... yes checking for afs/auth.h... yes yes I think: - it compiles without AFS-support on installations with old (non-FHS-compliant) openafs installations - it compiles with AFS-support whenever someone with a new (FHS-compliant) openafs installation also creates the directory /usr/afsws (hence the output above). Suggestion: remove this check - the ebuild itself is currently totally AFS-unaware
No, I do have /usr/afsws as it contains the binaries I use to distribute within the cell. I just wanted to make you aware of yet another dependency on afs. But am in contact with developers of mpich and mpich2 and some fixes will appear shortly. anyway, this I get with mpich-1.2.7: configure:1423: checking for Kerberos (/usr/kerberos) configure:1495: checking for AFS (/usr/afsws) configure:1503: checking for afs/kauth.h configure:1513: icc -E conftest.c >/dev/null 2>conftest.out configure(1509): catastrophic error: could not open source file "afs/kauth.h" #include <afs/kauth.h> ^ configure: failed program was: #line 1508 "configure" #include "confdefs.h" #include <afs/kauth.h> configure:1537: checking for afs/kautils.h configure:1547: icc -E conftest.c >/dev/null 2>conftest.out configure(1543): catastrophic error: could not open source file "afs/kautils.h" #include <afs/kautils.h> ^ configure: failed program was: #line 1542 "configure" #include "confdefs.h" #include <afs/kautils.h> configure:1571: checking for afs/auth.h configure:1581: icc -E conftest.c >/dev/null 2>conftest.out configure(1577): catastrophic error: could not open source file "afs/auth.h" #include <afs/auth.h> ^ configure: failed program was: #line 1576 "configure" #include "confdefs.h" #include <afs/auth.h> It's clear that I have to pass -I/usr/afsws/include in CPPFLAGS. ;)
Come on. We're talking Gentoo here. You know perfectly well that Gentoo chooses to put OpenAFS in FHS locations. Therefore the only thing that needs to be adapted to get this thing working properly, is to remove the requirement that /usr/afsws exists, just as I said in my previous comment. Yes, I did test this myself. You can pass all the -I/usr/afsws/include in CPPFLAGS that you want on your own system, but please, your last remark is just here to confuse any developer that would need to check up on this later. So now to get this straight: when using one of the newer openafs ebuilds (>=1.2.13) that will be promoted to stable, the include files required will be in /usr/include/afs/... The checking for /usr/afsws is for Transarc-paths, which aren't used on Gentoo and will therefore not be found, thus this check should be omitted if AFS-support is wanted.
So follow-up for comment #3: yes, so someone has to patch configure so it finds the headers in FHS. ;-)
Fixed in CVS, sorry for the delay.
