From: Sam Ravnborg <sam@ravnborg.org>
To: Benno <benjl@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Building on platforms other than Linux
Date: Wed, 11 Aug 2004 20:54:53 +0200 [thread overview]
Message-ID: <20040811185453.GA7217@mars.ravnborg.org> (raw)
In-Reply-To: <20040811091349.GX862@cse.unsw.edu.au>
On Wed, Aug 11, 2004 at 07:13:49PM +1000, Benno wrote:
> Hi,
>
> I was wondering if there were any, in priniciple, objections
> to making the Linux kernel buildable on different Unix-like
> platforms?
The userbase for building kernels are only increasing and there
continue to be more focus from the embedded people.
Having experince in this field first-hand tells me that a kernel
that can be build on several paltforms are a good thing.
For kbuild you will at some point start to see patches so at least
the build system does not restrict us to Linux alone.
People on this list usually reply: "shift development to a Linux
based platform". This is for many developers a nice dream,
but they are restricted by coporate rules etc.
So please feed patches to this list with your findings.
>
> I am currently compiling on MacOSX and this, for the most part was
> fairly straightforward and simple. The biggest gotcha I had was
> that libkconfig is compiled as a shared library, and unfortunately shared
> libraries are done quite different on different systems. Specifically MacOSX
> doesn't support gcc -shared.
Please submit a patch for this and make sure to include Roman Zippel, he
is the maintainer of kconfig.
[I recall RedHat already disables the shared library??]
Sam
next prev parent reply other threads:[~2004-08-11 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 9:13 Benno
2004-08-11 18:54 ` Sam Ravnborg [this message]
2004-08-11 19:03 ` Arjan van de Ven
2004-08-11 19:19 ` Sam Ravnborg
2004-08-12 0:22 ` [PATCH] " Benno
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=20040811185453.GA7217@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=benjl@cse.unsw.edu.au \
--cc=linux-kernel@vger.kernel.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®