#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 Dec 2, 2002 at 2:09:05 PM by Joel Sherrill

Status: assignedwaiting

comment:2 Changed on Jan 3, 2003 at 4:09:43 PM by Joel Sherrill

Status: waitingclosed

State-Changed-From-To: feedback->closed
State-Changed-Why: This should now be fixed for DEBUG variants and we are

ignoring the PROFILE variant because it is not functional.

Note: See TracTickets for help on using tickets.