This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PATCH] Add static_link_warning to dlopen

From: Jakub Jelinek <jakub at redhat dot com>
To: Ulrich Drepper <drepper at redhat dot com>, Roland McGrath <roland at redhat dot com>
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>
Date: Fri, 19 Sep 2003 20:34:48 +0200
Subject: [PATCH] Add static_link_warning to dlopen
Reply-to: Jakub Jelinek <jakub at redhat dot com>

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  <jakub@redhat.com>

	* 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 <shlib-compat.h>
 versioned_symbol (libdl, __dlopen_check, dlopen, GLIBC_2_1);
+static_link_warning (dlopen)

	Jakub

Follow-Ups:
- Re: [PATCH] Add static_link_warning to dlopen
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]