public inbox for gentoo-musl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: gentoo-musl <gentoo-musl@lists.gentoo.org>, llvm@gentoo.org
Subject: [gentoo-musl] Self-hosting Clang-based (libc++, musl libc) stage4
Date: Sun, 7 May 2017 08:05:33 +0200	[thread overview]
Message-ID: <20170507060532.GA2655@Krypton.localdomain> (raw)

Dear all,

I have made a self-hosting clang-based stage4 that some might want to
play with. LLVM/clang (4) are bootstrapped against libc++ and gcc is
uninstalled (custom crt{begin,end} from ELLCC, see /usr/local/hack/crt)

An update from the last version announced on the gentoo-musl list 1st of
May is that I now have LLVM-patched linux (4.11) sources in there (already
installed and symlinked to /usr/src/linux, default config binaries
installed to /boot)


The stage4 can be downloaded here:
https://mega.nz/#!VrQASApL!F4v7SmS5wkJKBzBigsqptipJYuT94yT3-ObjOWEEG3Y

sha256sum:
6d7d68478ead5c80fa34553cf3fbff2af2916364d1aef0cbdae7147c8761aa81

stuff that might interest the LLVM project:

- the whole system is based on libedit
- some LLVMlinux patch sources:

full patch set from llvmlinux project + extras
https://github.com/staalmannen/linux/tree/llvmlinux

minimal patch set
https://github.com/ramosian-glider/clang-kernel-build

the minimal patch set + some fixes against noisy build
https://github.com/staalmannen/linux/tree/llvmlinux-fresh

The linux 4.11 in /usr/local/portage-clang/sys-kernel/llvm-sources
is patched against the minimal patch set. For later kernel versions I
would most likely go for the llvmlinux-fresh set (alternatively, fixes
are upstream in the kernel or in clang-kernel-build).
Important note: I did not write any of those patches, just applied them.

Some thoughts:
- it would be really cool if an "official" custom crt package for
  llvm/clang could be in portage
- it would be really cool if llvm-sources could be officially supported
  since this would mean that clang actually can be (optionally) used as
  a system compiler with no reliance on gcc (a few years later than freebsd).






             reply	other threads:[~2017-05-07  6:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07  6:05 Jens Staal [this message]
     [not found] ` <1494142061.1410.3.camel@gentoo.org>
2017-05-07  9:19   ` [gentoo-musl] Re: Self-hosting Clang-based (libc++, musl libc) stage4 Jens Staal
     [not found]     ` <67270d8b-0bda-d6b0-a97f-722ae449e424@gentoo.org>
2017-05-07 18:29       ` Jens Staal
2017-05-08 11:00       ` Jens Staal
     [not found]     ` <1494669664.8406.1.camel@gentoo.org>
2017-05-13 11:24       ` Jens Staal

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=20170507060532.GA2655@Krypton.localdomain \
    --to=staal1978@gmail.com \
    --cc=gentoo-musl@lists.gentoo.org \
    --cc=llvm@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