From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Landley <rob@landley.net>, Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] Make m68k cross compile like every other architecture.
Date: Fri, 12 Oct 2007 02:26:07 +1000 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710120211130.4083@loopy.telegraphics.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0710111707270.3729@anakin>
On Thu, 11 Oct 2007, Geert Uytterhoeven wrote:
> > Reading the patch in that link, recent cross compilers from _where_?
> > Buildroot? Cross-tools? Gentoo embedded? Cross Linux From Scratch?
> > My Firmware Linux project?
> >
> > You assume they all use the same name, yet your patch changes them
> > from one default name to another default name, presumably due to a gcc
> > version change becoming increasingly political about the
> > GNU/Linux/Dammit thing...
>
> Compilers build from the only remaining distribution that supports (sort
> of) m68k: Debian.
Maybe. I use an old Cross LFS build, as well as Debian (does Debian
officially support m68k?), and there also exists an unofficial Gentoo
port.
> If you cross compile for m68k and don't specify a toolchain, you get a
> default one: the one the m68k developers use.
>
> On some other architectures, you always have to specify the toolchain.
> What's wrong with providing a default?
Nothing, except that uniformity across platforms follows the principal of
least suprise. That generally makes life easier downstream.
I personally have created and used m68k cross toolchains as "m68k-linux",
"m68k-linux-gnu" and "m68k-unknown-linux-gnu". AFAIK it's quite arbitrary.
This wasn't an issue before we came to depend on cross compilers. Since we
tend to need them more as compilation becomes more expensive, IMHO we
should follow the practice of the embedded architectures.
-f
>
> Gr{oetje,eeting}s,
>
> Geert
next prev parent reply other threads:[~2007-10-11 16:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 22:22 Rob Landley
2007-10-11 7:25 ` Geert Uytterhoeven
2007-10-11 11:31 ` Rob Landley
2007-10-11 11:39 ` Sam Ravnborg
2007-10-11 12:46 ` Geert Uytterhoeven
2007-10-11 13:27 ` Rob Landley
2007-10-11 13:52 ` Paul Mundt
2007-10-11 15:12 ` Geert Uytterhoeven
2007-10-11 16:26 ` Finn Thain [this message]
2007-10-11 21:14 ` Rob Landley
2007-10-12 6:51 ` Geert Uytterhoeven
2007-10-12 7:54 ` Finn Thain
2007-10-12 8:51 ` Geert Uytterhoeven
2007-10-12 10:21 ` Sam Ravnborg
2007-10-15 20:25 ` Geert Uytterhoeven
2007-10-16 0:31 ` Rob Landley
2007-10-16 4:15 ` Sam Ravnborg
2007-10-18 21:14 ` Sam Ravnborg
2007-10-19 6:38 ` Rob Landley
2007-10-19 15:10 ` Sam Ravnborg
2007-10-11 16:24 ` Sam Ravnborg
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=Pine.LNX.4.64.0710120211130.4083@loopy.telegraphics.com.au \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
/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
all inboxes | Powered by JetHome®