Mark my coments are inline
On Sat, May 31, 2008 at 4:16 PM, Mark Wright <markwright at internode.on.net> wrote: > Hi Luc, Ade and Stefan, > > I emailed this to the list, but its being held for moderator > approval as its too large. So personal email while the > list catches up. > > Hi, > > Stefan has backported HAL to Solaris 10u5, which > I think is awesome. > > I've attached some diffs to compile and package > Stefan's port of HAL to Solaris 10u5. Currently > there are some manual steps to compile it, so > its not quite ready yet, the status is: > > (1) When packaging HAL, I do not know where to put: > > /usr/etc/dbus-1/hal.conf > Should be /etc/dbus-1/hal.conf > > So I just placed it at the above location, no idea > if that is correct or not. > > (2) The make goes into an infinite loop when it > tries to build po. I worked around it by the > follwing in configure.sh > > # make in po goes into an infinite loop on my box, disable > # it for the moment to workaround this, since I do not know > # why it is looping. Also that is the only reason I added > # --disable-man-pages --disable-gtk-doc. > $KBE_PREFIX/bin/sed -i -e "s/ po //" Makefile > $KBE_PREFIX/bin/sed -i -e "s/ docprivileges//" Makefile > > Of course that has the dis-advantage of no man pages or > documentation currently. > > (3) Currently it fails building FOSShal with FOSSdbus, > as foss is missing dbus-glib-1, the error is: > > No package 'dbus-glib-1' found > dbus-glib is in dude, but I do not put there pspc, because it doesn't build on my machine pkgbuild: creating statemachine-server pkgbuild: make[7]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus/examples/statemachine' pkgbuild: make[6]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus/examples/statemachine' pkgbuild: make[5]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus/examples' pkgbuild: make[4]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus/examples' pkgbuild: make[3]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus' pkgbuild: make[2]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/dbus' pkgbuild: Making all in tools pkgbuild: make[2]: Entering directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/tools' pkgbuild: make[2]: *** No rule to make target `system-dbus-introspect.xml', needed by `dbus-bus-introspect.xml'. Stop. pkgbuild: make[2]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74/tools' pkgbuild: make[1]: *** [all-recursive] Error 1 pkgbuild: make[1]: Leaving directory `/home/luc/packages/BUILD/FOSSdbus-glib-0.74/amd64/DBUS-GLIB/0.74' pkgbuild: make: *** [all] Error 2 > > I guess we could add dbus-glib-1 to foss for when stock > Solaris 10u5 gnome 2.6 is used. I can not test it with > Solaris 10u5 gnome 2.6 though, as I trashed gnome 2.6 > from my machine. Also I am not sure which dbus-glib-1 > to add. Well apart from the idea of bumping foss glib2 and > dbus to the versions that JDS gnome 2.22, and adding > the corresponding dbus-glib, the JDS gnome 2.22 versions are: > > glib2 2.16.3 > dbus 1.2.1 > dbus-glib 0.74 > > But I don't know if KDE cares about the versions of these > gnome base libraries or not. > > (4) Currently I am building hal as SUNWhal using the > following procedure: > > perl Respect.pl --with-all --without-upload --without-build hal.pspc > cp -p FOSShal.spec SUNWhal.spec > sed -i -e "s/FOSShal/SUNWhal/g" SUNWhal.spec > pkgtool build SUNWhal.spec > > And then as root: > > # svcadm enable hal > # > > Then svcs -vx hal should show it running: > > # svcs -vx hal > svc:/system/hal:default (Hardware Abstraction Layer daemon) > State: online since Sat May 31 12:32:32 2008 > See: man -M /usr/man -s 1M hal > See: /var/svc/log/system-hal:default.log > Impact: None. > # cat /etc/release > Solaris 10 5/08 s10x_u5wos_10 X86 > Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. > Use is subject to license terms. > Assembled 24 March 2008 > # > > I'm using SUNWgnome-base-libs and SUNWdbus from the > JDS gnome 2.22, compiled from spec files, from: > > svn co > svn+ssh://anon at svn.opensolaris.org/svn/jds/spec-files/branches/gnome-2-22 > gnome-2-22 > Take care, becaseu guys from JDS sometimes using gcc instead of Sun Studio > > This also has the advantage that some things from SFE: > > http://pkgbuild.sourceforge.net/spec-files-extra/ > > like mplayer, compile on Solaris 10u5. > same as one step before > > (5) I tried to tweak things though so that if > SUNWgnome-base-libs and SUNWdbus are not installed, then > it tries to compile it as FOSShal. However it does not > quite compile at present like that due to (3). > No, we have FOSSglib (glib-2.12.12) and FOSSdbus (or SUNWdbus o Nevada) for that > > (6) I had to add libfstyp from OpenSolaris as FOSSlibfstyp, > since it is missing from Solaris 10u5 (or at least it is > from my box, it is not in SUNWhea which is installed). > ??? Stefan ? > > I've attached the diffs for this in case any one would > like to test, comment, etc. > > There are some other little things in the diffs: > > (7) Mindless change to rm lib*.a files in various > install.sh scripts. > > (8) Some stuff to change /bin/sh to /bin/bash, which > is only required if libtool 2.2.4 was used. It > would probably not hurt with libtool 1.5.X, but > I haven't tested it. Anyway, if you don't want > those change I can svn revert them. I've compiled FOSS > up to and including FOSSlibshout with libtool 2.2.4, > but we would probably like to pretend that libtool > doesn't exist, so can understand if you want to > stay with the hacked libtool 1.5.X for most stuff. > If I hit any libtool issues though probably the first > thing I will try is libtool 2.2.4. Its requirement for > /bin/bash is kind of annoying. I've had problems > earlier with trying to fix issues in the old libtool. > this is the reason, why I would not use libtool 2.2.4 globaly. Stefan, Ade what do you think. Do you would using libtool 2.2.4 ? It is simple put libtool 2.2.4 into KBE, harder way is migrate out hacked libtool 1.5 transform to 'our hacked' libtool 2.2.4 > > (9) libcaptury need /amd64 or whatever the 64 bit > /$_arch is added to the end of the output for: > you can use ${_libsuffix} in shell scripts (configure.sh and etc.) which is exported by pkgtool and contains /amd64 or /sparcv9 > > pkg-config --libs "xfixes >= 1.0.0" > I did not have a time to adjust libcaptury .... BTW, do you have capse built ? > > (10) CTL needs some extra #includes when compiled with -g . > It could be, but we don't use -g at this time. Maybe we should add switch for Respectl .... somethng like --with-debug a then will be setup just only debug flags. > > (11) Use SFElibcdio instead of FOSSlibcdio is SFElibcdio > is installed. > Why ? I don't know which vesion or fixes contains SFElibcdio, but you can expect some troubles maybe. > > (12) jasper built %{_bindir}/jiv. > ? > > (13) dirmngr, I had problems compiling it with the hacked > libtool 1.5.X earlier when compiling for 64 bit amd64, > I submitted these diffs earlier to fix that. So not sure > if anyone needs these now or not. > no problem with dirmngr.... dude contains your previous patches for dirmngr which are fine. :) > > Thanks, Mark > > -- > Thanks Luc -- Lukas 'Luc' Oboril IRC nickname: luc^ at freenode When dealing with people, let us remember we are not dealing with creatures of logic. We are dealing with creatures of emotions, creatures bristling with prejudices and motivated by pride and vanity. Dale Carnegie -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/kde-discuss/attachments/20080531/ff8b9e0f/attachment.html>
