From: Mickey Stein <yekkim@pacbell.net>
To: linux-kernel@vger.kernel.org
Cc: zippel@linux-m68k.org
Subject: [PATCH] kconfig: Makefile xconfig problem: qconf libs/cflags error
Date: Fri, 11 Nov 2005 05:14:09 -0800 [thread overview]
Message-ID: <43749921.2010603@pacbell.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
$make xconfig generates this error on the last couple kernels:
(2.6.14-git14, git13)
make xconfig
HOSTCXX scripts/kconfig/qconf.o
HOSTLD scripts/kconfig/qconf
/usr/bin/ld: cannot find -l-ldl
collect2: ld returned 1 exit status
make[1]: *** [scripts/kconfig/qconf] Error 1
make: *** [xconfig] Error 2
The actual problem may be at another level, since I don't see a
difference between the scripts/kconfig/Makefile & prior ones that work,
but this patch seems in line with other targets that work and used the
standard pkg-config --libs --cflags setup.
Signed-off-by: Mickey Stein <yekkim@pacbell.net>
---
[-- Attachment #2: qconf.patch --]
[-- Type: text/x-patch, Size: 694 bytes --]
--- linux-2.6.14-git14/scripts/kconfig/Makefile.orig.xx 2005-11-11 04:10:34.000000000 -0800
+++ linux-2.6.14-git14/scripts/kconfig/Makefile 2005-11-11 04:11:44.000000000 -0800
@@ -129,8 +129,8 @@
HOSTCFLAGS_lex.zconf.o := -I$(src)
HOSTCFLAGS_zconf.tab.o := -I$(src)
-HOSTLOADLIBES_qconf = -L$(QTLIBPATH) -Wl,-rpath,$(QTLIBPATH) -l$(LIBS_QT) -ldl
-HOSTCXXFLAGS_qconf.o = -I$(QTDIR)/include -D LKC_DIRECT_LINK
+HOSTLOADLIBES_qconf = `pkg-config qt-mt --libs`
+HOSTCXXFLAGS_qconf.o = `pkg-config qt-mt --cflags` -D LKC_DIRECT_LINK
HOSTLOADLIBES_gconf = `pkg-config gtk+-2.0 gmodule-2.0 libglade-2.0 --libs`
HOSTCFLAGS_gconf.o = `pkg-config gtk+-2.0 gmodule-2.0 libglade-2.0 --cflags` \
next reply other threads:[~2005-11-11 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 13:14 Mickey Stein [this message]
2005-11-11 14:26 ` [PATCH] kconfig: Makefile xconfig problem: qconf libs/cflags error Roman Zippel
2005-11-11 15:34 ` Mickey Stein
2005-11-14 1:24 ` Roman Zippel
2005-11-14 15:18 ` Mickey Stein
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=43749921.2010603@pacbell.net \
--to=yekkim@pacbell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.