Port build loops on 7.0 [SOLVED]

[Dave Smith]

On Thu, 27 Mar 2008 09:17:32 +0000, Dave Smith wrote:

> Hi
> 
> when trying to build any ports on 7.0-release I get failures at the
> configure stage.
> 
> The configure process runs through until it gets to the end. Here is a
> sample for portmanager:
> 
> ===>  Configuring for portmanager-0.4.1_9 checking for a BSD-compatible
> install... /usr/bin/install -c -o root -g wheel
> checking whether build environment is sane... yes checking for gawk...
> no
> checking for mawk... no
> checking for nawk... nawk
> checking whether make sets $(MAKE)... yes checking build system type...
> sparc64-portbld-freebsd7.0 checking host system type...
> sparc64-portbld-freebsd7.0 checking for style of include used by make...
> GNU checking for gcc... cc
> checking for C compiler default output file name... a.out checking
> whether the C compiler works... yes checking whether we are cross
> compiling... no checking for suffix of executables... checking for
> suffix of object files... o checking whether we are using the GNU C
> compiler... yes checking whether cc accepts -g... yes checking for cc
> option to accept ANSI C... none needed checking dependency style of
> cc... gcc3 checking for a sed that does not truncate output...
> /usr/bin/sed checking for egrep... grep -E
> checking for ld used by cc... /usr/bin/ld checking if the linker
> (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload
> object files... -r checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all checking how
> to run the C preprocessor... cc -E checking for ANSI C header files...
> yes checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
...
> checking whether stat accepts an empty string... no checking for
> strchr... yes
> checking for strstr... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating libMG/Makefile config.status: creating
> libMG/src/Makefile config.status: creating libMGPM/Makefile
> config.status: creating libMGPM/src/Makefile config.status: creating
> portmanager/Makefile config.status: creating config.h
> config.status: executing default-1 commands configure: creating
> ./config.status
> config.status: creating Makefile
> config.status: creating libMG/Makefile config.status: creating
> libMG/src/Makefile config.status: creating libMGPM/Makefile
> config.status: creating libMGPM/src/Makefile config.status: creating
> portmanager/Makefile config.status: creating externVars.h
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing default-1 commands ===>  Building for
> portmanager-0.4.1_9 /bin/sh ./config.status --recheck
> running /bin/sh ./configure  --with-prefix=/usr/local --with-bindir=/bin
> --with-etcdir=/etc --with-pkgdbdir=/var/db/pkg
> --with-portsdir=/usr/ports --with-sharedir=/share/portmanager
> --with-tempdir=/tmp --prefix=/usr/ local --mandir=/usr/local/man
> --infodir=/usr/local/info/ --build=sparc64- portbld-freebsd7.0 CC=cc
> CFLAGS=-O2 -fno-strict-aliasing -pipe  CXXFLAGS=- O2
> -fno-strict-aliasing -pipe CXX=c++ build_alias=sparc64-portbld-
> freebsd7.0  --no-create --no-recursion checking for a BSD-compatible
> install... /usr/bin/install -c
> 
> 
> 
> As you can see the whole process is starting again. I have been using
> FreeBSD for years and I have never seen this. Having said that, this is
> my first play with 7.0 on Sparc.
> 
> Any help would be greatly appreciated.
> 
> Dave S
> 
> _______________________________________________
> freebsd-sparc64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 To
> unsubscribe, send any mail to "freebsd-sparc64-unsubscribe at freebsd.org"

Replying to my on message with the solution:

The clock on the machine was set 75 years in the future! Set the time 
using our NTP server, all worked fine.

Woops....