This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: how close to binutils-2.12 previews


Daniel Jacobowitz wrote:
> 
> On Thu, Feb 14, 2002 at 01:37:33PM -0600, Joel Sherrill wrote:
> > Daniel Jacobowitz wrote:
> > >
> > > On Thu, Feb 14, 2002 at 12:49:01PM -0600, Joel Sherrill wrote:
> > > >
> > > > Hi,
> > > >
> > > > I am just curious how close to a preview tarball and
> > > > release things are right now.
> > >
> > > There's one particular set of Sparc failures and a Windows DLL bug I
> > > would like addressed before release, but I don't know if they will be.
> > > I need to figure out how to roll a prerelease tarball; with a little
> > > bit of luck I can make one early next week and leave two or three weeks
> > > for testing before release.  I don't see much point in holding off
> > > longer.
> >
> > Thanks for the quick reply.  This sounds great to me.  When the
> > first preview is cut, I will try to roll RTEMS RPMs for them and
> > give them a spin.
> >
> > FYI it looks like you can't even build gcc 3.0x for sh-coff/rtems
> > or powerpc-eabi/elf/rtems without newer than 2.11.2 binutils so a
> > 2.12 release will be good.
> 
> I suspect sh-coff is still broken, but powerpc-eabi should be fixed.
> If you have a chance, could you check sh-coff with CVS binutils?

OK.  As soon as I get my gcc 3.0 patches committed -- one thing
at a time. :)

> --
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]