This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC 4.6 not building crti.o and crtn.o in cross-compiler


On Fri, May 6, 2011 at 9:37 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> For most targets crti.o and crtn.o are built by the C library, not by
>> gcc. ?sparc-elf was one of the unusual exceptions. ?Support for building
>> them as part of gcc was removed by this change:
>> http://gcc.gnu.org/ml/gcc-patches/2010-12/msg01334.html , presumably
>> as part of "removes some left-overs".
>
> Right, sparc-elf and sparc-rtems were hijacking sol2-ci.asm and sol2-cn.asm,
> which are supposed to be Solaris-specific. ?Now the RTEMS folks complained
> about the removal and I accepted to backpedal for sparc-rtems:
> ?http://gcc.gnu.org/ml/gcc-patches/2011-01/msg00530.html
> They never applied the patch, though.
>
> The funny thing is that neither sparc64-elf nor sparc64-rtems build them.
> But they are very likely little used targets.
>
> I guess the best solution to clean up the mess at this point is to backpedal
> entirely and build them (again) for sparc*-elf and sparc*-rtems. ?I'll do the
> change for the upcoming 4.6.1 release.

Thanks guys.  Funnily, the reason for moving up to 4.6 was to get the Leon-
specific support.  I'm also planning on doing some experimentation with RTEMS,
so these patches and discussions are relevant to that as well.

I'm guessing this issue might also be relevant for the upcoming 4.7 release.

Someone's also asked me to help with tools for an embedded Arm project, and
a quick test gives me crti.o & crtn.o in both 4.5.2 and 4.6.0 builds.
Seems like
there isn't a consistent approach to which "extra_parts" get build for
the various
selectable platforms...

I'm quite new to GCC building, so don't want to be adding to the workload by
getting deprecated stuff restored.  If it makes more sense to generate
these files
from libc, and that's where you want to head for future releases, I'm
quite happy to
go that way.

Cheers,

David P.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]