[RTEMS Project] #2377: rtems_waf: Tools without a version are not supported

[RTEMS trac]

#2377: rtems_waf: Tools without a version are not supported
-----------------------------+-------------------
 Reporter:  sebastian.huber  |       Owner:
     Type:  defect           |      Status:  new
 Priority:  normal           |   Milestone:  4.11
Component:  tools            |     Version:  4.11
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+-------------------
Changes (by sebastian.huber):

 * cc: daniel (added)


Comment:

 Replying to [comment:5 chrisj]:
 > Replying to [comment:4 sebastian.huber]:
 > > The RCC archives use a version:
 > >
 > > http://gaisler.com/anonftp/rcc/bin/linux/
 > >
 >
 > These look like old tools. My understanding is un-versioned tools would
 not be be part of any 4.11 version and the last un-versioned tools by
 Gaisler was 4.10.

 The preliminary RCC for 4.11 has still un-versioned tools:

 http://www.gaisler.com/anonftp/rcc/smp/nov2014/sparc-
 rtems-4.11-gcc-4.9.2-1.2.99.1-linux.tar.bz2

 >
 > > However, the tools use all a sparc-rtems- prefix without a version.
 >
 > We should not and really cannot support un-versioned tools in the
 project. I will discourage any efforts to make it supported.

 Ok, then Gaisler should adjust their RCC structure.

 >
 > > I found it convenient to use this scheme for the RTEMS master as well.
 You can build the tools with an arbitrary string after the target-rtems,
 e.g. sparc-rtemsfoobarblug99.abc is also allowed.
 >
 > Did you try the --rtems-version option, ie --rtems-
 version=foobarblug99.abc ?
 >
 > I support any version label and encourage custom ones for a specific
 user build. It is just no versioning I wish to discourage.
 >
 > Note, the waf based rtems-config support has a bug with a hardcoded
 version.

 No, I didn't build the tools with such a version label.

--
Ticket URL: <http://devel.rtems.org/ticket/2377#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project