So, I've added this information to my bug report...
J-L
2016-11-09 10:07 GMT+01:00 Pascal Obry :
>
> Jean-Luc,
>
> > Unfortunately there was a new upgrade of binutils today on debian
> > sid.
> >
> > It is from 2.51.20161105-2 -> 2.51.20161108-1
> >
> > And... the bug is here again.
>
> Confirme
Jean-Luc,
> Unfortunately there was a new upgrade of binutils today on debian
> sid.
>
> It is from 2.51.20161105-2 -> 2.51.20161108-1
>
> And... the bug is here again.
Confirmed :( As you said it is sid so nothing to complaint about!
--
Pascal Obry / Magny Les Hameaux (78)
The best w
Hi,
Unfortunately there was a new upgrade of binutils today on debian sid.
It is from 2.51.20161105-2 -> 2.51.20161108-1
And... the bug is here again.
It seems that upsteam developpers are not aware of it. The changelog shows
that there was a revert to fixe a problem then (today) upgrading to a
Jean-Luc,
> There is a new version of binutils this morning (morning for me) on
> debian sid : 2.27.51.20161105-2 .
> This version fixes the ld problem for me.
Confirmed. Just an ld bug after all. Thanks.
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imag
Bonjour Pascal, hi everybody,
There is a new version of binutils this morning (morning for me) on debian
sid : 2.27.51.20161105-2 .
This version fixes the ld problem for me.
Regards
Jean-Luc
2016-11-05 22:21 GMT+01:00 Pascal Obry :
>
> Thanks Tobias and Jean-Luc, I'm not alone :)
>
> Good to
Thanks Tobias and Jean-Luc, I'm not alone :)
Good to see a bug report opened.
Cheers,
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
___
Hi,
I got the same on debian/sid with the update of binutils package from
2.27-9+b1 to 2.27.51.20161102-1.
I've opened a bug (#843164) for that.
Reverting to 2.27-9 probably needs also to revert gcc/cpp/g++ and Co as
well.
Regards
Jean-Luc
___
Am Samstag, 5. November 2016, 12:32:41 CET schrieb Pascal Obry:
> My build crash ld and here is the strange story. I'm always building
> stuff using script away from my repository and that's always been fine
> with darktable until recently.
>
> I just found out that when building into the "build"