From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: Roman Zippel <zippel@linux-m68k.org>
Subject: Re: make xconfig broken in bk current
Date: Sun, 12 Jan 2003 15:12:59 -0500 [thread overview]
Message-ID: <200301121512.59840.tomlins@cam.org> (raw)
Roman Zippel wrote:
> Hi,
>
> Ed Tomlinson wrote:
>
>> make -f scripts/Makefile.build obj=scripts/kconfig scripts/kconfig/qconf
>> g++ -o scripts/kconfig/qconf scripts/kconfig/kconfig_load.o
>> scripts/kconfig/qconf.o -L/usr/share
>> /qt/lib -Wl,-rpath,/usr/share/qt/lib -lqt-mt -ldl
>> scripts/kconfig/qconf.o(.text+0x31): In function `ConfigView::tr(char
>> const*, char const*)':
>> : undefined reference to `QApplication::translate(char const*, char
>> : const*, char const*, QApplication:
>> :Encoding) const'
>
> Which distribution do you use?
> It looks like you try to use a different g++ version than qt was
> compiled with.
This makes sense. Debian has changed its default compiler to 3.2 in
sid... Suspect we will get quite a few reports like this one.
Solution would seem to be to fix the links in /usr/bin for:
gcc
g++
gcov
cpp
to point at the 2.95 binary, make clean xconfig
Thanks
Ed Tomlinson
PS. The kernel will not link here using 3.2....
next reply other threads:[~2003-01-12 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 20:12 Ed Tomlinson [this message]
2003-01-12 20:31 ` make xconfig broken in bk current John Levon
2003-01-12 21:03 ` Sam Ravnborg
2003-01-12 21:18 ` John Levon
2003-01-12 23:56 ` Roman Zippel
2003-01-13 1:20 ` John Levon
2003-01-13 21:02 ` Roman Zippel
2003-01-12 23:49 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 2:25 Ed Tomlinson
2003-01-12 13:58 ` Roman Zippel
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=200301121512.59840.tomlins@cam.org \
--to=tomlins@cam.org \
--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.