From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23562 invoked by alias); 11 Jun 2003 16:44:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23548 invoked from network); 11 Jun 2003 16:44:23 -0000 Received: from unknown (HELO cam-admin0.cambridge.arm.com) (193.131.176.54) by sources.redhat.com with SMTP; 11 Jun 2003 16:44:23 -0000 Received: from pc960.cambridge.arm.com (pc960.cambridge.arm.com [10.1.205.4]) by cam-admin0.cambridge.arm.com (8.9.3/8.9.3) with ESMTP id RAA24116; Wed, 11 Jun 2003 17:44:22 +0100 (BST) Received: from pc960.cambridge.arm.com (rearnsha@localhost) by pc960.cambridge.arm.com (8.11.6/8.9.3) with ESMTP id h5BGiLB13107; Wed, 11 Jun 2003 17:44:21 +0100 Message-Id: <200306111644.h5BGiLB13107@pc960.cambridge.arm.com> X-Authentication-Warning: pc960.cambridge.arm.com: rearnsha owned process doing -bs To: "Kris Warkentin" cc: "Gdb@Sources.Redhat.Com" , Richard.Earnshaw@arm.com Reply-To: Richard.Earnshaw@arm.com Organization: ARM Ltd. X-Telephone: +44 1223 400569 (direct+voicemail), +44 1223 400400 (switchbd) X-Fax: +44 1223 400410 X-Address: ARM Ltd., 110 Fulbourn Road, Cherry Hinton, Cambridge CB1 9NJ. X-Url: http://www.arm.com/ Subject: Re: Elf OS ABI Number In-reply-to: Your message of "Wed, 11 Jun 2003 10:00:21 EDT." <085f01c33021$cc60dd20$0202040a@catdog> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Jun 2003 16:44:00 -0000 From: Richard Earnshaw X-SW-Source: 2003-06/txt/msg00184.txt.bz2 > Does anyone know how to get one of these? I was rooting around on Caldera's > website but didn't see anything. I've realized that we need to have a > practical way to identify QNX binaries and this looks like the way to go. > A fairly common question, to which most times the answer is that you don't need one. You should only be using the OS ABI field if you are changing the meaning of the ELF specifics for a processor (new relocs, for example) which a linker not trained to recognise these would be unable to handle. It shouldn't be used to represent things that are encoded in the instructions inside sections (eg library calls specific to your OS, etc). The ELF specs seem to find it very hard to express this, but if you read it carefully, that is what they do say. R.