From 0c1ff07e5ae37807fd240547f9739a94c502a746 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN\"" Date: Tue, 6 Mar 2012 01:14:01 +0100 Subject: [PATCH] readme: update with a bit more information - accept patches to the infrastructure - document known limitations Signed-off-by: "Yann E. MORIN" --- README | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/README b/README index a02ff2c..408a67b 100644 --- a/README +++ b/README @@ -10,3 +10,33 @@ Such changes shall be directed directly to the appropriate mailing list, and they will eventually find their way is this package at the next sync: mailto:linux-kbuild@vger.kernel.org + +However, if there is a bug in the packaging infrastructure, patches +are most welcome, of course! Most notably, because this is my very +first autostuff-based package, I may have done mistakes here and +there... + +As such, there are currently a few known limitations: + +- statically linking is much, much more complex than it should be. + I have been seemingly able to build part of the frontends with + such incantations of ./configure and make: + ./configure LDFLAGS=-static --disable-shared --enable-static \ + --disable-gconf --disable-qconf + make LDFLAGS="-all-static -static-libtool-libs" nconf_EXTRA_LIBS=-lgpm + +- the nconf frontends requires (at least on my machine) to linked + against GPM; this is not detected when staticaly linking (hence + the nconf_EXTRA_LIBS in the command above). + +- statically linking the graphical frontends (gconf and qconf) is + *not* supported: I am missing static libs for Qt3Support, so + qconf does not link. And there is a stupid bug in libtool that + prevent properly linking against installed static libraries + (seemingly fixed in 2.4, but not quite yet, in fact...), so + gconf does not link. That's why they are disabled above. + +Note that, provided you have the required dependencies, all +frontends are properly built if you link dynamicaly. The following +just works as expected: + ./configure && make -- 2.39.5