mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: kbuild-devel <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 07:22:45 -0600	[thread overview]
Message-ID: <20021107132245.GO4182@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0211071352270.13258-100000@serv>


[Roman Zippel]
> New features will be added and only the parser that comes with the kernel 
> will understand them. It's less likley that the library API will change.

Even if this is true - I'll grant you that it may be - let the vendor
package /usr/bin/qconf as a shell script that links /usr/lib/qconf.o
with -lqt and $(LINUX)/scripts/kconfig/libkconfig.a .  It's a little
unorthodox, but it removes the hackery of figuring out how HOSTCC is
supposed to build a shared library and whether any magic is needed at
runtime.  Removes the need for the horrible stuff libtool was invented
for, in other words.

Remember, the whole point of HOSTCC is to support a build environment
different from the compile target - arbitrarily different, even.

Peter

  reply	other threads:[~2002-11-07 13:18 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
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 [this message]
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=20021107132245.GO4182@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®