public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: gentuxx <gentuxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] kdebase won't "re"-build
Date: Wed, 09 Aug 2006 23:49:38 -0700	[thread overview]
Message-ID: <44DAD702.8050709@gmail.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've recently found that bugs.gentoo.org is my new friend.  However,
this is sort of a one-off issue, and I haven't been able to find it
there.  I run `glsa-check -f all' maybe once a month, or less (I
usually get packages/versions recommended in the glsa by routine
updates).  I watch the GLSA blog, so I know when something comes out,
and I usually check which version I have.  999 times out of 1000, I've
already got the updated package.

Be that as it may, I've been trying to "get through" running the tool
successfully, and I am getting stuck on rebuilding kdebase-3.4.3-r2.
I'm actually using KDE 3.5, but would like to keep 3.4 around until
the next major version comes around (I'm just anal that way).  When it
goes to rebuild kdebase, it quickly errors out with the following:

configure: error:
you need to install kdelibs first.

If you did install kdelibs, then the Qt version that is picked up by
this configure is not the same version you used to compile kdelibs.
The Qt Plugin installed by kdelibs is *ONLY* loadable if it is the
_same Qt version_, compiled with the _same compiler_ and the same Qt
configuration settings.


!!! Please attach the following file when filing a report to
bugs.gentoo.org:
!!! /var/tmp/portage/kdebase-3.4.3-r2/work/kdebase-3.4.3/config.log

!!! ERROR: kde-base/kdebase-3.4.3-r2 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  kdebase-3.4.3-r2.ebuild, line 92:   Called kde_src_compile
  kde.eclass, line 164:   Called kde_src_compile 'all'
  kde.eclass, line 323:   Called kde_src_compile 'myconf' 'configure'
'make'
  kde.eclass, line 305:   Called econf '--with-dpms'
'--with-x-binaries-dir=/usr/bin' '--with-arts' '--with-ldap'
'--with-cups' '--with-gl' '--with-ssl' '--with-samba'
'--without-openexr' '--without-sensors' '--without-libusb'
'--without-libraw1394' '--without-hal' '--with-pam=yes'
'--without-java' '--with-x' '--enable-mitshm' '--without-xinerama'
'--with-qt-dir=/usr/qt/3' '--enable-mt'
'--with-qt-libraries=/usr/qt/3/lib' '--disable-dependency-tracking'
'--disable-debug' '--without-debug' '--enable-final' '--with-arts'
'--prefix=/usr/kde/3.4' '--mandir=/usr/kde/3.4/share/man'
'--infodir=/usr/kde/3.4/share/info' '--datadir=/usr/kde/3.4/share'
'--sysconfdir=/usr/kde/3.4/etc'
  ebuild.sh, line 541:   Called die

!!! econf failed
!!! If you need support, post the topmost build error, and the call
stack if relevant.


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.

Any pointers would be awesome.  I've finally managed to get through an
`emerge_world.sh' (custom script - if you're interested/curious
contact me offlist) after about a month (or more) of skipping through
packages to avoid stuff that wouldn't build.  This is the icing on the
cake.  If I can get through the `glsa-check', I'll switch profiles to
2006.1 (then, of course, rebuild).

TIA

- --
gentux
echo "hfouvyyAhnbjm/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'

gentux's gpg fingerprint ==> 5495 0388 67FF 0B89 1239  D840 4CF0 39E2
18D3 4A9E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE2tcCTPA54hjTSp4RAtbQAKCWy//zI2XW181fUAVKOG9GL/2q4ACgjnnL
/TfRlsQq2kUdsOLWxfMHx14=
=bujM
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-08-10  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  6:49 gentuxx [this message]
2006-08-10  8:20 ` [gentoo-user] kdebase won't "re"-build Dirk Heinrichs
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=44DAD702.8050709@gmail.com \
    --to=gentuxx@gmail.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