From: Peter Samuelson <peter@cadcamlab.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [kbuild] Possibility to sanely link against off-directory .so
Date: Thu, 7 Nov 2002 05:47:47 -0600 [thread overview]
Message-ID: <20021107114747.GM4182@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0211071149200.13258-100000@serv>
[Peter Samuelson]
> > Basically, what I'm saying is, I see no need for the existing .so in
> > the kernel build, much less another one. Static libraries are ever so
> > much easier to manage.
[Roman Zippel]
> If you want to limit people to the config tools in the kernel, there
> is indeed no need for a shared library. Note that during the next
> development cycle all graphical front ends are possibly removed.
Huh? I don't get it. How is a shared library any better than a static
library in this regard? I'm pondering the traditional advantages of
shared libraries, and I cannot think of a single one that matters here.
Peter
next prev parent reply other threads:[~2002-11-07 11:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 18:52 Petr Baudis
2002-11-06 21:29 ` Sam Ravnborg
2002-11-06 22:03 ` Petr Baudis
2002-11-07 10:00 ` Peter Samuelson
2002-11-07 10:57 ` Roman Zippel
2002-11-07 11:47 ` Peter Samuelson [this message]
2002-11-07 12:09 ` Roman Zippel
2002-11-07 12:37 ` Peter Samuelson
2002-11-07 13:04 ` Roman Zippel
2002-11-07 13:22 ` Peter Samuelson
2002-11-07 13:45 ` Roman Zippel
2002-11-07 13:59 ` Peter Samuelson
2002-11-07 15:24 ` Petr Baudis
2002-11-07 16:20 ` [kbuild-devel] " Kenn Humborg
2002-11-07 18:52 ` Peter Samuelson
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=20021107114747.GM4182@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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®