#320 closed defect (fixed)
start.o for build-VARIANTS
Reported by: | Ralf Corsepius | Owned by: | Joel Sherrill |
---|---|---|---|
Priority: | normal | Milestone: | 2 |
Component: | bsps | Version: | unknown |
Severity: | major | Keywords: | |
Cc: | bugs@… | Blocked By: | |
Blocking: |
Description
Startup file handling for build variants is inconsistent:
a) the OPTIMIZE-variant uses start.o
b) the DEBUG-variant uses start_g.o
c) the PROFILE-variant uses start.o
[cf. <c/src/lib/libbsp/<cpu>/<bsp>/bsp_specs]
Building RTEMS however builds
a) start.o for OPTIMIZE.
b) start_g.o for DEBUG
c) start_p.o for PROFILE
=> If building the PROFILE-variant alone (without having build OPTIMIZE, beforehand), linking any application fails, because start.o is not available.
Additional question: Is using VARIANTS on startup-code useful at all? I am not sure, but I am having doubts on this.
Release:
RTEMS-CVS
Change History (2)
comment:1 Changed on 12/02/02 at 14:09:05 by Joel Sherrill
Status: | assigned → waiting |
---|
comment:2 Changed on 01/03/03 at 16:09:43 by Joel Sherrill
Status: | waiting → closed |
---|
Note: See
TracTickets for help on using
tickets.
State-Changed-From-To: feedback->closed
State-Changed-Why: This should now be fixed for DEBUG variants and we are