On 05/04/2010 16:10, Nathan Froyd wrote:
>
> Have you tried configuring with --enable-languages=c? Doing so should
> ensure that libstdc++ is not configured for your target.
I've found it possible to build a c++ compiler with no libstdc (as per other
post). Bare-metal COFF target, no libc; I
On 05/04/2010 15:59, Kofi Doku Atuah wrote:
> Hello, and a pleasant good day to everyone. With no further ado:
:) Actually, that's a fair amount of ado simply to say:
> There's no *need* for a libstdc++ on a vanilla or 'bare metal' build.
This is my idea of "no further ado":
/path/to/gcc/c
On Mon, Apr 05, 2010 at 10:29:07AM -0430, Kofi Doku Atuah wrote:
> The process of building a simply, plain vanilla cross compiler for
> arch-fmt-no_os is really probably overdone. To build, for example, a
> GCC cross compiler for an i586-elf target, the build process requires
> you to have a libc f
