cvs commit: src/gnu/usr.bin/binutils/libbfd/i386 bfd.h
obrien at FreeBSD.org
Sun Apr 18 09:46:54 PDT 2004
On Sun, Apr 18, 2004 at 09:33:01AM -0700, Marcel Moolenaar wrote:
> On Sun, Apr 18, 2004 at 07:24:31PM +0300, Ruslan Ermilov wrote:
> > On Sun, Apr 18, 2004 at 09:09:33AM -0700, David E. O'Brien wrote:
> > > obrien 2004/04/18 09:09:33 PDT
> > >
> > > FreeBSD src repository
> > >
> > > Modified files:
> > > gnu/usr.bin/binutils/libbfd/i386 bfd.h
> > > Log:
> > > Revert rev 1.21 which configured with --enable-64-bit-bfd.
> > > GDB 5.2 can't handle a 64-bit BFD on a 32-bit host.
> > > We can revisit configuring with --enable-64-bit-bfd when we get a modern GDB.
> > >
> > > Revision Changes Path
> > > 1.22 +1 -1 src/gnu/usr.bin/binutils/libbfd/i386/bfd.h
> > >
> > Hmm. :-(
> I have 6.1 pre-release in perforce. I plan to import that alongside
> gdb 5.2 as soon as 6.1 is announced.
What do mean "along side"? Please don't import src/contrib/gdb6. Import
it just as src/contrib/gdb. We've see what a mistake that turns into!
If you don't think gdb6 is readly, have poeple pound on it thru the
> People can pound on it while I
> finish support for kernel debugging.
I have ports/devel/gdb6 working with full kernel debugging already. I
just need to get cvs@ to repo copy a few patches before I can commit it.
> If people can tell my why again we wanted --enable-64-bit-bfd, I can
> work that in (or not).
GDB 6 will work fine with --enable-64-bit-bfd, there is nothing to do.
-- David (obrien at FreeBSD.org)
More information about the cvs-all