Date: Wed, 03 Feb 1999 10:40:51 -0800 (PST) From: John Polstra <jdp@polstra.com> To: current@FreeBSD.ORG Subject: libpam related buildworld failures Message-ID: <XFMail.990203104051.jdp@polstra.com>
next in thread | raw e-mail | index | archive | help
There have been some reports of builds failing in libpam. With help
from Jon Hamilton, I've narrowed down the causes. There are at least
two different failure modes, but the solution is the same in either
case.
* Don't define OBJLINK. It is badly broken, and a libpam build
failure happens to be the first symptom you're likely to see.
* Don't define NOCLEAN.
* Scan your entire source tree and make sure there are no symbolic
links named "obj" there. Remove any that you find.
* Scan your source tree under "/usr/src/lib/libpam" and make sure
there are no symbolic links at all. Remove any that you find.
* Scan your source tree under "/usr/src/lib/libpam" and make sure
there are no files with names matching "*.[oa]" or "*.?o" there.
Remove any that you find.
Don't assume that a "make clean" or "make cleandir" will remove the
files above. Check manually using "find". Once your source tree is
cleaned up, if you avoid using OBJLINK, it will stay clean.
Note, these problems have nothing to do with libpam. It's just the
thing that's getting clobbered by polluted source trees resulting from
unrelated breakage.
John
---
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990203104051.jdp>