Apologies - actual error earlier in the process - when compiling LDAP:

Making all in LDAP
gcc -DHAVE_CONFIG_H  -I../../.. -I../../../include -I../../../src  
-I../../../include  -I../../../libltdl  -I.    -Wall -Wpointer-arith 
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wcomments -Werror 
-D_REENTRANT -pthreads -Wall -g -O2 -MT squid_ldap_auth.o -MD -MP -MF 
.deps/squid_ldap_auth.Tpo -c -o squid_ldap_auth.o squid_ldap_auth.c
mv -f .deps/squid_ldap_auth.Tpo .deps/squid_ldap_auth.Po
/bin/bash ../../../libtool --tag=CC    --mode=link gcc -Wall -Wpointer-arith 
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wcomments -Werror 
-D_REENTRANT -pthreads -Wall -g -O2   -g -o squid_ldap_auth squid_ldap_auth.o 
../../../compat/libcompat.la  -L../../../lib -lmiscutil  -lldap    -lm -lsocket 
-lresolv -lnsl
libtool: link: gcc -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes 
-Wmissing-declarations -Wcomments -Werror -D_REENTRANT -pthreads -Wall -g -O2 
-g -o squid_ldap_auth squid_ldap_auth.o  ../../../compat/.libs/libcompat.a 
/usr/sfw/lib/libstdc++.so -L/usr/sfw/lib -lgcc_s 
-L/apps/cwapps/deployCSL/squid-3.1.19/lib -lmiscutil -lldap -lm -lsocket 
-lresolv -lnsl -pthreads -R/usr/sfw/lib -R/usr/sfw/lib
Undefined                       first referenced
 symbol                             in file
ldap_start_tls_s                    squid_ldap_auth.o
ldap_initialize                     squid_ldap_auth.o
ber_pvt_opt_on                      squid_ldap_auth.o
ld: fatal: Symbol referencing errors. No output written to squid_ldap_auth
collect2: ld returned 1 exit status
*** Error code 1



-----Original Message-----
From: Justin Lawler 
Sent: Saturday, February 11, 2012 2:52 PM
To: [email protected]
Subject: RE: [squid-users] compile error on Squid 3.1.18

HI,

I'm getting the same problem on 3.1.19 on solaris:

list='compat lib snmplib libltdl scripts src icons  errors doc helpers 
test-suite tools'; for subdir in $list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (CDPATH="${ZSH_VERSION+.}:" && cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'

Any suggestions?

Thanks,
Justin

-----Original Message-----
From: kzl [mailto:[email protected]]
Sent: Tuesday, December 06, 2011 2:20 PM
To: [email protected]
Subject: [squid-users] compile error on Squid 3.1.18

There's error thrown while compiling Squid 3.1.18 in Solaris Sparc which never 
experience in earlier version like 3.1.17, 3.1.16, 3.0.15 Anyone having any 
idea what's the problem? 

Making all in compat
/bin/bash ../libtool --tag=CXX    --mode=link g++ -Wall -Wpointer-arith 
-Wwrite-strings -Wcomments -Werror  -D_REENTRANT -pthreads -g -O2   -g 
-olibcompat.la  assert.lo compat.lo GnuRegex.lo
libtool: link: false cru .libs/libcompat.a .libs/assert.o .libs/compat.o 
.libs/GnuRegex.o
*** Error code 1
make: Fatal error: Command failed for target `libcompat.la'
Current working directory /home/squid-3.1.18/compat
*** Error code 1
The following command caused the error:
fail= failcom='exit 1'; \
for f in x $MAKEFLAGS; do \
  case $f in \
    *=* | --[!k]*);; \
    *k*) failcom='fail=yes';; \
  esac; \
done; \
dot_seen=no; \
target=`echo all-recursive | sed s/-recursive//`; \ list='compat lib snmplib 
libltdl scripts src icons  errors doc helpers test-suite tools'; for subdir in 
$list; do \
  echo "Making $target in $subdir"; \
  if test "$subdir" = "."; then \
    dot_seen=yes; \
    local_target="$target-am"; \
  else \
    local_target="$target"; \
  fi; \
  (CDPATH="${ZSH_VERSION+.}:" && cd $subdir && make  $local_target) \
  || eval $failcom; \
done; \
if test "$dot_seen" = "no"; then \
  make  "$target-am" || exit 1; \
fi; test -z "$fail"
make: Fatal error: Command failed for target `all-recursive'
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
http://www.amdocs.com/email_disclaimer.asp

Reply via email to