Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer 
On miércoles, 11 de enero de 2017 10:35:37 ART Sam Hartman wrote:
[snip]
> that was to doko not you.

Usual me I'm afraid. I suscribed to the bug and forgot to see the To field.

> I'd be happy to chat, but you've articulated your position fairly well.
> If there's stuff not in the bug you'd like me to know about I'd be happy
> to set things up, but from the bug logs, your position seems fairly
> simple.
> Let's see if my summary is accurate:
> 
> * This bug is creating a number of ftbfses, particularly for
>   larger//more complex libraries on mips.
> 
> * You have a preferred minimal work-around you tried to upload
> 
> * Doko requested you not upload something until it was patched upstream.
> 
> * You want a solution sooner than that.
> 
> Is that approximately correct?

Almost, and at least it's good that this happened. I don't have any 
preferences between both proposed workarounds/patches, I simply took the 
easiest one and added code to limit it to mips*. As long as we fix this I have 
no real position on how we do it.

Thanks for your work!

-- 
http://www.tiraecol.net/modules/comic/comic.php?content_id=162

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Sam Hartman 
> "Lisandro" == Lisandro Damián Nicanor Pérez Meyer  
> writes:

Lisandro> On miércoles, 11 de enero de 2017 09:39:25 ART Sam Hartman wrote:
>> Hi.
>> 
>> As you are probably aware, the question of what to do about
>> linking on mips and stretch has been referred to the TC.  There's
>> a reasonable probability that we're going to want to move very
>> quickly on this issue, and I wanted to reach out to you and see
>> how we could best work with you to collect your input.
>> 
>> I'd be happy to set up an IRC discussion, to set up a phone call,
>> etc.  I think that might work better than an email discussion,
>> because the email discussion might involve a number of round
>> trips.  I'd be happy to work one-on-one and summarize
>> results/provide logs back to the entire TC, or to set up
>> something open to as many people as we can.  Also if there's a TC
>> member you'd rather work with than me, I'm sure we'd be happy to
>> facilitate this.
>> 
>> I'm hoping that you will be able to quickly work with us to
>> understand this issue and your position.

Lisandro> Hi Sam! I think an IRC discussion will be the best choice
Lisandro> here as my phone lines are really not reliable at all :-(

Lisandro> I'll be online from 17:30 UTC onwards, nick lisandro on
Lisandro> freenode.

that was to doko not you.
I'd be happy to chat, but you've articulated your position fairly well.
If there's stuff not in the bug you'd like me to know about I'd be happy
to set things up, but from the bug logs, your position seems fairly
simple.
Let's see if my summary is accurate:

* This bug is creating a number of ftbfses, particularly for
  larger//more complex libraries on mips.

* You have a preferred minimal work-around you tried to upload

* Doko requested you not upload something until it was patched upstream.

* You want a solution sooner than that.

Is that approximately correct?

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer 
On miércoles, 11 de enero de 2017 11:49:48 ART Lisandro Damián Nicanor Pérez 
Meyer wrote:
[snip] 
> I'll be online from 17:30 UTC onwards, nick lisandro on freenode.

And also oftc, of course.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer 
On miércoles, 11 de enero de 2017 09:39:25 ART Sam Hartman wrote:
> Hi.
> 
> As you are probably aware, the question of what to do about linking on
> mips and stretch has been referred to the TC.
> There's a reasonable probability that we're going to want to move very
> quickly on this issue, and I wanted to reach out to you and see how we
> could best work with you to collect your input.
> 
> I'd be happy to set up an IRC discussion, to set up a phone call, etc.
> I think that might work better than an email discussion, because the
> email discussion might involve a number of round trips.
> I'd be happy to work one-on-one and summarize results/provide logs back
> to the entire TC, or to set up something open to as many people as we
> can.
> Also if there's a TC member you'd rather work with than me, I'm sure
> we'd be happy to facilitate this.
> 
> I'm hoping that you will be able to quickly work with us to understand
> this issue and your position.

Hi Sam! I think an IRC discussion will be the best choice here as my phone 
lines are really not reliable at all :-(

I'll be online from 17:30 UTC onwards, nick lisandro on freenode.

I can ping you if I get to IRC sooner.

Kinds regards, Lisandro.

-- 
Why should I care about posterity?
What's posterity ever done for me?
  -- Groucho Marx

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Sam Hartman 


Hi.

As you are probably aware, the question of what to do about linking on
mips and stretch has been referred to the TC.
There's a reasonable probability that we're going to want to move very
quickly on this issue, and I wanted to reach out to you and see how we
could best work with you to collect your input.

I'd be happy to set up an IRC discussion, to set up a phone call, etc.
I think that might work better than an email discussion, because the
email discussion might involve a number of round trips.
I'd be happy to work one-on-one and summarize results/provide logs back
to the entire TC, or to set up something open to as many people as we
can.
Also if there's a TC member you'd rather work with than me, I'm sure
we'd be happy to facilitate this.

I'm hoping that you will be able to quickly work with us to understand
this issue and your position.

Thanks for your consideration,

--Sam