From owner-freebsd-questions Sun Nov 19 10: 0:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from pi.codefab.com (pi.codefab.com [12.38.161.140]) by hub.freebsd.org (Postfix) with ESMTP id 0F46737B479 for ; Sun, 19 Nov 2000 10:00:07 -0800 (PST) Received: from bjork.codefab.com (root@bjork.codefab.com [12.38.161.11]) by pi.codefab.com (8.11.1/8.11.1) with ESMTP id eAJI06304281; Sun, 19 Nov 2000 13:00:06 -0500 (EST) Received: from bjork.codefab.com (bbum@bjork.codefab.com [12.38.161.11]) by bjork.codefab.com (8.11.1/8.11.1) with ESMTP id eAJI01324930; Sun, 19 Nov 2000 13:00:05 -0500 (EST) Date: Sun, 19 Nov 2000 13:00:01 -0500 (EST) From: Bill Bumgarner To: Mike Meyer Cc: questions@freebsd.org Subject: Re: port problems on clean install In-Reply-To: <14871.44667.137101.473405@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes-- I found how to set the timezone, but there doesn't seem to be anything associated with setting daylight savings time or not. It also seems that the system doesn't include an NTP daemon configuration, by default? It seems that a "make install" on openssh (the only port that built successfully) causes the system to try to run the sshd daemon twice upon boot. I haven't tracked that down yet, but will do so shortly. Enclosed is the output of a failed build. I figured out how to use cvsup to bring down a -STABLE of ports-all and will retry from that. thanks! b.bum On Sun, 19 Nov 2000, Mike Meyer wrote: > Bill Bumgarner types: > > Am I correct in assuming that one should be abel to cd into any of the > > ports in /usr/ports/ after a clean install from a 4.11 cd, type "make > > install" and it should "just work"? > > And it usually does. > > > It definitely isn't on my system. When checking to see whether the > > build environment is sane, it complains that "newly created file is > > older than system file". > > That's not enough information. How about the last bit of the output of > the make command? Or all of it, if it isn't very long. > > > The date/time on the system is correct-- though, looking more closely, > > it appears that it is not taking into account daylight savings time? > > Actually, there doesn't appear to be any option anywhere for either > > setting daylight savings time OR setting the computers clock during > > setup. This *really* should be a part of the setup as it can grossly > > impact a system's usability if the clock is wrong. > > It is part of the system installation process - you're just not forced > to do it. Run /stand/sysinstall, hit the c key, enter, then down arrow > until you get to time zone and hit enter again. That will walk you > through setting the time zone. > > > ===> Extracting for dog-1.5 >> Checksum OK for dog-1.5.tar.gz. ===> dog-1.5 depends on executable: gmake - not found ===> Verifying install for gmake in /usr/ports/devel/gmake ===> Extracting for gmake-3.79.1 >> Checksum OK for make-3.79.1.tar.gz. ===> gmake-3.79.1 depends on shared library: intl.1 - not found ===> Verifying install for intl.1 in /usr/ports/devel/gettext ===> Extracting for gettext-0.10.35 >> Checksum OK for gettext-0.10.35.tar.gz. ===> gettext-0.10.35 depends on executable: libtool - not found ===> Verifying install for libtool in /usr/ports/devel/libtool ===> Configuring for libtool-1.3.4 loading cache ./config.cache checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking whether make sets ${MAKE}... (cached) yes checking for working aclocal... missing checking for working autoconf... missing checking for working automake... missing checking for working autoheader... missing checking for working makeinfo... found checking for gcc... (cached) cc checking whether the C compiler (cc -O -pipe ) works... yes checking whether the C compiler (cc -O -pipe ) is a cross-compiler... no checking whether we are using GNU C... (cached) yes checking whether cc accepts -g... (cached) yes checking for ranlib... (cached) ranlib checking host system type... i386--freebsd4.1.1 checking build system type... i386--freebsd4.1.1 checking for ld used by GCC... (cached) /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... (cached) yes checking for BSD-compatible nm... (cached) /usr/bin/nm -B checking whether ln -s works... (cached) yes checking for mawk... (cached) awk updating cache ./config.cache creating ./config.status creating Makefile creating doc/Makefile creating tests/Makefile configuring in libltdl running /bin/sh ./configure --disable-ltdl-install --prefix=/usr/local i386--freebsd4.1.1 --cache-file=.././config.cache --srcdir=. loading cache .././config.cache checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock configure: error: ./configure failed for libltdl ===> Script "configure" failed: here are the contents of "config.log" This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:569: checking for a BSD compatible install configure:622: checking whether build environment is sane configure:679: checking whether make sets ${MAKE} configure:725: checking for working aclocal configure:738: checking for working autoconf configure:751: checking for working automake configure:764: checking for working autoheader configure:777: checking for working makeinfo configure:818: checking for gcc configure:931: checking whether the C compiler (cc -O -pipe ) works configure:947: cc -o conftest -O -pipe conftest.c 1>&5 configure:973: checking whether the C compiler (cc -O -pipe ) is a cross-compiler configure:978: checking whether we are using GNU C configure:1006: checking whether cc accepts -g configure:1040: checking for ranlib configure:1074: checking host system type configure:1095: checking build system type configure:1124: checking for ld used by GCC configure:1186: checking if the linker (/usr/libexec/elf/ld) is GNU ld configure:1203: checking for BSD-compatible nm configure:1240: checking whether ln -s works configure:1266: checking for mawk (end of "config.log") *** Error code 1 Stop in /usr/ports/devel/libtool. *** Error code 1 Stop in /usr/ports/devel/libtool. *** Error code 1 Stop in /usr/ports/devel/libtool. *** Error code 1 Stop in /usr/ports/devel/libtool. *** Error code 1 Stop in /usr/ports/devel/libtool. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gettext. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/devel/gmake. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. *** Error code 1 Stop in /usr/ports/misc/dog. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message