Summary: | kphone configure fails on checking about kde | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gavrila <gavrilao> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | ares_tyr, centic |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Gavrila
2004-03-05 11:25:24 UTC
It seems that kdb2html was deprecated in KDE 3.1.5 and is not contained in KDE 3.2 any more. Therefore kphone 3.1.4 will not compile against KDE 3.2 any more. I will try to update kphone to the current version 4.0.1. DUnno if I should post it here but renaming 3.1.4 ebuild to 4.0 worked until this sandbox violation make[1]: Entering directory `/var/tmp/portage/kphone-4.0/work/kphone-4.0/icons' install --mode=0755 --directory /usr/share/kphone/icons ACCESS DENIED mkdir: /usr/share/kphone install: cannot create directory `/usr/share/kphone': Permission denied make[1]: *** [install] Error 1 make[1]: Leaving directory `/var/tmp/portage/kphone-4.0/work/kphone-4.0/icons' make: *** [install] Error 2 !!! ERROR: net-misc/kphone-4.0 failed. !!! Function kde_src_install, Line 153, Exitcode 2 !!! died running make install, kde_src_install:make --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-net-misc_-_kphone-4.0-8701.log" mkdir: /usr/share/kphone --------------------------------------------------------------- Thoough creating manually the dir could be a workaround, there's surely a more efficient solution. Regards The sandbox-violation ocurrs because the install-target in the Makefile does not observe the target-directory that is passed, but hardcodes the /usr/share/kphone-directory. Therefore the solution will be to add a patch to adjust the Makefile.in/.am and/or submit the patch upstream for future inclusion in kphone. After adding some magic to configure it merges very well. So this issue is fixed. Closing this bug. |