mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sven Peter" <sven@svenpeter.dev>
To: "Nick Desaulniers" <nick.desaulniers@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Hector Martin" <marcan@marcan.st>
Cc: "Nick Desaulniers" <ndesaulniers@google.com>,
	clang-built-linux <llvm@lists.linux.dev>,
	"Linux Kbuild mailing list" <linux-kbuild@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: Any interest in building the Linux kernel from a MacOS host?
Date: Mon, 26 Sep 2022 10:09:41 +0200	[thread overview]
Message-ID: <ba821ade-1573-4c35-8fbb-285283817147@app.fastmail.com> (raw)
In-Reply-To: <CAH7mPvj64Scp6_Nbaj8KOfkoV5f7_N5L=Tv5Z9zGyn5SS+gsUw@mail.gmail.com>

On Mon, Sep 26, 2022, at 09:51, Nick Desaulniers wrote:
> Not sure if this is potentially interesting to anyone but I was able
> to get the kernel building from MacOS my M2 Air with a small amount of
> effort (read: duct tape and bailing wire).  

I originally tried exactly that last year but I guess my duct tape wasn't
quite strong enough ;)

> If this might seem helpful
> to anyone's workflow, I wouldn't mind pursuing this (with some
> cleanup, sending a more formal patch set).  Maybe this helps us
> bootstrap or get Linux up and running sooner on these machines?

I've been either using a Linux VM or just a bare metal system running
on these machine for quite a while now to build kernels. This would've
been useful when I originally started though and VMs weren't working very
well yet so maybe it's still worth pursuing.


>
> Take a look at the commit message linked below for the trials & 
> tribulations:
> https://github.com/ClangBuiltLinux/linux/commit/f06333e29addbc3d714adb340355f471c1dfe95a
>
> Thanks,
> ~Nick Desaulniers


Best,


Sven

  reply	other threads:[~2022-09-26  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  7:51 Nick Desaulniers
2022-09-26  8:09 ` Sven Peter [this message]
2022-09-26  9:06   ` Martin Povišer
2022-09-26 11:16     ` Hector Martin
2022-09-26 11:35     ` Eric Curtin
2022-09-26  8:56 ` Masahiro Yamada

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=ba821ade-1573-4c35-8fbb-285283817147@app.fastmail.com \
    --to=sven@svenpeter.dev \
    --cc=asahi@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=marcan@marcan.st \
    --cc=masahiroy@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nick.desaulniers@gmail.com \
    --cc=torvalds@linux-foundation.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®