>> You mean something like the attached patch?
>>
>...added missing definition TDEICONLOADER_DEBUG in config.h.cmake
Um, yes, I think so. I presumed something similar was needed but I
wanted one of the experts to say as much. :-)
* Are you going to push the patch?
* How do we test the binaries compiled correctly when
WITH_TDEICONLOADER_DEBUG=true? Backtraces?
* Is this an option normally left as false and changed to true only
when a developer asks for that change to help debug related
problems?
Darrell
HI there,
is anybody aware of any good reason why tdelibs14-trinity and some other packages have a very strict dependency on binutils in Debian Jessie and Wheezy (and I suspect also on previous versions and in Ubuntu, even though I didn't check)?
For example I get dependencies such as:
binutils (>= 2.23.52.20130828), binutils (<< 2.23.52.20130829).
The problem with such kind of dependency is that when binutils is updated, I need to do a full rebuild of TDE before I can update the binutils package on my machine.
After the full rebuild is completed, everything can be updated, but I don't see the reason for having the '<<' part of the dependency since it doesn't seem to affect anything: TDE builds with both the old and the new binutils package.
So I am wondering if such strict dependency is intentional or if it is something that we are dragging along from the past (perhaps because of a broken or incompatible binutils version in the past).
If there isn't any particular reason, I will open a bug report in a few days about this point.
Thanks
Michele
Tim,
Commit cced03e1 2013-10-17 disabled the constant generation of
backtraces in TDEIconLoader. The patch inidcates that
KICONLOADER_CHECKS must now be explicitly defined. I presume the
only people who want to do that are folks wanting to troubleshoot
related problems.
Should the need arise, where is the appropriate place to define
KICONLOADER_CHECKS?
Darrell
