From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3518 invoked by alias); 24 Mar 2003 19:40:46 -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 3502 invoked from network); 24 Mar 2003 19:40:45 -0000 Received: from unknown (HELO Cantor.suse.de) (213.95.15.193) by sources.redhat.com with SMTP; 24 Mar 2003 19:40:45 -0000 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 4FC9A14C77; Mon, 24 Mar 2003 20:40:45 +0100 (MET) Received: from aj by arthur.inka.de with local (Exim 3.34 #1) id 18xXoK-0006aS-00; Mon, 24 Mar 2003 20:40:44 +0100 To: Ulrich Drepper Cc: GNU libc hacker Subject: Re: abilist problems From: Andreas Jaeger Date: Mon, 24 Mar 2003 19:46:00 -0000 In-Reply-To: <3E7F58D5.4020602@redhat.com> (Ulrich Drepper's message of "Mon, 24 Mar 2003 11:13:25 -0800") Message-ID: User-Agent: Gnus/5.090017 (Oort Gnus v0.17) XEmacs/21.4 (Artificial Intelligence, linux) References: <3E7F58D5.4020602@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-03/txt/msg00084.txt.bz2 Ulrich Drepper writes: > I have some big problems with the current abilist implementation. glibc > always allowed to compile against different kernel headers and have the > resulting binary reflect the kernel the headers are taken from. This > can cut down on runtime tests for functionality which is known to not be > available since an old kernel is used. And there's the problem with the _nl_dirname (sp?) symbol which has a different length depending on the value of --prefix. We need to find a way to take this into account without the testsuite failing. > The abilist check causes all such builds to fail. Syscalls which are > listed only in syscalls.list and are not available in the kernel headers > will have no code created for them. This in turn obviously results in > differences to the interface. > > I see two ways out: > > - make the abilist check optional and/or figure out how to determine > when the tests can be made mandatory. E.g., if the kernel header > version is more recent than x.y.z, make the tests mandatory. > > - create stubs for the syscalls which are not announced in the kernel > headers. > > > I probably have a preference for the second solution. Any volunteer to > hack something? Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj