From owner-freebsd-mips@FreeBSD.ORG Sat Apr 7 08:21:26 2012 Return-Path: Delivered-To: mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EA691065670; Sat, 7 Apr 2012 08:21:26 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 882718FC0C; Sat, 7 Apr 2012 08:21:25 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1030749wgb.1 for ; Sat, 07 Apr 2012 01:21:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Bnyf3+mhF0q4M573sJ+I+XF8+NH1RAby+NwOrJqULyQ=; b=rV/FPgqBo1G3FBogDDGrm12Bv7f9v64LSPyQPeyr6/2xD+xHrm3qNE+JOmNrWj1WLp p1broU3tGjxrahFFGqAXwurUIdtZUvbCL3vmgymNFxD58y8a8DS3PqcLMP8sB5GovGVs 7akKtrXeUXyFzJlW+aLvgcbjdP2vey94nCjL6VtOZv9SW4UvZpFZ7SlC8yYcL6l019w6 MgzMmAcHCAiLeUhzUEHYGUXtKO69mVauCx7+J4AxgiwMXyqDITRTI5T4fgBkZY/W6tDC KJBg/8seLpOfSu+J0oG9IlZ3nPho+dhfhSWbGUzkELMyqPnaT6X7HXqBRo7GzTlbllsI 0f/Q== MIME-Version: 1.0 Received: by 10.180.83.198 with SMTP id s6mr1790887wiy.8.1333786884468; Sat, 07 Apr 2012 01:21:24 -0700 (PDT) Received: by 10.216.62.81 with HTTP; Sat, 7 Apr 2012 01:21:24 -0700 (PDT) In-Reply-To: <20120407005801.204e52db.stas@FreeBSD.org> References: <20120405142423.90d48b27.stas@FreeBSD.org> <036C5A57-2B63-40C1-A0DA-0678B7BF29F8@freebsd.org> <20120406135447.6ca86bd9.stas@FreeBSD.org> <20120407005801.204e52db.stas@FreeBSD.org> Date: Sat, 7 Apr 2012 13:51:24 +0530 Message-ID: From: "Jayachandran C." To: Stanislav Sedov Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mips@freebsd.org Subject: Re: There is a known problem with MIPS tinderbox. X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 08:21:26 -0000 On Sat, Apr 7, 2012 at 1:28 PM, Stanislav Sedov wrote: > On Sat, 7 Apr 2012 11:40:43 +0530 > "Jayachandran C." mentioned: > >> I would still suggest the asn1 change if we are doing a temporary fix, b= ecause: >> - It does not add any new symbol versioning, it just converts the >> 'global: *' to an explicit list of symbols. >> - there are other libraries lined to asn1 which may have the same >> issue as libkafs5 (I haven't really looked at this. > > On one hand, it seems that the issue is triggered only when you > link versioned library against non-versioned, and all other > kerberos libraries that use libasn1 are versioned. =A0On the other, > you're right and if we don't fix libasn1 anything else linking > agains it (e.g. something from ports) might trigger the bug. > >> The only downside I see is that libasn1 has a lot of symbols. > > Yep, that was my concern. :-( =A0But I think you're right and we > should go with the edited libasn1 map. =A0I noticed that you > added some internal symbols to the map, though (.e.g. _init > and _fini). =A0What do you think if we take them out? You are right, we should probably take out _init and _fini, > There're some other symbols as well which no libraries seem > to use. I haven't really gone thru the symbols, this is a dump of 'nm -D' of libasn1 with a few obvious ones taken out. I do not have any background on this component, that is why I did not want to take a stab at cutting down the symbols or testing the resultant binaries. If the workaround works fine in your testing, you are welcome to check in after removing symbols you feel can be taken out. Thanks, JC.