> Try these items in this order, doing a rebuilding test
> (including
> autogen.sh) after each item:
> 1. Remove all Makefile.in files from all folders in the
> libcarddav-0.6.2
> directory
> 2. Copy over your system's autoconf files:
> cp -Rp <path to your system's libool.m4 file>
> admin/libtool.m4.in
> cp -Rp <path to your system's ltmain.sh file>
> admin/ltmain.sh
> 3. I don't know?
There is no admin directory when I unpack the sources.
I created an admin directory and then copied the libtool files.
The make process failed with the following:
make: admin/Makefile.common: No such file or directory
make: *** No rule to make target `admin/Makefile.common'. Stop.
As there is no admin directory, there is no Makefile.common file.
Unsure, and not knowing exactly what is different with each package, I downloaded libcarddav_0.6.2-0debian3.tar.gz and libcarddav_0.6.2-0debian4.tar.gz.
Same results.
Log attached.
I discovered an annoying bug with /usr/bin/kde-config.
Because I am maintaining multiple KDE desktops in my testing, I am running a simple test to ensure I have the correct startkde script installed.
When I run the test in interactive mode (logged in) the test functions as expected. When I run the test in non-interactive mode, such as in an rc.local or rc.shutdown script, then kde-config misbehaves.
The annoying behavior is creating a .kde* home directory in the top level root directory. The bug is a carry-over from KDE because the same behavior occurs in 3.5.10. The only difference is that the 3.5.10 kde-config creates a /.kde directory while Trinity create /.kde3.
The directory gets get created there because in non-interactive mode the current working directory of a script usually is the top level.
To verify run this little snippet in an rc.local or rc.shutdown script:
/bin/ls -la /
sleep 2
/usr/bin/kde-config --help
/bin/ls -la /
sleep 2
Change the kde-config parameter to --version. Same results. You should see a /.kde3 directory get created.
Temporarily changing directories to /root in the test snippet does not help. Probably because kde-config sees no login name or ID. My only workaround at this point is to run my test snippet and then test for the existence of the new root directory.
The bug will affect anybody who runs kde-config in a script in non-interactive mode.
I believe kde-config is supposed to be informational and not pro-active. Hence, the tool should not presumptively be creating directories.
Darrell
I was browsing through KControl and later saw the following messages in the xsession-errors log:
Load smb config files from /dev/null
Loaded services file OK.
Server role: ROLE_STANDALONE
I think the messages should be prefixed with something like [kcontrol] so users know what was accessing the samba configuration files.
As a general guideline, I believe any stdout or stderr message Trinity generates in this manner should contain some clue about what generated the message. In these days of script kiddies and malicious users, a simple prefix like that will quiet fears.
Darrell
I noticed all but two of the modules in KInfo Center have been moved to KControl/Peripherals.
Is there a reason the remaining two modules, PCMCIA and Storage Devices, have not been moved to KControl?
If those two modules are moved, should KInfo Center be removed as an app?
Or should Kinfo Center then be a hook into KControl/Peripherals?
Darrell
There is a module in KControl, Internet & Network, called Zeroconf Service Discovery.
I built kdelibs and kdebase with --disable-dnssd.
Seems incorrect that the module appears.
If a build option is explicitly disabled then no modules should appear. Non-fatal, but I would call that a bug.
Darrell
Hello,
poking around trinity and got this message from tqtinterface configure script:
configure: WARNING: You are attempting to compile Trinity without the
Trinity Qt Interface installed. Please install libtqtinterface-dev
and try again!
Doesn't seems fatal, but should be fixed.
Regards Ladislav Laska
S pozdravem Ladislav Laska
---
xmpp/jabber: ladislav.laska(a)jabber.cz
Hello,
today, I wanted to checkout new svn snapshot and poke around, but I am
unable to remember the correct url for svn checkout. I searched a
little around websvn and stuff, but can't find it. I might be able to
guess it (and I probably will, since I've done it once already), but
other users won't. Maybe it should be somewhere more visible?
Regards Ladislav Laska
S pozdravem Ladislav Laska
---
xmpp/jabber: ladislav.laska(a)jabber.cz
I used the following in my build script:
=======================
python ./configure.py -k $PREFIX -L $LIBDIR -n $LIBDIR/kde3 -o /usr/include
make || exit 1
make install DESTDIR=$PKG
python importTest.py
=======================
Where $PREFIX and $LIBDIR are the same as all other build scripts.
The build stalls at the same point. I really don't know whether anything is happening, but I wait for about 10 minutes.
The configure.py script needs verbosity. There are long periods when the user does not know if anything is happening. For example, when creating the make files. Would be nice if something appeared on screen.
Darrell
FTBFS. Log attached.
We started to address this issue, but we kind of forgot to move forward with the other things going on.
I just built libcaldav so that package still builds.
SVN 1177573.
Darrell
