From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 30 Aug 2018 02:41:12 -0500 (CDT) From: Per Oberg Message-ID: <958976130.615145.1535614872210.JavaMail.zimbra@wolfram.com> In-Reply-To: <1401452424.613986.1535613456917.JavaMail.zimbra@wolfram.com> References: <368012593.481146.1535555747324.JavaMail.zimbra@wolfram.com> <8992f6ad-6627-cb28-32f8-a3e890567e3a@xenomai.org> <1401452424.613986.1535613456917.JavaMail.zimbra@wolfram.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] Importance of missing modechk/cobolt.wrappers List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: xenomai Please visit us at: [ http://www.wolframmathcore.com/ | wolframmathcore.com= ] or [ http://www.wolfram.com/ | wolfram.com ] ----- Den 30 aug 2018, p=C3=A5 kl 9:17, Per =C3=96berg pero@wolfram.com skr= ev: > ----- Den 29 aug 2018, p=C3=A5 kl 18:01, Philippe Gerum rpm@xenomai.org s= krev: > > On 08/29/2018 05:15 PM, Per Oberg wrote: > > > Hello all > >> I'm working with a Yocto build of xenomai. I have compiled a sdk for b= uilding on > >> a build-host but I am doing something wrong because I get the wrong pa= th to > >> modechk.wrappers and cobalt.wrappers. I could probably fix this but I = just want > > > to know whether this is a real problem or not. > > > When I run xeno-config i get : > > > Xenomai: wrappers cannot be read from /usr/lib/modechk.wrappers > > > Xenomai: wrappers cannot be read from /usr/lib/cobalt.wrappers > >> The contents of the wrapper files are listed below for completeness. I= t seems > >> like a lot of stuff that is not getting wrapped when these files are m= issing, > >> and that would mean that I am missing a lot of wrapping and that I def= initely > > > need to fix it. Or is is just a warning? > > It's an important warning, your build may be broken. This means that > > wrapping failed for any executable depending on it, which retrieved its > > linker flags from xeno-config --ldflags. Basically, all built-in Xenoma= i > > apps (e.g. latency, switchtest), and any user application depending on > > xeno-config for retrieving those flags. > > > How do I know if the final software is wrapping stuff the way I want? > > Dumping the executable's namelist should always refer to the wrapper fo= r > > any routine listed in the wrapper files. e.g. > > $ nm -u $executable | grep 'U __wrap_' > > U __wrap_clock_gettime > > U __wrap_close > > U __wrap_fclose > > U __wrap_fprintf > > U __wrap_fputc > > U __wrap_fputs > > U __wrap_free > > U __wrap_fwrite > > U __wrap_ioctl > > U __wrap_kill > > U __wrap_malloc > > U __wrap_open > > U __wrap_printf > > U __wrap_pthread_attr_init > > U __wrap_pthread_create > > U __wrap_pthread_join > > U __wrap_pthread_setname_np > > U __wrap_puts > > U __wrap_read > > U __wrap_sem_close > > U __wrap_sem_open > > U __wrap_sem_post > > U __wrap_sem_unlink > > U __wrap_sem_wait > > U __wrap_time > > U __wrap_timerfd_create > > U __wrap_timerfd_settime > > U __wrap_write > > -- > > Philippe. > Thanks for that, I suspected this was the case. > I did do some checking on the built-in Xenomai apps and they are compiled= using > the right flags. This does not puzzle me because we are usually able to t= rust > the magic of the build system for solving this. (Meaning: Since there are= no > libraries, linker files, or other dependencies in the "prefix" directorie= s > during the first build the tools must all be referring to the build-dir i= nstead > of the prefix destination.) > In my case, since I'm building for a target with no build tools installed= (which > I assume would be quite normal for a lot of people doing real time stuff)= I > need to prepare some kind of SDK. For the X86 platform I can install Xeno= mai on > my laptop, and have the exact same setup on the target. But I rather not = have > it this way. Is there some kind of special flag I can use during build of= the > SDK or how do people generally go about this? I just found the DESTDIR environment variable, it was quite easily found in= the documentation. > Perhaps this is more of a Yocto-question or question of build-systems in = general > but I guess Xenomai-users should be quite good at setting these things up= . > Thanks > Per =C3=96berg Thanks Per =C3=96berg=20