Comment # 10 on bug 1141188 from Martin Li��ka

(In reply to J��rg Schiling from comment #9)
> As mentioned for bug https://bugzilla.suse.com/show_bug.cgi?id=1141105
> already, the important issue is that both bug reports miss the needed
> information on what non-standard build procedure has been used to compile
> the failing binary.

Ok, the build procedure is to add -flto to C{,XX}FLAGS.

> 
> There has not been any report about a similar problem when the unmodified
> schily build system is in use on Linux.
> 
> This is a proof that there is no problem in my software and as long as you
> do not document how you caused that problem, there is no way to help you.
> 
> The problem may have been caused by using an unusual compiler or by
> enforcing unusual linker flags when compiling/linking the binary. 

Yes, LTO is a cutting edge technology but has been thoroughly tested and used
by the various projects during the last couple of years.

> 
> BTW: This is linker bug with the linker used on the target platform and the
> best way to deal with this bug report is to forward it to a person with
> skill for the related link sub system.

Yes, that's possible, but without a small test-case reproducer nobody will help
us.