Daniel Robbins wrote:
> I've made a transition to the most recent set of GNU development tools for
> my own (Linux) distro, and all I can say is that it may take a bit of fiddling to
> find the "best" binutils that will work with gcc 2.95.2. But, it's definitely
> worth the work, since gcc's new x86 backend is just incredible, and produces
> wonderfully fast code. In the end, I simply snagged the most recent version
> of binutils from the URL above, and it seemed to work ok. You *can expect*
> problems and challenges integrating 2.95.2 into FreeBSD -- it's like a whole
> new compiler. And it *will* cause new compile errors that were not flagged
> before. That's just the nature of the new gcc. In the end, it will be worth
> it.
Why don't we do it? Let's find out from the maintainer of binutils
which version he recommends, and then integrate it into the next
version of -current. We can find the bugs and fix them on our own.
Personally, I'd like to find out what's taking so long.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
