Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 117389 - Emerge kdelibs
Summary: Emerge kdelibs
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: HPPA Linux
: High normal (vote)
Assignee: HPPA Porters
Depends on:
Reported: 2006-01-01 14:20 UTC by Giorgio
Modified: 2006-08-09 12:52 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Giorgio 2006-01-01 14:20:33 UTC
we are installing gentoo on hp j5600

"emerge --search gcc" show:
latest version available: 3.3.2-r1
latest version installed: 3.3.2-r1
Size of downloaded files: 23,033 Kb
Descripion: Gcc for 64bit hppa kernels
License: GPL-2 LGPL-2.1

"Gcc --version " show:
gcc (GCC) 3.3.6 (Gentoo 3.3.6, pie-8.7.8)

when we emerge kde-base/kdelibs, we have this trouble:
hppa2.0-unknown-linux-gnu-g++: cannot specify -o with -c or -S and multiple compilations.
make[5]: *** [kimiface_stub.lo] Error 1 
make[5]: leaving directory '/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/interfaces/kimproxy/library'
make[4]: *** [all-recursive] Error 1
make[4]: leaving directory '/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/interfaces/kimproxy/library'
make[3]: *** [all-recursive] Error 1
make[3]: leaving directory '/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/interfaces/kimproxy'
make[2]: *** [all-recursive] Error 1
make[2]: leaving directory '/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3/interfaces'
make[1]: *** [all-recursive] Error 1
make[1]: leaving directory '/var/tmp/portage/kdelibs-3.4.3/work/kdelibs-3.4.3'
make: *** [all] Error 2

!!! ERROR: kde-base/kdilibs-3.4.3 failed.
!!! Function kde_src_compile, Line 173, Exitcode 2
Comment 1 Guy Martin (RETIRED) gentoo-dev 2006-06-03 16:04:56 UTC
kde 3.5.2 has been rolled out.
Does this still happen ?
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2006-08-09 12:52:48 UTC
I'm closing this bug since no response to comment #1 ever emerged.