Raw-ethernet rteth0 does work. See the output: # /usr/examples/xenomai/posix/raw-ethernet eth0 cannot get interface index: No such device # /usr/examples/xenomai/posix/raw-ethernet rteth0 Sent frame of 1514 bytes Sent frame of 1514 bytes Sent frame of 1514 bytes Sent frame of 1514 bytes shutting down
So should I compare the invoked gcc command line with the output of "xeno-config --skin=posix --ldflags"? Can that be possible if "raw-ethernet" is working? Daniel Am Fr., 7. Juni 2019 um 12:15 Uhr schrieb Jan Kiszka <jan.kis...@siemens.com >: > On 07.06.19 11:40, danwe wrote: > > I have checked what the generated binary is using. > > E.g. it is using lines like: > > > > 19: 00008bc8 0 FUNC GLOBAL DEFAULT UND ioct1@GLIBC_2.4 (3) > > 45: 00008cc4 0 FUNC GLOBAL DEFAULT UND socket@GLIBC_2.4 (3) > > > > Does that mean that it is using the non-rt glibc services? If so then I > do not > > understand one thing: the file "raw-ethernet" is a example where it uses > the > > same ioct1@GLIBC and socket@GLIBC but it does not throw the "network is > > unreachable error". > > But how can I change that it is using the __wrap_socket? > > Compare the invoked gcc command line with the output of "xeno-config > --skin=posix --ldflags". Something is preventing the the required flags > make it > into your build. Also try building manually, to exclude flaws in your > buildroot > environment. > > Does "raw-ethernet rteth0" actually work? Or are you calling "raw-ethernet > eth0" > by accident? > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux >
