This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [m68k] Add m68k-uclinux-uclibc target
- From: Bernardo Innocenti <bernie at develer dot com>
- To: Ben Elliston <bje at wasabisystems dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, libstdc++ at gcc dot gnu dot org, config-patches at gnu dot org, Richard Henderson <rth at redhat dot com>, hch at infradead dot org, schwab at suse dot de, hp at bitrange dot com
- Date: Fri, 03 Oct 2003 09:26:41 +0200
- Subject: Re: [m68k] Add m68k-uclinux-uclibc target
- Organization: Develer S.r.l.
- References: <3F6F12EF.1030007@develer.com> <87smma963w.fsf@wasabisystems.com>
Ben Elliston wrote:
Bernardo Innocenti <bernie@develer.com> writes:
2003-09-22 Bernardo Innocenti <bernie@develer.com>
* config.sub (m68k-unknown-linux-uclibc, m68k-unknown-uclinux-uclibc):
New targets.
Why is it necessary for there to be two names for the same target?
A few minutes ago I've sent an updated patch to config-patches@gnu.org,
just before reading your comment.
All possible kernel/libc combinations should be supported
in config.sub:
linux-gnu (the real GNU/Linux)
linux-uclibc (Linux using uClibc)
uclinux-uclibc (the uClinux kernel with uClibc)
uclinux-glibc (the uClinux kernel with the GNU libc)
The latter is not really possible on m68k, but I think the
ARM and perhaps other platforms can do that.
I've not bothered adding those targets to config.guess
because, AFAIK, nobody is doing self-hosted uClinux
development, even though it would theorically be
possible by designing a board with plenty of memory.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html