Hi,
> FWIW amid the reports merged with this one, there is one person using
> i386 and another using mipsel.
I don't know for i386 and mipsel, but here are my investigations for ia64.
> From the point of view of fixing this in binutils, it would be _very_
> helpful to have a collection of object files and e.g. two linker
> command lines that should produce the same binary but do not. At the
> moment, a person investigating this has to get to know the
> gnome-settings-daemon build system and it is hard to debug or pass
> upstream. Alternatively, if this is a regression than a regression
> range would be helpful.
gnome-settings-daemon first appears (at least on ia64) in Debian 5.0 "Lenny".
So I started with a fresh Lenny install on a spare HDD.
>From there, the older binutils package that I can install without
breaking the whole system is binutils_2.17cvs20070426-1_ia64.
Guess what? This old version already produces a broken
gnome-settings-daemon with -z flag passed to the linker, and a working
one without the flag :-(
For further debugging, I can thus provide the locally rebuilt (with
binutils_2.17cvs20070426-1_ia64)
gnome-settings-daemon_2.22.2.1-2_ia64.deb binary packages with and
without -z flag passed to linker. I've also kept the build directories
of these two packages if preferred.
As an alternative, I can also provide these packages but from a
daily-updated Debian Testing "Wheezy" install, with up-to-date
binutils and gnome-settings-daemon packages if preferred.
About the gnome-settings-daemon build system, maybe Josselin can give
us a clue? I have no idea how it works.
Best regards,
Émeric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
