From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27641 invoked by alias); 7 Jun 2018 13:38:53 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 24822 invoked by uid 89); 7 Jun 2018 13:38:51 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=UD:6, UD:so.6, burden X-HELO: mx1.redhat.com Subject: Re: [PATCH] Introduce --enable-math-noprivate From: Florian Weimer To: libc-alpha@sourceware.org References: <20180511154314.83126424B00CE@oldenburg.str.redhat.com> Message-ID: <81a58bc9-7069-3b9f-6b70-bd68d626990b@redhat.com> Date: Thu, 07 Jun 2018 13:38:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2018-06/txt/msg00142.txt.bz2 On 05/16/2018 06:54 AM, Florian Weimer wrote: > On 05/11/2018 05:43 PM, Florian Weimer wrote: >> Avoid errno@GLIBC_PRIVATE if enabled.  Additional work is needed >> to eliminate further GLIBC_PRIVATE symbol references. >> >> 2018-05-11  Florian Weimer >> >>     Introduce --enable-math-noprivate. >>     Avoid errno@GLIBC_PRIVATE if enabled. >>     * config.h.in (CONFIG_MATH_NOPRIVATE): Define. >>     * config.make.in (config-math-noprivate): New variable. >>     * configure.ac: Recognize --enable-math-noprivate option. >>     * manual/install.texi (Configuring and compiling): Document >>     --enable-math-noprivate. >>     * configure: Regenerate. >>     * INSTALL: Likewise. >>     * include/errno.h: Do not redefine errno for libm, libmvec if >>     CONFIG_MATH_NOPRIVATE. > > Ping.  These patches > > > > > allow building libm.so.6 without GLIBC_PRIVATE references on aarch64, > and on x86-64 if --disable-multi-arch is also specified (I have a patch > to add multi-arch support for the latter, but I need to come up with > something that reduces the maintenance burden). Ping? What's the general feeling regarding this feature? Thanks, Florian