From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-dev List <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] kdelibs-3.0.1.20020604
Date: 16 Jun 2002 06:59:58 +0800 [thread overview]
Message-ID: <1024181998.26521.39.camel@rattus> (raw)
In-Reply-To: <200206152305.01221.danarmak@gentoo.org>
Thanks, I eventually traced my case to still having the old libpng on
the system (error message further back in the compiler messages, and a
hint from the maining list put me on track). I must have missed a step
when I followed the upgrade instructions! Whole of kde (re)compiled
fine after unmerging the old one - had to do gnome as well as that was
obviously affected. Two days gone recompiling :(
BillK
On Sun, 2002-06-16 at 04:04, Dan Armak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday 12 June 2002 15:47, Bill Kenworthy wrote:
> > Trying bring a system up to date and get this from
> > kdelibs-3.0.1.20020604
> >
> > using gcc version 2.95.3 20010315 (release)
> >
> > Any ideas?
> >
> > In file included from libkdecore_la.all_cpp.cpp:23:
> > kcharsets.cpp:420: warning: #warning FIXME?
> > cpp0: output pipe has been closed
> > g++: Internal compiler error: program cc1plus got fatal signal 15
> > make[3]: *** [libkdecore_la.all_cpp.lo] Error 1
> > make[3]: Leaving directory
> > `/var/tmp/portage/kdelibs-3.0.1.20020604/work/kdelibs-3.0.1/kdecore'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory
> > `/var/tmp/portage/kdelibs-3.0.1.20020604/work/kdelibs-3.0.1/kdecore'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory
> > `/var/tmp/portage/kdelibs-3.0.1.20020604/work/kdelibs-3.0.1'
> > make: *** [all-recursive-am] Error 2
> >
> > !!! ERROR: The ebuild did not complete successfully.
> > !!! Function kde_src_compile, Line -3694, Exitcode 2
> > !!! died running emake, kde_src_compile:make
> >
> > !!! emerge aborting on
> > /usr/portage/kde-base/kdelibs/kdelibs-3.0.1.20020604.ebuild .
>
> Please look at bug #3396 and my comments at the end.
>
> - --
> Dan Armak
> Gentoo Linux developer (KDE)
> Matan, Israel
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE9C53sUI2RQ41fiVERAvdAAJ9p7jYyPKzXC+jjPeec3/u3n4WXSQCfY7fY
> 3WmL/XMk9p23t6BzvrkW4jE=
> =tqy/
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Bill Kenworthy <billk@iinet.net.au>
prev parent reply other threads:[~2002-06-15 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-12 12:47 [gentoo-dev] kdelibs-3.0.1.20020604 Bill Kenworthy
2002-06-15 20:04 ` Dan Armak
2002-06-15 22:59 ` Bill Kenworthy [this message]
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=1024181998.26521.39.camel@rattus \
--to=billk@iinet.net.au \
--cc=gentoo-dev@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