mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benno <benjl@cse.unsw.edu.au>
To: linux-kernel@vger.kernel.org
Subject: Building on platforms other than Linux
Date: Wed, 11 Aug 2004 19:13:49 +1000	[thread overview]
Message-ID: <20040811091349.GX862@cse.unsw.edu.au> (raw)

Hi,

I was wondering if there were any, in priniciple, objections
to making the Linux kernel buildable on different Unix-like 
platforms?

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.

libkconfig.so appears to be the only shared library created in the
build system, and given that it is only about 95K, and that you don't
often run two copies of conf at once, it doesn't seem to buy much.

The only other reason for doing it this way is to provide a plugin
style architecture but this doesn't appear evident. gconf and qconf
appear to manually load libkconfig.so (rather than linking against
it), but in both cases it appears to be the very first thing they
do is explicitly load libconfig.

It would seem that using static libraries would enhance portability,
and produce a simpler build system, however I expect I am missing some
other reasons.

In summary two questions:

1: Is portability of the build system a desirable property?

2: If so, is moving to static libraries a valid way of achieving this?

Thanks,

Benno

             reply	other threads:[~2004-08-11  9:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  9:13 Benno [this message]
2004-08-11 18:54 ` Sam Ravnborg
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=20040811091349.GX862@cse.unsw.edu.au \
    --to=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®