From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4B742963.5010301@domain.hid> Date: Thu, 11 Feb 2010 16:59:31 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4B72A7E2.5020001@domain.hid> <4B72A9DA.1090104@domain.hid> <4B730A04.9040908@domain.hid> <4B731608.6010803@domain.hid> <4B73180C.6070301@domain.hid> <4B73207C.6020400@domain.hid> <4B73218A.9080306@domain.hid> <4B7323D5.1040804@domain.hid> <4B732487.50103@domain.hid> <4B732679.4030306@domain.hid> <4B73278F.9050603@domain.hid> <4B73C214.3010107@domain.hid> <4B73C421.1020200@domain.hid> <4B73CFD9.6010904@domain.hid> <4B73D202.5050004@domain.hid> <4B73DDC9.2020906@domain.hid> <4B73E421.3050708@domain.hid> <4B7410BB.5010809@domain.hid> In-Reply-To: <4B7410BB.5010809@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : Make xnarch_init_timeconv an uninlined weak function List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Xenomai core Jan Kiszka wrote: > And instantly - you forget about dlopen scenarios which triggered the > bug in timeconv. I do not see why dlopen would trigger a bug. Could you explain it? -- Gilles.