From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe Gerum References: <7528e4df-ac06-8893-bf77-7cbf9e91eeef@xenomai.org> Message-ID: Date: Thu, 5 Apr 2018 15:09:58 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: [Xenomai] xeno-config --no-mode-check still has -lmodechk List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Giulio Moro , "xenomai@xenomai.org" On 04/05/2018 01:15 PM, Giulio Moro wrote: > so would it not be up to the external libs to specify in their docs that they should be linked with -lmodechk? You likely mean mentioning such dependency in their LDFLAGS as DSOs when linked, which is right. Over time, I received several reports from users of 3rd party libs which could not assume that unfortunately. So the question boils down to: should we break those builds to remove a generally useless dependency on libmodechk, or should we keep this dependency to please those users and maintain backward compat. Another question this raises is about calling __real_* symbols directly from the application code - which would be ok as a way to bypass the assertion checking in this case (likewise the other way around, referring to __wrap* calls). Not depending on libmodechk would invalidate such usage, ending up in undefined references. Open question AFAIC. -- Philippe.