From owner-freebsd-current@FreeBSD.ORG Sat Sep 6 15:46:56 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4845016A4BF for ; Sat, 6 Sep 2003 15:46:56 -0700 (PDT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1200A43FA3 for ; Sat, 6 Sep 2003 15:46:55 -0700 (PDT) (envelope-from null@pozo.com) Received: from quad.pozo.com (quad.pozo.com [192.168.0.61]) (authenticated bits=0) by pozo.com (8.12.9/8.12.9) with ESMTP id h86Mkrp6030665 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT); Sat, 6 Sep 2003 15:46:53 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <5.2.1.1.2.20030906154312.02f1f290@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Sat, 06 Sep 2003 15:46:53 -0700 To: Aaron Smith , freebsd-current@freebsd.org From: Manfred Antar In-Reply-To: <20030906203507.GP560@gelatinous.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: can't log in! openpam_load_module failures on strcpy, cgetclose X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2003 22:46:56 -0000 At 01:35 PM 09/06/2003 -0700, Aaron Smith wrote: >Hi everyone. login and sshd are both failing for me after a make world on >current. I have mergemaster'd, rebuilt world, ad infinitum. I've compared >/etc/pam.d with the source tree version and they're the same. > >I instrumented openpam_dynamic, and login is failing on 'strcpy': > >login: in openpam_dynamic(): pam_nologin.so: /usr/lib/pam_nologin.so: >Undefined symbol "strcpy" >login: in openpam_load_module(): no pam_nologin.so found >login: pam_start(): system error > >for sshd the failure is on 'cgetclose': > >sshd: in openpam_dynamic(): pam_nologin.so: /usr/lib/pam_nologin.so: >Undefined symbol "cgetclose" >sshd: in openpam_load_module(): no pam_nologin.so found >sshd: fatal: PAM: initialisation failed > >Now, there are T symbols for both of these in the respective binaries, >according to nm (at least before they are stripped). So just in case >stripping was an issue I figured I'd try unstripped binaries and rebuilt >them. No luck. > >Can anyone help me out? > >Thanks, >--Aaron >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" What version of bsd.lib.mk are you using ? There was a problem with version 1.152 From CVS log: Emergency backout of rev 1.152. This is a 100% guaranteed way to totally hose your system. You end up with just about everything statically linked (except for libpam.so), which then causes all the pam users to fail. eg: login, sshd, su etc all stop working because dlopen no longer works because there is no libc.so in memory anymore. gcc passes -L/usr/lib to ld. The /usr/lib/libxxx.so symlink is *not* a compatability link. It is actually the primary link. There should be no symlinks in /lib at all. Only /lib/libXX.so.Y. peter@daintree[9:27pm]/usr/bin-104> file yppasswd yppasswd: setuid ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 5.1.1, dynamically linked (uses shared libs), stripped peter@daintree[9:27pm]/usr/bin-105> ldd yppasswd yppasswd: libpam.so.2 => /usr/lib/libpam.so.2 (0x280d1000) peter@daintree[9:28pm]/usr/bin-106> Note no libc.so.5. Hence libpam.so.2 has unresolved dependencies. I believe this is also the cause of the recent buildworld failures when pam_krb5.so references -lcrypto stuff etc and when librpcsvc.so references des_setparity() etc. This change could not possibly have worked, unless there are other missing changes to the gcc configuration. It won't work with ports versions of gcc either. You need to get 1.151 or 1.153 and rebuild world ================================== || null@pozo.com || || Ph. (415) 681-6235 || ==================================