From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4E3195FB.4040701@domain.hid> Date: Thu, 28 Jul 2011 19:01:47 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4E299162.8000309@domain.hid> <4E305DAB.80402@domain.hid> <4E3194A5.5040709@domain.hid> In-Reply-To: <4E3194A5.5040709@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] __wrap_clock_gettime List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai core On 2011-07-28 18:56, Jan Kiszka wrote: > On 2011-07-27 20:49, Gilles Chanteperdrix wrote: >> On 07/22/2011 05:04 PM, Jan Kiszka wrote: >>> Hi Gilles, >>> >>> pulling assert_context.c into the common libxenomai created a problem >>> around picking the right __wrap_clock_gettime. As libpthread_rt depends >>> on libxenomai, the latter is loaded first and defines the debug version >>> of __wrap_clock_gettime as the default. There is no chance to pull the >>> posix skin implementation. >>> >>> I don't have a nice idea yes how to resolve this. Options are: >>> - drop __wrap_clock_gettime from assert_context.c (affects any skin >>> user != posix) >>> - put assert_context stuff into separate library again >>> - put __wrap_clock_gettime in all skin libs != posix >>> >>> I'm favoring the simplest approach ATM, ie. the first one. Other ideas? >> >> I agree, but I would have thought __attriibute__((weak)) takes care of >> this issue. > > The point is that once you have pulled in that weak symbol into a > process, the dynamic loader won't update it if a non-weak version is > pulled in via dlopen. Mmh, maybe we have a fourth option: disabling the weak version if CONFIG_XENO_LIBS_DLOPEN is set. OTOH, the correlation may not be obvious to users. So that result could be even more confusing. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux