--On Sunday, July 22, 2001 12:39:18 -0500 Charles Clancy
<[EMAIL PROTECTED]> wrote:
> Second, I tried adding '-xarch=v9' to the XCFLAGS line of
> src/config/Makefile.sun4x_58, to compile EVERYTHING as 64-bit. That
> didn't work either:
>
> -------------------------
> /opt/SUNWspro/bin/cc -g -I.
> -I/afs/cs.rose-hulman.edu/openafs/source/openafs-1.1.1/sun4x_58/dest/inc
> lude -O
> -I/afs/cs.rose-hulman.edu/openafs/source/openafs-1.1.1/src/config -dy
> -Bdynamic -xarch=v9 install.c -o pinstall -lresolv -lsocket -lnsl -lintl
> -ldl ;; \
> esac
> Undefined first referenced
> symbol in file
> sys_errlist install.o
> sys_nerr install.o
> ld: fatal: Symbol referencing errors. No output written to pinstall
> make[3]: *** [pinstall] Error 1
> make[3]: Leaving directory
> `/afs/cs.rose-hulman.edu/openafs/source/openafs-1.1.1/src/pinstall'
> -------------------------
I'm not sure how to continue. The error above is familiar to me, because
sendmail had the same problem. The reason is that those two sysmbols are
only in the 32-bit version of Sun's libc, not in the 64-bit version (go
figure). Anyway, it was easy enough to fix for sendmail, because the
alternative that Sun offers is strerror and sendmail already had support
for that, so that I only had to change a #define.
Alas, it looks like OpenAFS pretty much relies on those two calls. Maybe
it'd be possible to build the PAM modules without needing them, but it
looks like it's going to take a lot of trial and error unless someone with
more intimate knowledge of the interdependencies involved tells me/us
exactly which libs are needed...
Cheers, Sebastian Hagedorn
--
Sebastian Hagedorn M.A. - RZKR, Zimmer 18
Zentrum f�r angewandte Informatik - Unversit�tsweiter Service RRZK
Universit�t zu K�ln / Cologne University - Tel. +49-221-478-5587
PGP signature
