From: Dirk Heinrichs <ext-dirk.heinrichs@nokia.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdebase won't "re"-build
Date: Thu, 10 Aug 2006 10:20:36 +0200 [thread overview]
Message-ID: <200608101020.36200.ext-dirk.heinrichs@nokia.com> (raw)
In-Reply-To: <44DAD702.8050709@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
Am Donnerstag, 10. August 2006 08:49 schrieb ext gentuxx:
> configure: error:
> you need to install kdelibs first.
>
> I've gone through some toolchain changes recently, so I wasn't
> completely surprised by this message the first time I got it. So, I
> immediately rebuilt qt, which actually rebuilt qt4 (I think qt3 is
> actually being detected by the kdebase ebuild, but we'll get to
> that). I also rebuilt kdelibs (at the same time as qt - qt was
> rebuilt first), then tried the kdebase rebuild again. I get the same
> error. So, I said to myself, "ok, it's picking up qt3 (not qt4, which
> I just rebuilt) so I need to rebuild that". So I did. I did a
> `emerge -av =x11-libs/qt-3.3.6-r1', which completed successfully, but
> when attempting a rebuild of kdebase I get the same, above, error.
If it says "install kdelibs first" (means re-build), why didn't you do so?
Bye...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@capgemini.com
Hambornerstraße 55 | Web: http://www.capgemini.com
D-40472 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-10 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 6:49 [gentoo-user] kdebase won't "re"-build gentuxx
2006-08-10 8:20 ` Dirk Heinrichs [this message]
2006-08-10 9:37 ` Gian Domeni Calgeer
2006-08-10 9:47 ` Dirk Heinrichs
2006-08-10 16:47 ` Richard Fish
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=200608101020.36200.ext-dirk.heinrichs@nokia.com \
--to=ext-dirk.heinrichs@nokia.com \
--cc=gentoo-user@lists.gentoo.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