On 3/22/16 9:48 PM, Matthew Gabeler-Lee wrote: > On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli > <[email protected]> wrote: >> Please give a look to >> >> https://sourceware.org/ml/libc-help/2016-03/msg00010.html >> >> to me it seems that the real problem is in glibc. > > From reading that thread and looking at the referenced git commit, I'm > not convinced it's a glibc bug. While I'm definitely not an expert in > this area, it looks to me like glibc removed some legacy cruft that > should no longer have been needed by any app that used the correct > compile/link flags for pthreads. They also added a workaround for a > common case of incorrect flags.
I haven't been able to chase these glibc details down. Do you have pointers to specifics for this? > But what we have here is an uncommon case driven by mosh's linker > options, which means that the glibc workaround for protobuf's incorrect > linker options doesn't (can't?) work. I agree that this issue seems to be provoked by a *change* in glibc, but not a *bug*-- I believe the bug is protobuf's bad linker options. All this stuff is ill-documented though. > If protobuf didn't recommend incorrect linker options, we wouldn't have > this problem. Seems thus this bug should be moved to the protobuf > package and the upstream patch applied? That seems reasonable to me. > Having mosh conflict with the broken protobuf versions would be handy > too, but may not be necessary? I think it's not necessary; I think we'll have to fix this in packaging for mosh-1.2.5 on unstable, and in the upstream for mosh master. We're working on #1 now. I just pushed the fix for #2. regards, --jh
