RE: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Ángel González <keisial@xxxxxxxxx>
Subject: RE: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
From: David Aldrich <David.Aldrich@xxxxxxxxxxxx>
Date: Mon, 13 May 2013 14:05:04 +0000
Cc: "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx>
In-reply-to: <5190E767.2030205@gmail.com>

Hi Ángel

> Is it possible that when loading libB, libD got loaded as a dependency?

Thanks for your suggestion but we believe that libB does not require libD.

David

References:
- Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
  - From: David Aldrich
- Re: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
  - From: Ángel González

Prev by Date: Re: Ongoing Error in make stage2 building gcc-4.7.2
Next by Date: RE: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
Previous by thread: Re: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
Next by thread: Re: Has dlopen() behaviour changed between gcc4.1 and gcc 4.4?
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux