From: John Levon <levon@movementarian.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: make xconfig broken in bk current
Date: Mon, 13 Jan 2003 01:20:33 +0000 [thread overview]
Message-ID: <20030113012032.GA73639@compsoc.man.ac.uk> (raw)
In-Reply-To: <3E2200C6.665A12CA@linux-m68k.org>
On Mon, Jan 13, 2003 at 12:56:54AM +0100, Roman Zippel wrote:
> > Can I just repeat my request to move this Qt stuff entirely out of the
> > kernel package, where it belongs ?
>
> We can discuss this during 2.7, until then I prefer to keep it close to
> the kernel, as the config system still has to mature a bit more.
OK, so you're fine with the moving to a different package when the
config library reaches a stable API ? Fair enough.
> > The current detection doesn't even start to get things working
> > correctly.
>
> For example?
You don't seem to set MOC correctly if you guess a Qt dir. It doesn't
cater for binaries called moc2 or libraries called qt3 or qt2[1]
regards
john
[1] I can't remember if some of these are only present on FreeBSD in
which case it wouldn't be relevant
--
Khendon's Law: If the same point is made twice by the same person,
the thread is over.
next prev parent reply other threads:[~2003-01-13 1:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 20:12 make xconfig broken in bk current Ed Tomlinson
2003-01-12 20:31 ` 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 [this message]
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=20030113012032.GA73639@compsoc.man.ac.uk \
--to=levon@movementarian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox