On Tue, 2013-11-26 19:50:10 +0000, Joern Rennecke <joern.renne...@embecosm.com> 
wrote:
> On 26 November 2013 17:38, Joel Sherrill <joel.sherr...@oarcorp.com> wrote:
> > as to Joern's question:
> > > Is there something that microblaze-rtems exposes that is not
> > > already covered by other microblaze or rtems targets that are
> > > already included?
> >
> > I believe it was on the microblaze where someone broke the libgcc
> > pattern for rtems by changing the pattern from XXX*-*-* to
> > XXX*-*-elf.
> 
> In order to catch such a problem, we'd have to at least build
> libgcc.  Which requires to have an assembler for the respective
> target first.
> 
> How should this be handled?  Test if an cross-asembler for target
> has been installedon the host?  Or having a separate list of targets
> that are supported by FSF GAS, and a curent gas checkout, and then
> building gas for those targets?

I think it'd possible to eg. first create a linked tree and then build
all-gas all-ld install-gas install-ld all-gcc .  I think that most
targets should be gas-/ld-supported. At least, we'd give that a try
and see where it takes us.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbg...@lug-owl.de              +49-172-7608481
  Signature of:                           Wenn ich wach bin, träume ich.
  the second  :

Attachment: signature.asc
Description: Digital signature

Reply via email to