On Fri, Jan 27, 2012 at 6:46 PM, luxInteg <lux-in...@btconnect.com> wrote: > On Friday 27 January 2012 16:21:34 Matijn Woudt wrote: >> It seems to me that you have 2 gssapi header files installed on your >> system. I don't know much about heimdal etc, but note that one is in >> /usr/local/include and the other one in /usr/include/gssglue/gssapi >> >> - Matijn > > here is my updated build sequence (i.e. fresh build) (everything in > /usr/local ) > > --1--heimdal-1.5.2 > --2--libevent2 > --3--libnfsidmap > --4--libgssapi (omitted) > --5--libgssglue > --6--librpcsecgss > --7--nfs-utils-1.2.5 > > the build failed like this:- > > ############## > from context_heimdal.c:44: > /usr/local/include/gssglue/gssapi/gssapi.h:42:2: error: #error It appears you > have already included the Heimdal gssapi.h file > context_heimdal.c: In function 'write_heimdal_enc_key': > context_heimdal.c:76:3: warning: implicit declaration of function > 'gssd_k5_err_msg'
Right, Looking at context_heimdal.c, there's a note at line 44, saying /* Must use the heimdal copy! */ This means that gcc is wrong in including the libgssglue. While you might be able to solve this by letting GCC know you want to prefer one include directory over the other one (don't know if possible), it might be easier to just remove the #include <gssapi.h> from line 44 of context_heimdal.c. That should fix the problem. - Matijn > --- > -- > make[2]: *** [gssd-context_heimdal.o] Error 1 > ############## > > the nub of the problem seems to be:- > > --4--libgssapi can be safely omitted but nfs-utils-1.2.5 calls for > --5--libgssglue and this also provides a ~/gssapi.h that seems to be > preferred to that provided by heimdal. > > ----- > luxInteg -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
