Re: Building Mozilla LDAP C SDK block linux
LA <[email protected]> Sat, 26 Oct 2019 17:28:05 -0700 (PDT)
| Newsgroups | gmane.comp.mozilla.devel.directory |
|---|---|
| Message-ID | <[email protected]> |
Pada Senin, 21 Desember 2015 18.21.12 UTC+7, [email protected] menulis: > Hi to all the gurus.. > > I have been trying to get the Mozilla c SDK compiled in-order to use it compile some old c source code that wil be used as a authentication plugiun module in a vendor product. The code was orininally compiled and was used on Solaris. We are migrating to Linux. > > Platform:- X86_64 > OS :- Linux ( 2.6.32-573.7.1.el6.x86_64) > > Downloaded these source codes & binaries:= > mozldap-6.0.7.tar (source code) > nss-3.11.tar ( compiled binaries) > nspr-4.6.tar ( compiled binaries) > > created folder structure as follows:- > Mozilla > |---- directory -- (contents of mozldap-6.0.7) > |---- dist > |-- nss-3.11 > |-- nspr-4.6 > > Steps:- followed > cd Mozilla/directory/csdk > ./configure USE_64=0 --with-nss=../../dist/nss-3.11 --with-nspr=../../dist/nspr-4.6 --with-nss-lib=../../dist/nss-3.11/lib --with-nss-inc=../../dist/nss-3.11/include --with-nspr-inc=../../dist/nspr-4.6/include --with-nspr-lib=../../dist/nspr-4.6/lib > > make > > --> The compilation fails. Not clear from the config.log or the make o/p as to what is the failure cause. > I am trying to build a 32 bit version only, since the vendor product is a 32 bit one, and the plugin code also needs to be 32 bit compiled. So I am trying to build the c asdk in 32 bit, so that I can use those 32 bit .so files and compile my custom auth code. > > --> config.log contents > configure:661: checking host system type > configure:682: checking target system type > configure:700: checking build system type > configure:972: checking for --with-svrcore > configure:1238: checking for --with-nss > configure:1261: checking for --with-nss-inc > configure:1283: checking for --with-nss-lib > configure:1526: checking for --with-nspr > configure:1554: checking for --with-nspr-inc > configure:1575: checking for --with-nspr-lib > configure:1952: checking for whoami > configure:2042: checking for c++ > configure:2074: checking whether the C++ compiler (c++ ) works > configure:2090: c++ -o conftest conftest.C 1>&5 > configure:2116: checking whether the C++ compiler (c++ ) is a cross-compiler > configure:2121: checking whether we are using GNU C++ > configure:2149: checking whether c++ accepts -g > configure:2198: cc -c conftest.c 1>&5 > configure:2215: cc -c conftest.c 1>&5 > configure: In function 'main': > configure:2211: warning: incompatible implicit declaration of built-in function 'exit' > configure:2237: checking for gcc > configure:2350: checking whether the C compiler (gcc ) works > configure:2366: gcc -o conftest conftest.c 1>&5 > configure:2392: checking whether the C compiler (gcc ) is a cross-compiler > configure:2397: checking whether we are using GNU C > configure:2425: checking whether gcc accepts -g > configure:2458: checking how to run the C preprocessor > configure:2540: checking for ranlib > configure:2572: checking for as > configure:2613: checking for ar > configure:2654: checking for ld > configure:2695: checking for strip > configure:2736: checking for windres > configure:3578: checking for gcc -pipe support > dummy-hello.c: In function 'main': > dummy-hello.c:2: warning: incompatible implicit declaration of built-in function 'exit' > configure:3600: gcc -c -pipe conftest.c 1>&5 > configure:3633: checking for perl5 > configure:5787: checking for dlopen > configure:5834: checking for dlopen in -ldl > configure:5881: checking whether gcc needs -traditional > configure:5929: checking for lchown > configure:5929: checking for strerror > configure:5929: checking for getaddrinfo > configure:5929: checking for getnameinfo > configure:5995: checking for pthread_create in -lpthreads > gcc -o dummy dummy.c -pipe -lpthreads > > --> The failure occurs when compiling the libldif60.so. I ran make with --debug=all > make[3]: Entering directory `/export/gcs1/data/mesh/apps/mozilla/directory/c-sdk/ldap/libraries/libldif' > ======= making ./libldif60.so > Putting child 0x0250c5b0 (libldif60.so) PID 18082 on the chain. > Live child 0x0250c5b0 (libldif60.so) PID 18082 > Reaping winning child 0x0250c5b0 PID 18082 > /usr/bin/ld -o libldif60.so ./line64.o > Live child 0x0250c5b0 (libldif60.so) PID 18085 > /usr/bin/ld: warning: cannot find entry symbol _start; defaulting to 00000000004000b0 > ./line64.o: In function `ldif_get_entry': > line64.c:(.text+0x2bb): undefined reference to `malloc' > line64.c:(.text+0x2cd): undefined reference to `realloc' > line64.c:(.text+0x307): undefined reference to `memcpy' > line64.c:(.text+0x326): undefined reference to `fgets' > ./line64.o: In function `ldif_put_type_and_value_with_options': > line64.c:(.text+0x482): undefined reference to `__ctype_b_loc' > line64.c:(.text+0x4ed): undefined reference to `__ctype_b_loc' > ./line64.o: In function `ldif_type_and_value_with_options': > line64.c:(.text+0x60a): undefined reference to `malloc' > ./line64.o: In function `ldif_getline': > line64.c:(.text+0x6dd): undefined reference to `strchr' > line64.c:(.text+0x74a): undefined reference to `strchr' > ./line64.o: In function `ldif_base64_decode': > line64.c:(.text+0x779): undefined reference to `__rawmemchr' > Reaping losing child 0x0250c5b0 PID 18085 > make[3]: *** [libldif60.so] Error 1 > Removing child 0x0250c5b0 PID 18085 from chain. > make[3]: Leaving directory `/export/gcs1/data/mesh/apps/mozilla/directory/c-sdk/ldap/libraries/libldif' > Reaping losing child 0x01193630 PID 18048 > make[2]: *** [export] Error 2 > Removing child 0x01193630 PID 18048 from chain. > make[2]: Leaving directory `/export/gcs1/data/mesh/apps/mozilla/directory/c-sdk/ldap/libraries' > Reaping losing child 0x0244e1a0 PID 18010 > make[1]: *** [export] Error 2 > Removing child 0x0244e1a0 PID 18010 from chain. > make[1]: Leaving directory `/export/gcs1/data/mesh/apps/mozilla/directory/c-sdk/ldap' > Reaping losing child 0x01af87c0 PID 17970 > make: *** [export] Error 2 > Removing child 0x01af87c0 PID 17970 from chain. > > Apprecite all inputs on wwhat could be the problem ? or Any pointers on how to proceed further. Apprecite any help.