From owner-freebsd-stable Mon Jun 11 15:20:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bkmls01.bak.rr.com (bkmls01.bak.rr.com [24.30.163.15]) by hub.freebsd.org (Postfix) with ESMTP id 7BA5E37B401 for ; Mon, 11 Jun 2001 15:20:14 -0700 (PDT) (envelope-from rjackson@cs.csubak.edu) Received: from cs.csubak.edu ([24.161.200.221]) by bkmls01.bak.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with ESMTP id com; Mon, 11 Jun 2001 15:20:13 -0700 Message-ID: <3B254497.4090001@cs.csubak.edu> Date: Mon, 11 Jun 2001 15:22:15 -0700 From: Russell Jackson User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.2-RELEASE i386; en-US; rv:0.9) Gecko/20010525 X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: stable@FreeBSD.ORG Subject: Re: Why is the STABLE branch not so stable anymore? References: <20010611172443.A18552@home.com> <3B25405D.2090209@cs.csubak.edu> <20010611150838X.jkh@osd.bsdi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > Short answer: -stable builds fine. > > Long answer: It only builds fine if you don't use non-standard build > flags like SHARED=symlinks, which some people appear to be using since > they're reporting problems. On a completely stock -stable system as > of yesterday, I can report: > > >>>>elf make world started on Sun Jun 10 12:28:33 PDT 2001 >>>>elf make world completed on Sun Jun 10 13:23:54 PDT 2001 >>>>Kernel build for WINSTON started on Sun Jun 10 13:23:54 PDT 2001 >>>>Kernel build for WINSTON completed on Sun Jun 10 13:30:25 PDT 2001 >>>> > > So both the world and the kernel build just fine if you don't try to > do things your own way right now and if you have a stock -stable > source tree without local modifications. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > I have no non-standard build flags; I have no modifications. I just cvsup'ed yet again, and now it errors at pam instead of perl. It seems to be breaking earlier and ealier. cvsup command used: cvsup -P - stable-supfile (the file provided for in the manual) make.conf: CFLAGS=-O -pipe COPTFLAGS=-O -pipe NOPROFILE=true build commands used: script /root/mw.out && cd /usr/src && make -j4 buildworld && exit script /root/mw.out && cd /usr/src && make buildworld && exit current error: ===> lib/libpam/libpam rm -f a.out pam_account.o pam_auth.o pam_data.o pam_delay.o pam_dispatch.o pam_end.o pam_env.o pam_handlers.o pam_item.o pam_log.o pam_misc.o pam_password.o pam_second.o pam_session.o pam_start.o pam_strerror.o help_env.o misc_conv.o xstrdup.o pam_get_pass.o pam_prompt.o pam_std_option.o pam_static_modules.o pam_account.o.tmp pam_auth.o.tmp pam_data.o.tmp pam_delay.o.tmp pam_dispatch.o.tmp pam_end.o.tmp pam_env.o.tmp pam_handlers.o.tmp pam_item.o.tmp pam_log.o.tmp pam_misc.o.tmp pam_password.o.tmp pam_second.o.tmp pam_session.o.tmp pam_start.o.tmp pam_strerror.o.tmp help_env.o.tmp misc_conv.o.tmp xstrdup.o.tmp pam_get_pass.o.tmp pam_prompt.o.tmp pam_std_option.o.tmp security pam_static.o setdef0.o _pam_static_modules.o setdef1.o setdef0.c setdef1.c setdefs.h pam_authenticate.3.gz pam_chauthtok.3.gz pam_fail_delay.3.gz pam_open_session.3.gz pam_setcred.3.gz pam_start.3.gz pam_strerror.3.gz pam.8.gz pam_authenticate.3.cat.gz pam_chauthtok.3.cat.gz pam_fail_delay.3.cat.gz pam_open_session.3.cat.gz pam_setcred.3.cat.gz pam_start.3.cat.gz pam_strerror.3.cat.gz pam.8.cat.gz rm: security: is a directory *** Error code 1 Stop in /usr/src/lib/libpam/libpam. *** Error code 1 Stop in /usr/src/lib/libpam/libpam. *** Error code 1 Stop in /usr/src/lib/libpam. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message