Re: KBE 1.0 - Build enviroment for KDE
Damian Wojslaw <[email protected]> Thu, 24 Jan 2008 10:02:53 +0100
| Newsgroups | gmane.comp.kde.solaris |
|---|---|
| Message-ID | <[email protected]> |
Lukas Oboril pisze:
> Looking forward to you comments!
> Luc
>
Hi, I write for the sake of keeping it somewhere documented. As stated
in irc discussion, I got KBE to compile and install with:
-bash-3.00$ uname -a
SunOS wojslaw.pl 5.10 Generic_127112-06 i86pc i386 i86pc
-bash-3.00$ /opt/SUNWspro/bin/cc -V
cc: Sun C 5.9 SunOS_i386 Patch 124868-02 2007/11/27
-bash-3.00$ /opt/SUNWspro/bin/CC -V
CC: Sun C++ 5.9 SunOS_i386 Patch 124864-01 2007/07/25
-bash-3.00$ isainfo
amd64 i386
It took less than three hours.
During the build I have hit something:
[...]
1.
Executing(%clean): /bin/bash
/var/tmp/pkgbuild-root/pkgbuild-tmp-7.14109
2.
+ umask 022
3.
+ uname -a
4.
SunOS wojslaw.pl 5.10 Generic_127112-06 i86pc i386 i86pc Solaris
5.
+ cd //root/packages/BUILD
6.
+ rm -rf /var/tmp/pkgbuild-root/KBEenv-1.0.0-build
7.
+ exit 0
8.
Installing package KBEenv
9.
10.
The following files are already installed on the system and are being
11.
used by another package:
12.
* /opt/kdebld <attribute change only>
13.
14.
* - conflict with a file which does not belong to any package.
15.
16.
Installation of <KBEenv> was suspended (administration).
17.
No changes were made to the system.
18.
KBE setup FAILED
It turned out, that I was using a user with profile=Primary
Administrator. Changing profile to Software Installation made issue go
away. Also, I have tried it with profile=Software Installation,Primary
Administrator and it came back. So, don't use root, don't use PA
profile. Just Software Installation.
Regards
Damian Wojslaw
___________________________________________________
This message is from the kde-solaris mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.