| View previous topic :: View next topic |
| Author |
Message |
Kate Monster Apprentice

Joined: 13 Jun 2006 Posts: 209 Location: Clarkston, Michigan
|
Posted: Tue Jun 01, 2010 7:00 am Post subject: |
|
|
Hi,
akode will not build. I lost the exact error message as I got fed up with it and hacked around it, but, at first, during make it complained of a missing libakode.so. After some digging I discovered that file was linked to a libakode.so.2.0.0 which didn't exist. Out of curiosity I moved a local copy of that .so into the temp library folder to see what would happen, and the compilation made it to the install stage, but then complained about more missing .so files, and I can only conclude that the ebuild was not doing any linking. Like I said I've worked around it, I disabled the arts use flag for the time being as I've got 427 more packages to update and don't have time to deal with this right now. Does anyone else run into this issue? |
|
| Back to top |
|
 |
Kate Monster Apprentice

Joined: 13 Jun 2006 Posts: 209 Location: Clarkston, Michigan
|
Posted: Fri Jun 04, 2010 5:24 pm Post subject: |
|
|
| Another user fixed a very similar error with Amarok 1.4 by masking ">=sys-devel/autoconf-2.64". I will try this and report back. Also, does KDE 3.5 require GCC 4.2 or earlier? Trying to emerge many KDE 3.5 packages makes them die complaining of libstdc++ lacking "GLIBCXX_3.4.11" unless I use GCC 4.2. Is there anyway around this? |
|
| Back to top |
|
 |
pappy_mcfae Watchman


Joined: 27 Dec 2007 Posts: 5609 Location: Dallas
|
|
| Back to top |
|
 |
Kate Monster Apprentice

Joined: 13 Jun 2006 Posts: 209 Location: Clarkston, Michigan
|
Posted: Fri Jun 04, 2010 11:19 pm Post subject: |
|
|
| pappy_mcfae wrote: | I use gcc-4.3.2, and have been for some time. How often do you sync?
Cheers,
Pappy | I switched to 4.4 myself. My system did in fact go un-updated for several months, but I thought the error message translated to simply "your libstdc++ is too new for this package". Apparently I was wrong, because after wiping out 3.5, running emerge -uDN world && emerge -e world, and then emerging 3.5 again, and 75/250 packages have emerged without incident, so I must have spoken too soon. Will report back if any errors pop up. |
|
| Back to top |
|
 |
pappy_mcfae Watchman


Joined: 27 Dec 2007 Posts: 5609 Location: Dallas
|
|
| Back to top |
|
 |
ssuominen Developer

Joined: 30 Sep 2005 Posts: 1376 Location: Finland
|
Posted: Sat Jun 05, 2010 11:12 am Post subject: |
|
|
| For the record, KDE 3.5.x in kde-sunset is fine with GCC 4.4.x simply because it was also fine when it was in Portage. The first version of GCC that's *not* tested with KDE 3.5.x ebuilds is 4.5.x, and it will most likely cause build-time problems, ones that are rather easy to fix. |
|
| Back to top |
|
 |
jesnow Guru

Joined: 26 Apr 2006 Posts: 394
|
Posted: Thu Dec 09, 2010 10:50 pm Post subject: |
|
|
What about Trinity? I'm still soldiering along with kde-sunset on 2 machines, but Trinity looks like it has rapidly improved 3.5 to the point where I wish I had it. Has anybody got it working? I'm not afraid to try to compile it, but I've never written an ebuild, so I'm no help there.
I saw some chatter some time ago about kde-sunset and trinity being combined, but i don't know where that went. I saw some posts along the lines of "it would be a good idea" and there's been nothing since.
Has anybody heard anything?
jon |
|
| Back to top |
|
 |
pappy_mcfae Watchman


Joined: 27 Dec 2007 Posts: 5609 Location: Dallas
|
|
| Back to top |
|
 |
pappy_mcfae Watchman


Joined: 27 Dec 2007 Posts: 5609 Location: Dallas
|
|
| Back to top |
|
 |
pappy_mcfae Watchman


Joined: 27 Dec 2007 Posts: 5609 Location: Dallas
|
|
| Back to top |
|
 |
|