[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:7 Sebastian Huber]:
 > Maybe the RSB should warn that there are already tools installed in the
 prefix and offer an option to remove them.

 A prefix can be a shared resource used by a number of packages so what are
 you asking is removed?

 The RSB has no concept or knowledge of what the package actually installs
 so how would it be able to remove these specific parts. This is what
 distro packaging systems do.

 > For example building the latest or1k tool chain failed since I had the
 previous tools installed in $prefix. During GCC build the Binutils of
 $prefix are used and not the ones which are newly built.

 All I can suggest is you wrap the RSB in the distro system of your choice
 and deploy the tools that way if you want to track specific files in
 packages.

 I think the real issue is not this but the build. The RSB build of the
 RTEMS tools should be looking to use the binutils just built however for
 some reason gcc must be looking in the `$prefix` before the `$PATH` and
 when the `$prefix` is empty it uses the binutils in the `$PATH`, after all
 this is what happens when there are no tools installed. Does an option
 exist in gcc to control this order?

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