problems compiling latest -current

M. Warner Losh imp at bsdimp.com
Fri Jul 30 07:51:08 PDT 2004


In message: <410A3FB2.908 at freebsd.org>
            Peter Grehan <grehan at freebsd.org> writes:
:  >	Since noone is complaining, then it might be that I cross >compile - 
: compiling
:  >under stable (4.10) for current, this worked fine till now.
: 
:   I get this too, using 5.1-RELEASE. The fix was:
: 
: RCS file: /home/ncvs/src/gnu/usr.bin/cc/cc_int/Makefile,v
: retrieving revision 1.41
: diff -u -r1.41 Makefile
: --- Makefile    28 Jul 2004 05:27:20 -0000      1.41
: +++ Makefile    29 Jul 2004 10:24:33 -0000
: @@ -9,7 +9,7 @@
: 
:   # Files from libiberty.
:   SRCS=  choose-temp.c concat.c cp-demangle.c cp-demint.c cplus-dem.c \
: -        dyn-string.c errors.c fibheap.c getpwd.c getruntime.c hashtab.c \
: +        dyn-string.c fibheap.c getpwd.c getruntime.c hashtab.c \
:          hex.c lbasename.c make-temp-file.c md5.c obstack.c partition.c \
:          pexecute.c physmem.c splay-tree.c xexit.c xmalloc.c xmemdup.c \
:          xstrdup.c xstrerror.c xexit.c
: 
:   The routines in errors.c are contained in diagnostic.c, so I couldn't
: really see why they were needed, and I guess binutils < 2.15 isn't
: happy with having duplicate routines in an archive.

This also is a happiness making patch for me.  I'm nearly all the way
through a buildworld right now on 4.10 PRERELEASE.  There are new
warnings that weren't there before, but they are also there on my
current box...

Maybe now is the right time to take the plunge and upgrade my 'stable'
system to current...  Now that I'm no longer married and required to
have a stable mail server at all times for domestic harmony, I can
take more risks...

Warner


More information about the freebsd-current mailing list