From: "C Bergström" <cbergstrom@pathscale.com>
To: "Anthony G. Basile" <gentoo-dev@lists.gentoo.org>
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: LLVM
Date: Thu, 18 Aug 2016 21:56:22 +0800 [thread overview]
Message-ID: <CAOnawYoeTLrgeajVorH0KjOknML51WtDHLKyciOLT7Ba+4OYig@mail.gmail.com> (raw)
In-Reply-To: <CADopNUe-pjJjKRpTk+j01smA0BGOz1EQxTxG6cS1V524-i2qGw@mail.gmail.com>
@mgorny may be able to help with some of this and has quite a bit of
experience building clang/llvm. Where I work we use a "wrapper" that
helps coordinate a lot of the moving pieces.
https://github.com/pathscale/llvm-suite/
This may not be the perfect "gentoo" way to handle it, but the
approach would produce a clean and correct compiler. With llvm
dependencies getting more and more complicated, I'm not sure if it
would be possible to have both a gnu-free and also perfect
1-project-source-repo:1-ebuild ratio.
I'm sure there's llvm/clang ebuilds already and curious what others think..
On Thu, Aug 18, 2016 at 9:48 PM, Ian Bloss <ianlinkcd@gmail.com> wrote:
> Woot! Don't tell Stallman lol.
>
>
> On Tue, Aug 16, 2016, 09:22 Michał Górny <mgorny@gentoo.org> wrote:
>>
>> Hello, everyone.
>>
>> I have the pleasure of announcing that after the long period of split
>> maintenance, we are forming an united LLVM project [1] to maintain all
>> of LLVM packages in Gentoo and work on establishing improved support for
>> a healthy, gcc-free ecosystem.
>>
>> [1]:https://wiki.gentoo.org/wiki/Project:LLVM
>>
>> --
>> Best regards,
>> Michał Górny
>> <http://dev.gentoo.org/~mgorny/>
next prev parent reply other threads:[~2016-08-18 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:22 [gentoo-dev] New project: LLVM Michał Górny
2016-08-18 13:48 ` Ian Bloss
2016-08-18 13:56 ` C Bergström [this message]
2016-08-18 23:33 ` Lei Zhang
2016-08-19 2:07 ` cbergstrom
2016-08-19 2:40 ` Lei Zhang
2016-08-19 3:11 ` C Bergström
2016-08-19 15:01 ` Luca Barbato
2016-08-19 15:15 ` C Bergström
2016-08-19 17:38 ` Luca Barbato
2016-08-19 18:02 ` james
2016-08-19 18:20 ` C Bergström
2016-08-19 20:52 ` james
2016-08-19 21:05 ` C Bergström
2016-08-19 21:41 ` james
2016-08-20 5:45 ` C Bergström
2016-08-19 16:54 ` Lei Zhang
2016-08-19 17:13 ` C Bergström
2016-08-19 17:34 ` Luca Barbato
2016-08-21 1:10 ` Lei Zhang
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=CAOnawYoeTLrgeajVorH0KjOknML51WtDHLKyciOLT7Ba+4OYig@mail.gmail.com \
--to=cbergstrom@pathscale.com \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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