On Fri, Oct 11, 2002 at 02:42:34AM -0700, David O'Brien wrote: > On Fri, Oct 11, 2002 at 01:04:23AM -0700, David O'Brien wrote: > > I've ended up hosing world with the Binutils upgrade. > > I think world is OK now.
Looks as if something is (still?) broken: >>> stage 4: building everything.. ... ===> gnu/usr.bin/binutils/gdb ... cc -O -pipe -mcpu=pentiumpro -D_GNU_SOURCE -I. -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/include -Dprint_insn_i386=print_insn_i386_att -DDEFAULT_BFD_VEC=bfd_elf32_i386_vec -DGDB_XM_FILE -Dprint_insn_i386=print_insn_i386_att -DDEFAULT_BFD_VEC=bfd_elf32_i386_vec -DGDB_XM_FILE -DDEFAULT_BFD_ARCH=bfd_i386_arch -I/usr/src/gnu/usr.bin/binutils/gdb/i386 -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/binutils/bfd -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb -I/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/config -I/usr/src/gnu/usr.bin/binutils/gdb -I/usr/obj/usr/src/i386/usr/include/readline -static -o gdb init.o annotate.o ax-general.o ax-gdb.o bcache.o blockframe.o breakpoint.o buildsym.o c-exp.o c-lang.o c-typeprint.o c-valprint.o ch-exp.o ch-lang.o ch-typeprint.o ch-valprint.o coffread.o complaints.o copying.o corefile.o corelow.o cp-valprint.o dcache.o dbxread.o demangle.o dwarfread.o dwarf2read.o elfread.o environ.o eval.o exec.o expprint.o f-exp.o f-lang.of-typeprint.o f-valprint.o findvar.o fork-child.o gdbarch.o gdbtypes.o infcmd.o inflow.o infptrace.o infrun.o inftarg.o language.o jv-exp.o jv-lang.o jv-valprint.o jv-typeprint.o nlmread.o m2-lang.o m2-exp.o m2-typeprint.o m2-valprint.o main.o maint.o mdebugread.o mem-break.o minsyms.o objfiles.o parse.o printcmd.o remote.o remote-utils.o scm-exp.o scm-lang.o scm-valprint.o solib.o source.o stabsread.o stack.o symfile.o symmisc.o symtab.o target.o thread.o top.o tracepoint.o typeprint.o utils.o valarith.o valops.o valprint.o values.o serial.o ser-unix.o ser-tcp.o arch-utils.o cp-abi.o completer.o doublest.o event-loop.o event-top.o frame.o gdb-events.o inf-loop.o linespec.o memattr.o regcache.o signals.o solib-svr4.o solib-legacy.o ui-file.o ui-out.o wrapper.o cli-out.o cli-cmds.o cli-decode.o cli-script.o cli-setshow.o cli-utils.o freebsd-uthread.o kvm-fbsd.o i386fbsd-nat.o i386bsd-tdep.o i386bsd-nat.o i386-nat.o i386-tdep.o i387-nat.o i387-tdep.o core-regset.o core-aout.o gdbversion.o -lkvm -lm ../libbfd/libbfd.a ../libopcodes/libopcodes.a -lgnuregex ../libiberty/libiberty.a -lreadline -ltermcap arch-utils.o(.data+0x40): undefined reference to `bfd_elf32_i386_vec' *** Error code 1 1 error What next? Thanks, david -- David H. Wolfskill [EMAIL PROTECTED] To paraphrase David Hilbert, there can be no conflicts between the discipline of systems administration and Microsoft, since they have nothing in common. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
