#255 closed defect (fixed)
c4x-rtems-gcc crt0.o stupidity
Reported by: | Ralf Corsepius | Owned by: | Joel Sherrill |
---|---|---|---|
Priority: | normal | Milestone: | 2 |
Component: | tool | Version: | unknown |
Severity: | major | Keywords: | |
Cc: | bugs@…, ralf.corsepius@… | Blocked By: | |
Blocking: |
Description
From the c4x-rtems-newlib patch:
you'll have to copy the object file crt0.o from /usr/local/c4x/lib
+to /usr/local/lib/gcc-lib/c4x/gcc-xxx/ using the naming convention for
+c4x-gcc (i.e. c4x small mem model, memparm requires crt0_4sm.o; c4x
+small mem model, regparm requires crt0_4sr.o)
I.e c4x-rtems-gcc requires these crt0_*.o to be present:
/opt/c4x-rtems/c4x-rtems/lib/c3x/crt0_3br.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/mem/crt0_3bm.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/mem/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/small/crt0_3sr.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/small/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/small/mem/crt0_3sm.o
/opt/c4x-rtems/c4x-rtems/lib/c3x/small/mem/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/crt0_4br.o
/opt/c4x-rtems/c4x-rtems/lib/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/mem/crt0_4bm.o
/opt/c4x-rtems/c4x-rtems/lib/mem/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/small/crt0_4sr.o
/opt/c4x-rtems/c4x-rtems/lib/small/crt0.o
/opt/c4x-rtems/c4x-rtems/lib/small/mem/crt0_4sm.o
/opt/c4x-rtems/c4x-rtems/lib/small/mem/crt0.o
With all ct0_* being identical to neighboring crt0.o.
At present time, all crt0.o are present, but most crt0_*.o's are missing.
Without the crt0_*, building RTEMS-CVS multilib'ed fails due to linker errors. Having them installed (by adding hard-links), the build succeeds perfectly.
Release:
RTEMS-CVS
Environment:
c4x-rtems-gcc-2.95.2-newlib-1.8.2
c4x-rtems-binutils-2.7.x
Attachments (2)
Change History (2)
comment:1 Changed on 06/17/03 at 12:12:49 by Joel Sherrill
Status: | assigned → closed |
---|
Changed on 12/03/06 at 13:31:13 by Ralf Corsepius
Attachment: | c4x-rtems-gcc-newlib-gcc2.95.2newlib1.8.2-3.nosrc_v1.rpm added |
---|
c4x-rtems-gcc-newlib-gcc2.95.2newlib1.8.2-3.nosrc.rpm
State-Changed-From-To: analyzed->closed
State-Changed-Why: This appears to be OK in gcc 3.3 with the newer toolset.