linux-kernel - Re: [PATCH] Make m68k cross compile like every other architecture.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0710120211130.4083@loopy.telegraphics.com.au>
Date:	Fri, 12 Oct 2007 02:26:07 +1000 (EST)
From:	Finn Thain <fthain@...egraphics.com.au>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
cc:	Rob Landley <rob@...dley.net>, Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>
Subject: Re: [PATCH] Make m68k cross compile like every other architecture.

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/