public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kdelibs fails to build
Date: Sat, 03 Jul 2010 12:38:39 -0500	[thread overview]
Message-ID: <4C2F759F.2070409@gmail.com> (raw)
In-Reply-To: <201007031749.29838.michaelkintzios@gmail.com>

Mick wrote:
> On Saturday 03 July 2010 17:28:41 Mick wrote:
>    
>> On Saturday 03 July 2010 12:49:49 Dale wrote:
>>      
>>> Mick wrote:
>>>        
>>>> I am running the kde-4.4.4 upgrade on a x86 machine and this is how
>>>> kdelibs fails:
>>>> ====================================
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/netw
>>>> or k/k3socketdevice.h:275: warning:   by ‘virtual qint64
>>>> KNetwork::KSocketDevice::writeData(const char*, qint64, const
>>>> KNetwork::KSocketAddress*)’
>>>> [ 54%] Building CXX object
>>>> kio/CMakeFiles/kio.dir/kssl/ksslcertificate.o [ 54%] Building CXX
>>>> object kio/CMakeFiles/kio.dir/kssl/ksslkeygen.o [ 54%] Building CXX
>>>> object kio/CMakeFiles/kio.dir/kssl/ksslsettings.o [ 54%] Building CXX
>>>> object kio/CMakeFiles/kio.dir/kssl/ksslutils.o
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/ks
>>>> sls ettings.cpp: In member function ‘void KSSLSettings::load()’:
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> ls ettings.cpp:134: warning: ‘void KConfigGroup::changeGroup(const
>>>> char*)’ is deprecated (declared at
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/conf
>>>> i g/kconfiggroup.h:159)
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> l settings.cpp:139: warning: ‘void KConfigGroup::changeGroup(const
>>>> char*)’ is deprecated (declared at
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/conf
>>>> i g/kconfiggroup.h:159)
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> l settings.cpp:144: warning: ‘void KConfigGroup::changeGroup(const
>>>> char*)’ is deprecated (declared at
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/conf
>>>> i g/kconfiggroup.h:159)
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> l settings.cpp: In member function ‘void KSSLSettings::save()’:
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> ls ettings.cpp:177: warning: ‘void KConfigGroup::changeGroup(const
>>>> char*)’ is deprecated (declared at
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/conf
>>>> i g/kconfiggroup.h:159)
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kio/kssl/kss
>>>> l settings.cpp:182: warning: ‘void KConfigGroup::changeGroup(const
>>>> char*)’ is deprecated (declared at
>>>> /var/tmp/portage/kde-base/kdelibs-4.4.4/work/kdelibs-4.4.4/kdecore/conf
>>>> i g/kconfiggroup.h:159) [ 54%] Building CXX object
>>>> kio/CMakeFiles/kio.dir/kssl/ksslx509v3.o Linking CXX shared library
>>>> ../lib/libkio.so
>>>> /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/../../../../i686-pc-linux-gnu/bin/
>>>> ld
>>>>
>>>> : warning: creating a DT_TEXTREL in object.
>>>>
>>>> collect2: ld returned 1 exit status
>>>> make[2]: *** [lib/libkio.so.5.4.0] Error 1
>>>> make[1]: *** [kio/CMakeFiles/kio.dir/all] Error 2
>>>> make: *** [all] Error 2
>>>>
>>>>    * ERROR: kde-base/kdelibs-4.4.4 failed:
>>>>    *   Make failed!
>>>>    *
>>>>    * Call stack:
>>>>    *     ebuild.sh, line   54:  Called src_compile
>>>>    *   environment, line 4033:  Called kde4-base_src_compile
>>>>    *   environment, line 3111:  Called cmake-utils_src_compile
>>>>    *   environment, line 1258:  Called _execute_optionaly 'src_compile'
>>>>    *   environment, line  665:  Called enable_cmake-utils_src_compile
>>>>    *   environment, line 1623:  Called cmake-utils_src_make
>>>>    *   environment, line 1277:  Called die
>>>>    * The specific snippet of code:
>>>>    *           emake "$@" || die "Make failed!";
>>>>
>>>> ====================================
>>>>
>>>> Any ideas?
>>>>          
>>> Do you have MAKEOPTS set to a high number in make.conf?  I ask because
>>> in my 'knowing very little mind' I think it is trying to make a link to
>>> a file that kdelibs is supposed to be making.  It may be trying to link
>>> to something that isn't there yet so it failed.  If you have that set to
>>> 2 or higher, try setting it to 1 and see if that helps.
>>>
>>> Hope that works.  At least it didn't fail at 99%.  lol
>>>
>>> Dale
>>>        
>> Thanks Dale, I tried with -j1 and it fails with the same libkio.so error.
>>      
> I found a bug about it (324061) and I'm now trying again without ccache.
>    

That would be the next thing to try.  Most packages can compile with 
higher than -j1 and with ccache but some can not do so well.  I hope it 
compiles when you disable that.

Dale

:-)  :-)



  reply	other threads:[~2010-07-03 17:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03  8:09 [gentoo-user] kdelibs fails to build Mick
2010-07-03 11:49 ` Dale
2010-07-03 16:28   ` Mick
2010-07-03 16:49     ` Mick
2010-07-03 17:38       ` Dale [this message]
2010-07-04  7:46         ` Stéphane Guedon
2010-07-04  8:59       ` Neil Bothwick
2010-07-04  9:44         ` Mick

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=4C2F759F.2070409@gmail.com \
    --to=rdalek1967@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