On 13 January 2017 at 13:02, Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 + moreinfo > > Am 13.01.2017 um 13:03 schrieb Helmut Grohne: >> Can we revert it in Debian or find some other solution? > > We don't have a decent explanation what's going on so I'm wary of > applying a workaround where nobody knows why it's needed.
Normally I would agree, but we are very near the freeze, so the time required to properly investigate the issue might well be longer than what is available to get to stretch, and thus stretch would release without being able to cross-build a core component to nios2 (and possibly other architectures). AFAIK, the fact that the real binary is in .libs/$program is an internal implementation detail of libtool and not a guaranteed interface, so it may well be possible (although unlikely) that different architectures differ in behavior. Given that the workaround in question lived for a relatively long time in unstable and caused no issues, I think the case for reverting is sound. This of course assumes that it is relevant to reach stretch with the cross-buildable component. If it is not, then I think investigating the root cause will be more fruitful. > This smells like a bug in libtool. Indeed. -- Saludos, Felipe Sateler
