[RTEMS Project] #3944: qoriq_e500 BSP bset fails
RTEMS trac
trac at rtems.org
Tue Apr 28 05:13:43 UTC 2020
#3944: qoriq_e500 BSP bset fails
---------------------------+------------------------------
Reporter: Joel Sherrill | Owner: Sebastian Huber
Type: defect | Status: assigned
Priority: normal | Milestone: 5.1
Component: bsps | Version: 5
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
---------------------------+------------------------------
Comment (by Chris Johns):
Replying to [comment:1 Sebastian Huber]:
> The build picks up the installed compiler and not the new one of the
build set. I think this is a known issue. The compiler is not in my $PATH.
It was picked up by the default prefix. I will try it again with an empty
prefix.
I am not sure how the `PATH` is being set. The prepend path is set here
...
https://git.rtems.org/rtems-source-builder/tree/source-
builder/sb/setbuilder.py#n422
... and this is the staging area. The build module does not play with the
path and the defaults handles the prepend and postpend and extras ...
https://git.rtems.org/rtems-source-builder/tree/source-
builder/defaults.mc#n267
I am confused. Maybe using `--trace` and inspecting the variables would
highlight the issue.
Is there something in gcc causing the prefix to used?
--
Ticket URL: <http://devel.rtems.org/ticket/3944#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list