From owner-freebsd-arm@FreeBSD.ORG  Tue Oct  7 20:09:10 2014
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E07FF25D
 for <freebsd-arm@freebsd.org>; Tue,  7 Oct 2014 20:09:10 +0000 (UTC)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com
 [IPv6:2607:f8b0:4001:c05::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B004C8FF
 for <freebsd-arm@freebsd.org>; Tue,  7 Oct 2014 20:09:10 +0000 (UTC)
Received: by mail-ig0-f173.google.com with SMTP id h18so4920897igc.6
 for <freebsd-arm@freebsd.org>; Tue, 07 Oct 2014 13:09:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:from:date:message-id
 :subject:to:cc:content-type;
 bh=RiwI5CDseZ4grjZV+h4Axhj/9LFoTTcCJJDVOlmv0yc=;
 b=nfhkLDCtQppYm/cyJPhTpFXLI0TdZDiV+xttrg3NiHlnby9lV5fecEBrEy8v7khvJs
 8/tcfkllrZGThJoQLtCoCSD0LmypLtUH8QyxbkxYOtFLm2RmCN+sqvamsRL+7JM9zXE2
 7JivBVRKkbJTDLFYD08QPjXB6f+TUga6von04sGXczxHkD8dxI0k9QhXJ6qLhzXUyRYS
 qFfMSrfT4gVjMz8zFYiySMMdRHia6LjgPFjUp4czQHXs9oDtwu2gEPBtK2oaUXhU8Zf5
 dA2Ky0doWMsgySjEdnNg38kXB2/ekZvLTKHQvXFJrvikwPEIwsRu0cqnpQz9zvt/iSmn
 k/5w==
X-Received: by 10.43.68.206 with SMTP id xz14mr4579588icb.33.1412712550180;
 Tue, 07 Oct 2014 13:09:10 -0700 (PDT)
MIME-Version: 1.0
Sender: carpeddiem@gmail.com
Received: by 10.107.29.132 with HTTP; Tue, 7 Oct 2014 13:08:50 -0700 (PDT)
In-Reply-To: <20141007163440.02a402f8@bender.lan>
References: <op.xnc7szg9kndu52@ronaldradial.radialsg.local>
 <20141007163440.02a402f8@bender.lan>
From: Ed Maste <emaste@freebsd.org>
Date: Tue, 7 Oct 2014 16:08:50 -0400
X-Google-Sender-Auth: Z8RKM-JMIUqN-H0_y9oVcupDO0Q
Message-ID: <CAPyFy2CSAp=TYCzMTy1yz0fqrJzfRjq7+=qPobSoeJkUPrk0SA@mail.gmail.com>
Subject: Re: Why are arm libs branded as SYSV?
To: Andrew Turner <andrew@fubar.geek.nz>
Content-Type: text/plain; charset=UTF-8
Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Oct 2014 20:09:11 -0000

On 7 October 2014 11:34, Andrew Turner <andrew@fubar.geek.nz> wrote:
>> On my ARM Sheevaplug:
>> # file /usr/local/lib/libpcre.so.3
>> /usr/local/lib/libpcre.so.3: ELF 32-bit LSB shared object, ARM,
>> EABI5 version 1 (SYSV), dynamically linked, stripped
>> ...
>
> Because the EI_OSABI field, where this value comes from, is documented
> to be zero in the ARM AAELF spec.

It's somewhat confusing for file to report SYSV, since both
ELFOSABI_SYSV and ELFOSABI_NONE are 0.  It could perhaps output
"SYSV/NONE", although I'm not sure that would be less confusing.

I looked for references to EI_OSABI in the source tree.  Aside from
ldd the only tool I found that might need a change is gcore, which
sets the field to ELFOSABI_FREEBSD in generated core files.  I'm not
sure that this will actually cause trouble in practice though.