[RTEMS Project] #2540: RSB has problems building into existing directory

[RTEMS trac]

#2540: RSB has problems building into existing directory
----------------------------+----------------------------
 Reporter:  Simon Williams  |       Owner:  Needs Funding
     Type:  defect          |      Status:  assigned
 Priority:  normal          |   Milestone:  Indefinite
Component:  tool/rsb        |     Version:  5
 Severity:  normal          |  Resolution:
 Keywords:                  |  Blocked By:
 Blocking:                  |
----------------------------+----------------------------

Comment (by Chris Johns):

 Replying to [comment:14 Sebastian Huber]:
 > I don't have a solution for this problem.

 I did outline one :)

 > Normally I just delete the prefix before I start the RSB. While testing
 the new or1k tool chain I forgot to do this and got a GCC build error.

 > Even though I know that the RSB build is broken with an existing
 installation in the prefix

 The RSB is not broken, it is doing what it is suppose to do. It is the
 package that is being built that is broken or it is the configuration in
 the RSB that could be improved. Adding shell call-outs using `$()` to
 check the installed version to the gcc tool set scripts would work but we
 need an RSB signature in `as` and `ld`.

 > I didn't think about this and assumed that the new upstream or1k support
 in GCC is broken.

 Then please raise this with gcc or fix it's build so we can control where
 it looks for `as`. It is a weakness with gcc's build we cannot control the
 `as` used.

 Adding an RSB signature to `as` and `ld` is something that should happen.

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