kdelibs-3.5.3-r3

hfish · n00b Joined: 29 Jun 2006 Posts: 10

Hello,

merging kdelibs-3.5.3-r3 gives me the following error:

kfiaciarka · Posted: Thu Jun 29, 2006 6:51 pm Post subject:

downgrade autoconf to previous version:)

hfish · n00b Joined: 29 Jun 2006 Posts: 10

I have downgraded to autoconf-2.59-r7 from the stable branch but kdelibs-3.5.3-r3 has autoconf-2.60 as a dependency so the problem still persists because emerge installs autoconf-2.60 first. I think the error is in the ebuild because emerge says it cant find the configure script ...... any idea?

jasm · Posted: Thu Jun 29, 2006 10:00 pm Post subject:

I noticed you're using confcache as FEATURE. Perhaps this is the culprit? I suggest removing this from your /etc/make.conf and try emerging again.

hfish · n00b Joined: 29 Jun 2006 Posts: 10

Removing 'confcache' from FEATURES did not resolve the problem.....

enderandrew · l33t Joined: 25 Oct 2005 Posts: 731

I can't get this to compile at all either. Perhaps modify the ebuild to use the stable autoconf?
_________________
Nihilism makes me smile.

hfish · n00b Joined: 29 Jun 2006 Posts: 10

I dont think the error is related to autoconf-2.60, emerge says that kde needs autoconf-2.53 or newer, so autoconf-2.60 should be right, the error is elsewhere....

cerebus_k · Posted: Fri Jun 30, 2006 7:01 am Post subject:

FWIW, I was able to emerge kdelibs 3.5.3-r3 successfully but that was with autoconf-2.59d (I used genlop to figure out when kdelibs and autoconf were emerged). I kicked off anoher emerge of kdelibs-3.5.3-r3 now that I have autoconf-2.60 installed and it made it past this point:

cerebus_k · Posted: Fri Jun 30, 2006 7:06 am Post subject:

I just noticed https://forums.gentoo.org/viewtopic-t-475822-highlight-.html. It's not exactly the same error msg but I was struck by the part that said:

hfish · n00b Joined: 29 Jun 2006 Posts: 10

Removing ccache fom FEATURES did not resolve the problem.
This is the whole output of the emerge kdelibs-3.5.3-r3 command:

puggy · Posted: Fri Jun 30, 2006 10:15 am Post subject:

I ran into this problem. I did an emerge sync in case it was an error in the ebuild which had been fixed, I got some new packages, none of which should have effected kdelibs. I noticed that there was a portage update to do though, which I took, then kdelibs compiled ok. That is with portage-2.1.1_pre1-r5. I don't have time to actually investigate this problem, but that did seem to fix it for me.
_________________
Where there's open source , there's a way.

puggy · Posted: Fri Jun 30, 2006 10:16 am Post subject:

Ah, you already seem to be on that version of portage. Sorry I couldn't be more help.
_________________
Where there's open source , there's a way.

TheIxian · Posted: Fri Jun 30, 2006 1:39 pm Post subject:

I was having the exact same issue. I did an emerge --sync followed by a re-emerge of autoconf-2.60 and now the kdelibs-3.5.3-r3 compile is going.

I was running portage-2.1.1_pre1-r3 before the sync.
_________________
Irony can be pretty ironic sometimes

hfish · n00b Joined: 29 Jun 2006 Posts: 10

I have tried a emerge --sync and to re-emerge autoconf but the error still remains

Flameeyes · Posted: Fri Jun 30, 2006 6:00 pm Post subject:

The problem is the one reported in https://bugs.gentoo.org/show_bug.cgi?id=138187 and has been resolved already since a couple of days, basically the same day that 2.60 was released.

Make sure you're _not_ using an overlay that comes with kde.eclass, because as many other fixes, it has been pushed through the eclass. If the overlay has one based on an old version of our, you'll be on your own.

Note that all the eclasses that used to add the hidden visibility support are not needed anymore, kdehiddenvisibility is there for that, and for all the people using kdenewldflags, I suggest reading http://farragut.flameeyes.is-a-geek.org/articles/2006/06/22/nonsensical-hacks-why-i-find-kdenewldflags-stupid .
_________________
You want to know what I'm working on right now? Just follow my blog.