I cannot and I found the following reasons:
ldd /opt/trinity/bin/groupwarewizard libegroupwarewizard.so => not found libsloxwizard.so => not found libkolabwizard.so => not found libexchangewizard.so => not found
ldd /opt/trinity/bin/egroupwarewizard libegroupwarewizard.so => not found
ldd /opt/trinity/bin/exchangewizard libexchangewizard.so => not found
ldd /opt/trinity/bin/kolabwizard libkolabwizard.so => not found
ldd /opt/trinity/bin/scalixwizard libscalixwizard.so => not found
ldd /opt/trinity/bin/groupwisewizard libgroupwisewizard.so => not found
My build script includes:
-DWITH_ALL_OPTIONS=ON -DBUILD_ALL=ON
The *.so files exist, but none of the binaries are linked
correctly.
Darrell
Starts fine:
http://www.3111skyline.com/dl/dt/trinity/ss/tde-groupware- wizard.jpg
Notice anything unusual about the screen grab? The title bar? I'll fix the branding when I push the changes for the menu.
I notice in your screen grab you do not have a button for Novell Groupwise. 3.5.10 has that button:
http://humanreadable.nfshost.com/misc/groupwise-3.5.10.png
Does the groupware software have any other Trinity dependencies? I get the same results with 3.5.13 and 3.5.12. Won't start and didn't link correctly.
Starts fine on 3.5.10.
I am missing something obvious that all of those package sets have the same problem?
Darrell
On 02/13/2014 02:52 PM, Darrell Anderson wrote:
Starts fine:
http://www.3111skyline.com/dl/dt/trinity/ss/tde-groupware- wizard.jpg
Notice anything unusual about the screen grab? The title bar? I'll fix the branding when I push the changes for the menu.
Went right over my head -- good catch.
I notice in your screen grab you do not have a button for Novell Groupwise. 3.5.10 has that button:
What got deleted? I haven't seen that in any of my new builds???
There is nothing I am doing differently, not that I am aware of, let's compare again:
source=('tdebase.tar.gz' # source 'patches.tar.bz2' # standard patches 'arch-kdeshutdown.png' # fancy Archlinux icon 'kdm-default-face.png' # fix the missing default 'agent-shutdown.sh' # gpg agent shutdown 'agent-startup.sh' # gpg agent startup 'tdm-trinity' # old initscript for Arch 'trinity.desktop' # starttde desktop file 'tdm.service' # systemd service file for TDE 'blueglass.png' # kicker background 'r14-xsession.patch' # Xsession patch for Arch 'tdebase-kdesktop-systemd.diff' # Slavek's systemd patch )
build() {
cd ${srcdir}/${pkgname#*-}
msg "Setting PATH, CMAKE and Trinity Environment variables" # Source the QT and TDE profile [ "$QTDIR" = "" ] && . /etc/profile.d/tqt3.sh [ "$TDEDIR" = "" ] && . /etc/profile.d/trinity.sh
msg "Patching - tdebase patch set...." for patch in ${srcdir}/patches/*.patch; do _p=`basename $patch` msg "Applying patch $_p..." patch -Np0 -i $patch done
## fix for user session tracking in pure systemd environment msg "Patch fix for user session tracking in pure systemd environment" patch -Np1 -i "${srcdir}/tdebase-kdesktop-systemd.diff"
msg "Creating out-of-source build directory: ${srcdir}/build" mkdir -p ../build cd ../build
msg "Starting cmake..."
cmake ${srcdir}/tdebase \ -DCMAKE_INSTALL_PREFIX=${TDEDIR} \ -DSYSCONF_INSTALL_DIR=${TDEDIR}/etc \ -DWITH_SASL=ON \ -DWITH_LDAP=ON \ -DWITH_SAMBA=ON \ -DWITH_OPENEXR=ON \ -DWITH_XCOMPOSITE=ON \ -DWITH_XCURSOR=ON \ -DWITH_XFIXES=ON \ -DWITH_XRANDR=ON \ -DWITH_XRENDER=ON \ -DWITH_XDAMAGE=ON \ -DWITH_XEXT=ON \ -DWITH_XTEST=ON \ -DWITH_OPENGL=ON \ -DWITH_XSCREENSAVER=ON \ -DWITH_LIBART=ON \ -DWITH_LIBUSB=ON \ -DWITH_LIBRAW1394=ON \ -DWITH_PAM=ON \ -DWITH_XDMCP=ON \ -DWITH_XINERAMA=ON \ -DWITH_ARTS=ON \ -DWITH_I8K=ON \ -DWITH_SENSORS=ON \ -DWITH_HAL=OFF \ -DWITH_TDEHWLIB=ON \ -DWITH_UPOWER=ON \ -DBUILD_ALL=ON \ -DWITH_GCC_VISIBILITY=ON \ -DCMAKE_BUILD_TYPE=Release
make $NUMJOBS }
All of the patch files are here if you want to look at them:
http://www.3111skyline.com/dl/dt/trinity/tmp/tde-tdebase/
Does the groupware software have any other Trinity dependencies? I get the same results with 3.5.13 and 3.5.12. Won't start and didn't link correctly.
Starts fine on 3.5.10.
I am missing something obvious that all of those package sets have the same problem?
Darrell
Are you sure you don't have some global patch that is getting applied somewhere in the bowels of you build scripts? Even then, I can't see how that would cause the linking to fail without it blowing up your build. That is the strange part..
-
Darrell Anderson -
David C. Rankin