From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9988 invoked by alias); 19 Sep 2003 20:36:51 -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 9971 invoked from network); 19 Sep 2003 20:36:51 -0000 Received: from unknown (HELO sunsite.ms.mff.cuni.cz) (195.113.19.66) by sources.redhat.com with SMTP; 19 Sep 2003 20:36:51 -0000 Received: from sunsite.ms.mff.cuni.cz (sunsite.mff.cuni.cz [127.0.0.1]) by sunsite.ms.mff.cuni.cz (8.12.8/8.12.8) with ESMTP id h8JIYm2c016113; Fri, 19 Sep 2003 20:34:48 +0200 Received: (from jakub@localhost) by sunsite.ms.mff.cuni.cz (8.12.8/8.12.8/Submit) id h8JIYmWv016111; Fri, 19 Sep 2003 20:34:48 +0200 Date: Fri, 19 Sep 2003 20:36:00 -0000 From: Jakub Jelinek To: Ulrich Drepper , Roland McGrath Cc: Glibc hackers Subject: [PATCH] Add static_link_warning to dlopen Message-ID: <20030919183448.GD12344@sunsite.ms.mff.cuni.cz> Reply-To: Jakub Jelinek Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-SW-Source: 2003-09/txt/msg00077.txt.bz2 Hi! Using dlopen in statically linked apps has the same problems as using NSS/iconv, so we should warn about it too. Well, there might be an exception if the statically linked program is dlopening libraries which are self-contained and don't need anything from glibc (e.g. by using callbacks into the statically linked program), but I guess it is so rare compared to the libs which actually need libc that it should be warned always. 2003-09-19 Jakub Jelinek * dlfcn/dlopen.c (dlopen): Add static_link_warning. --- libc/dlfcn/dlopen.c.jj 2001-07-06 00:54:45.000000000 -0400 +++ libc/dlfcn/dlopen.c 2003-09-19 16:08:44.000000000 -0400 @@ -54,3 +54,4 @@ __dlopen_check (const char *file, int mo } #include versioned_symbol (libdl, __dlopen_check, dlopen, GLIBC_2_1); +static_link_warning (dlopen) Jakub