Date: Sat, 6 Jul 2002 02:19:34 -0500 From: "Kevin Kinsey, DaleCo, S.P." <kdk@daleco.biz> To: "Brian Szymanski" <bks10@cornell.edu>, <freebsd-questions@FreeBSD.ORG> Subject: Re: horked /usr/ports? Message-ID: <012d01c224bd$7af83160$a4e2910c@fbccarthage.com> References: <1090.192.168.1.5.1025939349.squirrel@wuhjuhbuh.2y.net>
next in thread | previous in thread | raw e-mail | index | archive | help
You did a cvsup of the ports tree as well as the
source code, I presume?
KDK
----- Original Message -----
From: "Brian Szymanski" <bks10@cornell.edu>
To: <freebsd-questions@FreeBSD.ORG>
Sent: Saturday, July 06, 2002 2:09 AM
Subject: horked /usr/ports?
> Hi,
>
> I seem to have entered a situation where I can't build anything in
> /usr/ports... I'm not sure what I did to enter this situation. It was a
> 4.6-RELEASE install, which I upgraded to -STABLE, set my processor type to
> k7 in /etc/make.conf, and did a {build, install}{world, kernel} sequence
> on. Most ports compiles seem to die with missing variables from include
> files. Almost every package I tried to build failed in a similar fashion
> to the below (some variable was undeclared) Can it be I screwed up
> /usr/include somehow? Or /etc/make.conf (the build/install sequence went
> fine so I'd be skeptical of this, especially considering the only thing I
> changed was the cputype)... Example included below obligatory thank you.
> Oh, for the record, manually trying the cc line in the proper directory
> without the -march=k6 gets the same results (altho it would be damn weird
> if setting the output binary format screwed up the parsing ;-)
> Thanks,
> Brian
>
> Example: when I try to install pcre:
> su-2.05a# cd /usr/ports/devel/pcre && make clean && make
> ===> Cleaning for pcre-3.7
> ===> Extracting for pcre-3.7
> >> Checksum OK for pcre-3.7.tar.bz2.
> ===> Patching for pcre-3.7
> ===> Applying FreeBSD patches for pcre-3.7
> ===> Configuring for pcre-3.7
> configure: WARNING: you should use --build, --host, --target
> checking for i386-portbld-freebsd4.6-gcc... cc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler... yes
> checking whether cc accepts -g... yes
> checking for a BSD compatible install... /usr/bin/install -c -o root -g
wheel
> checking for i386-portbld-freebsd4.6-ranlib... no
> checking for ranlib... ranlib
> checking how to run the C preprocessor... cc -E
> checking for ANSI C header files... yes
> checking for limits.h... yes
> checking for cc option to accept ANSI C... none needed
> checking for an ANSI C-conforming const... 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 for unistd.h... yes
> checking for size_t... yes
> checking for bcopy... yes
> checking for memmove... yes
> checking for strerror... yes
> checking build system type... i386-portbld-freebsd4.6
> checking host system type... i386-portbld-freebsd4.6
> checking for ld used by GCC... /usr/libexec/elf/ld
> checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes
> checking for /usr/libexec/elf/ld option to reload object files... -r
> checking for BSD-compatible nm... nm
> checking whether ln -s works... yes
> checking how to recognise dependant libraries... pass_all
> checking command to parse nm output... ok
> checking for dlfcn.h... yes
> checking for i386-portbld-freebsd4.6-ranlib... ranlib
> checking for i386-portbld-freebsd4.6-strip... no
> checking for strip... strip
> checking for objdir... .libs
> checking for cc option to produce PIC... -fPIC
> checking if cc PIC flag -fPIC works... yes
> checking if cc static flag -static works... yes
> checking if cc supports -c -o file.o... yes
> checking if cc supports -c -o file.lo...
> checking if cc supports -fno-rtti -fno-exceptions... yes
> checking whether the linker (/usr/libexec/elf/ld) supports shared
> libraries... yeschecking how to hardcode library paths into programs...
immediate
> checking whether stripping libraries is possible... yes
> checking dynamic linker characteristics... freebsd4.6 ld.so
> checking if libtool supports shared libraries... yes
> checking whether -lc should be explicitly linked in... yes
> creating libtool
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating pcre.h
> config.status: creating pcre-config
> config.status: creating RunTest
> config.status: creating config.h
> ===> Building for pcre-3.7
> /bin/sh ./libtool --mode=compile cc -c -O -pipe -march=k6 -I.
./maketables.c
> mkdir .libs
> cc -c -O -pipe -march=k6 -I. ./maketables.c -fPIC -DPIC -o maketables.o
> In file included from ./maketables.c:42:
> internal.h:55: syntax error before `size_t'
> internal.h: In function `pcre_memmove':
> internal.h:58: `dest' undeclared (first use in this function)
> internal.h:58: (Each undeclared identifier is reported only once
> internal.h:58: for each function it appears in.)
> internal.h:58: `n' undeclared (first use in this function)
> internal.h:59: `src' undeclared (first use in this function)
> *** Error code 1
>
> Stop in /usr/ports/devel/pcre/work/pcre-3.7.
> *** Error code 1
>
> Stop in /usr/ports/devel/pcre.
> su-2.05a#
>
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?012d01c224bd$7af83160$a4e2910c>