[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: KDE 2.x and lt_dlopen_flag
From: |
Alexandre Oliva |
Subject: |
Re: KDE 2.x and lt_dlopen_flag |
Date: |
05 Jun 2001 21:12:52 -0300 |
User-agent: |
Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.4 (Academic Rigor) |
On Jun 4, 2001, Nick Hudson <address@hidden> wrote:
> - libltdl_la_LDFLAGS = -no-undefined -version-info 3:0:0
> + libltdl_la_LDFLAGS = -no-undefined -version-info 3:1:0
This is wrong. Since they have added an interface, CURRENT and AGE
should have been incremented, and REVISION left as zero.
> ! lt_module module = dlopen (filename, LT_GLOBAL | LT_LAZY_OR_NOW);
> if (!module)
> {
> --- 575,588 ----
> # define DLERROR(arg) LT_DLSTRERROR (arg)
> #endif
> + int lt_dlopen_flag = LT_LAZY_OR_NOW;
> +
> static lt_module
> sys_dl_open (loader_data, filename)
> lt_user_data loader_data;
> const char *filename;
> {
> ! lt_module module = dlopen (filename, lt_dlopen_flag);
> if (!module)
> {
Do they realize that this change removed LT_GLOBAL from the default
lt_dlopen_flag setting?
I can't say I like this approach. Tweaking lt_dlopen_flag is not
guaranteed to have any effect on the outcome of a lt_dlopen, since
there's no guarantee that dlopen() is going to be used.
To me, tweaking the dlopen() flags is entering non-portable zone and,
since you're doing that, why not use dlopen() directly?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer address@hidden, redhat.com}
CS PhD student at IC-Unicamp address@hidden, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me