>>>>> "jwackley" == Jonathan Wackley <[EMAIL PROTECTED]> writes:

jwackley> Here is the salient output from the build.  Please keep in
jwackley> mind that it is only representative, i.e. I have tried a
jwackley> permutation of flags of -D_POSIX_SOURCE and -D_HPUX_SOURCE
jwackley> through the --with-ccopts configure argument.

I doubt that's the actual issue.

jwackley> ../src/configure --with-cc="cc -Ae" --enable-shared
jwackley> --prefix=/usr/kerberos/hp11w_dynamic_123

[...]

jwackley> cc -Ae -L../../../lib -Wl,+s
jwackley> -Wl,+b,/net/salvador/space0/kerberos/hp11w_dynamic_123/lib -o ftpd
jwackley> ftpd.o ftpcmd.o glob.o popen.o vers.o radix.o secure.o  setenv.o
jwackley> ../../../krb524/libkrb524.a -lpty -lgssapi_krb5 -lkrb5util -lkrb4 -lkrb5
jwackley> -ldes425 -lk5crypto -lcom_err  -lcrypt
jwackley> /usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (ftpd.o) was
jwackley> detected. The linked output may not run on a PA 1.x system.
jwackley> /usr/ccs/bin/ld: Unsatisfied symbols:
jwackley>    alloca (code)
jwackley> gmake[3]: *** [ftpd] Error 1

Hm.  Most of the places that use alloca in the tree have to do with
yacc/bison.  Do you have some version of bison installed?  Does the
version of ftpcmd.c that's built from ftpcmd.y end up actually
attempting to use alloca?

---Tom

Reply via email to