2012/4/7 Stanislav Sedov :
> On Fri, 6 Apr 2012 13:08:12 +0530
> "Jayachandran C." mentioned:
>
>> On Fri, Apr 6, 2012 at 12:01 PM, Stanislav Sedov wrote:
>> >
>> > On Apr 5, 2012, at 11:08 PM, Jayachandran C. wrote:
>> >>
>> >>
>> >> The asn1 library has a export map containing 'global: *', this
On Fri, 6 Apr 2012 13:08:12 +0530
"Jayachandran C." mentioned:
> On Fri, Apr 6, 2012 at 12:01 PM, Stanislav Sedov wrote:
> >
> > On Apr 5, 2012, at 11:08 PM, Jayachandran C. wrote:
> >>
> >>
> >> The asn1 library has a export map containing 'global: *', this exports
> >> two symbols _fdata and _
On Fri, Apr 6, 2012 at 12:01 PM, Stanislav Sedov wrote:
>
> On Apr 5, 2012, at 11:08 PM, Jayachandran C. wrote:
>>
>>
>> The asn1 library has a export map containing 'global: *', this exports
>> two symbols _fdata and _ftext versioned. When libkafs5 is linked,
>> these symbols confuse the bfd cod
On Apr 5, 2012, at 11:08 PM, Jayachandran C. wrote:
>
>
> The asn1 library has a export map containing 'global: *', this exports
> two symbols _fdata and _ftext versioned. When libkafs5 is linked,
> these symbols confuse the bfd code and the entries corresponding to
> theses (index 13, and 16)
On Fri, Apr 6, 2012 at 2:54 AM, Stanislav Sedov wrote:
> On Thu, 5 Apr 2012 12:39:00 -0700
> Juli Mallett mentioned:
>
>> On Thu, Apr 5, 2012 at 12:28, Doug Barton wrote:
>> > But as always, if someone comes up with an actual problem related to the
>> > [BIND] update I'm happy to address it.
>>
Stanislav Sedov writes:
> What I still cannot understand is that why my workaround doesn't work
> on tinderbox and for some people builds. It should disable linking
> agains libasn1 for libkafs5 completely on mips which is the source of
> the problem in libkafs5.
The complete build log is here:
On Thu, 5 Apr 2012 12:39:00 -0700
Juli Mallett mentioned:
> On Thu, Apr 5, 2012 at 12:28, Doug Barton wrote:
> > But as always, if someone comes up with an actual problem related to the
> > [BIND] update I'm happy to address it.
>
> The MIPS tinderbox build is currently broken. This is related
On 4/5/2012 12:39 PM, Juli Mallett wrote:
> You have not broken the MIPS tinderbox. It has been broken for a
> couple of weeks now, and is a known problem, and hopefully will be
> fixed soon.
*phew* Thanks for letting me know. :)
Doug
___
freebsd-curre
On Thu, Apr 5, 2012 at 12:28, Doug Barton wrote:
> But as always, if someone comes up with an actual problem related to the
> [BIND] update I'm happy to address it.
The MIPS tinderbox build is currently broken. This is related to a
binutils bug for which a workaround was committed to head. For
