This build has failed three times for me. Here is the applicable portion of the build log:

rm: cannot remove 'Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ': Is a directory
Assembler messages:
Fatal error: can't create Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o: No such file or directory
pk11cert.c: In function 'pk11_fastCert':
pk11cert.c:231:14: warning: variable 'status' set but not used [-Wunused-but-set-variable]
     PRStatus status;
              ^
pk11cert.c: In function 'PK11_MakeCertFromHandle':
pk11cert.c:297:12: warning: variable 'swapNickname' set but not used [-Wunused-but-set-variable]
     PRBool swapNickname = PR_FALSE;
            ^
pk11cert.c:296:12: warning: variable 'isFortezzaRootCA' set but not used [-Wunused-but-set-variable]
     PRBool isFortezzaRootCA = PR_FALSE;
            ^
pk11cert.c: In function 'PK11_TraverseCertsForNicknameInSlot':
pk11cert.c:2007:28: warning: variable 'pk11cb' set but not used [-Wunused-but-set-variable]
     struct nss3_cert_cbstr pk11cb;
                            ^
pk11cert.c: In fupk11cert.c:2151:21: warning: unused variable 'td' [-Wunused-variable]
     NSSTrustDomain *td = STAN_GetDefaultTrustDomain();
                     ^
make[2]: *** [Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ/pk11cert.o] Error 2
make[2]: *** Waiting for unfinished jobs....
pk11load.c: In function 'SECMOD_UnloadModule':
pk11load.c:569:28: warning: unused variable 'status' [-Wunused-variable]
                   PRStatus status = PR_UnloadLibrary(softokenLib);
                            ^
pk11merge.c: In function 'pk11_mergeByObjectIDs':
pk11merge.c:852:15: warning: 'error' may be used uninitialized in this function [-Wmaybe-uninitialized]
  PORT_SetError(error);
               ^
pk11merge.c:753:9: note: 'error' was declared here
     int error;
         ^
make[1]: *** [libs] Error 2
make: *** [libs] Error 2
nction 'PK11_FindCertFromDERCertItem':

Each failure involved not being able to remove the directory "Linux3.8_x86_64_glibc_PTH_64_OPT.OBJ" It appears that if the "build" can't remove the directory it thinks it can't create the file. I'm going to stick my nose into the Makefile and see if I can find what's happening. I just wanted to see if anyone else had noticed this and/or if anyone knew any solutions.

Thanks,
Dan


-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to