From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30831 invoked by alias); 10 Feb 2005 16:51:31 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 30799 invoked from network); 10 Feb 2005 16:51:28 -0000 Received: from unknown (HELO are.twiddle.net) (64.81.246.98) by sourceware.org with SMTP; 10 Feb 2005 16:51:28 -0000 Received: from are.twiddle.net (localhost.localdomain [127.0.0.1]) by are.twiddle.net (8.12.11/8.12.11) with ESMTP id j1AGoWhU006453; Thu, 10 Feb 2005 08:50:33 -0800 Received: (from rth@localhost) by are.twiddle.net (8.12.11/8.12.11/Submit) id j1AGnfgP006449; Thu, 10 Feb 2005 08:49:41 -0800 X-Authentication-Warning: are.twiddle.net: rth set sender to rth@twiddle.net using -f Date: Thu, 10 Feb 2005 16:51:00 -0000 From: Richard Henderson To: Roland McGrath Cc: libc-hacker@sources.redhat.com Subject: Re: FR-V PLT audit Message-ID: <20050210164941.GA6437@twiddle.net> Mail-Followup-To: Roland McGrath , libc-hacker@sources.redhat.com References: <20050210075139.GD4296@twiddle.net> <200502100903.j1A93Mos031618@magilla.sf.frob.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502100903.j1A93Mos031618@magilla.sf.frob.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2005-02/txt/msg00044.txt.bz2 On Thu, Feb 10, 2005 at 01:03:22AM -0800, Roland McGrath wrote: > That's not the concern. The concern is that one could try to compile an > audit library on a different platform and have it seem like it's ok because > the signature happens to match, but in fact the audit library's > pltenter/pltexit functions have not been ported properly to the machine you > are compiling for. Since those implementations are always > machine-specific, having the API distinguish the machine in the names makes > sure you have considered the target machine specifically. Given that any non-trivial audit library will be looking at the arguments, and the structure member names are different for each platform, what do you think the odds are that the library will compile when configured incorrectly? I'm thinking pretty low, myself. r~