From: Esben Haabendal <esben.haabendal@dev.prevas.dk>
To: Mike Frysinger <vapier@gentoo.org>
Cc: <crossgcc@sourceware.org>, "Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [PATCH] kernel/linux: change arch tuple to use -uclinux for uclinux toolchains
Date: Wed, 26 Sep 2012 04:47:00 -0000 [thread overview]
Message-ID: <878vbx9yr8.fsf@arh128.prevas.dk> (raw)
In-Reply-To: <201209252233.18809.vapier@gentoo.org> (Mike Frysinger's message of "Tue, 25 Sep 2012 22:33:17 -0400")
Mike Frysinger <vapier@gentoo.org> writes:
>> I will rework the patch to set CT_TARGET_KERNEL depending on both
>> CT_ARCH_USE_MMU and CT_ARCH. So "linux" for bfin and "uclinux" for
>> m68k.
>
> hard coding one way or the other is wrong. bfin-uclinux is valid, as is m68k-
> uclinux and arm-uclinux and mips-uclinux and many other targets.
Well, the fact is that either GCC has to be changed to handle
linux/uclinux in the arch tuple to your preferences, or ct-ng has to be
able to handle it. The current situations makes ct-ng unable to build
linux-uclibc for m68k cpus without mmu.
So what do you propose?
/Esben
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-09-26 4:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 12:30 Esben Haabendal
2012-09-25 16:42 ` Yann E. MORIN
2012-09-25 16:46 ` Mike Frysinger
2012-09-25 18:18 ` Esben Haabendal
2012-09-25 20:38 ` Mike Frysinger
2012-09-25 21:18 ` Esben Haabendal
2012-09-26 2:33 ` Mike Frysinger
2012-09-26 4:47 ` Esben Haabendal [this message]
2012-09-26 5:26 ` Mike Frysinger
2012-09-26 6:38 ` Esben Haabendal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vbx9yr8.fsf@arh128.prevas.dk \
--to=esben.haabendal@dev.prevas.dk \
--cc=crossgcc@sourceware.org \
--cc=vapier@gentoo.org \
--cc=yann.morin.1998@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).