Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180702152805.GA26760@voyager>
Date: Mon, 2 Jul 2018 17:28:05 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Subject: Re: future of compiler wrappers

On Sun, Jul 01, 2018 at 08:11:50PM -0400, Rich Felker wrote:
> It came up again today on #musl that gratuitous use of musl-gcc was
> breaking something (this time, ppc and mips toolchains that were
> already musl-targeting but where the musl-gcc specs broke things), and
> I expressed a sentiment that the compiler wrapper scripts tend to
> reflect badly on musl, and that I'd really rather not keep maintaining
> them but pass maintainership of them off to someone else as a separate
> project for users who still want to use them. Would anyone be
> particularly upset to see them go from the main musl repo/releases,
> and is anyone interested in maintaining them out-of-tree separately
> from musl?
> 
> Rich

By all means, nuke them. Cross-compilers are the way to go in OS
development, as well, and pretty much for the same reason: You want to
insulate your compilate from the host environment. So yes, in the words
of William Shatner: Let them die!

Ciao,
Markus

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.