Hi Alan, I did. This way I could compile and run my code on Nuttx but I now get "Socketpair creation error" from my program. As far as I know socketpair fucnction was includded in Nuttx 10.1 but I can't see its reference in the latest Network documentation here: https://nuttx.apache.org/docs/latest/reference/user/11_network.html Anyway, I got some progress.
On 2021/07/04 16:43:05, Alan Carvalho de Assis <[email protected]> wrote: > Hi Murat, > > Just use the netnsh config and follow my video tutorial explaining how to > use USB Console. > > It is easy when you know which options to look at on menuconfig. It is > important to get used to menuconfig, otherwise it always will be like a > maze. > > BR, > > Alan > > On Sunday, July 4, 2021, murat tologlu <[email protected]> wrote: > > > I wish there was an easier way to configure the Nuttx; it is really hard! > > > > The application I wrote with the :netnsh configuration was compiled > > without any problems. However I want to use /dev/ttyUSBx as >nsh console. > > I'm trying to compare nsh and netnsh .config files to do something, but > > it's really complicated. > > > > How can I go further .. :( > > > > On 2021/07/03 19:18:47, murat tologlu <[email protected]> wrote: > > > Hi Alan, > > > > > > Good advise the previous problem resolved after enabling the network but > > now I get : > > > > > > ... > > > netlib_setifstatus.c: In function 'netlib_ifup': > > > netlib_setifstatus.c:67:27: error: 'NETLIB_SOCK_TYPE' undeclared (first > > use in this function); did you mean 'NETLIB_SOCK_FAMILY'? > > > 67 | NETLIB_SOCK_TYPE, > > NETLIB_SOCK_PROTOCOL); > > > | ^~~~~~~~~~~~~~~~ > > > | NETLIB_SOCK_FAMILY > > > netlib_setifstatus.c:67:27: note: each undeclared identifier is reported > > only once for each function it appears in > > > netlib_setifstatus.c: In function 'netlib_ifdown': > > > netlib_setifstatus.c:111:27: error: 'NETLIB_SOCK_TYPE' undeclared (first > > use in this function); did you mean 'NETLIB_SOCK_FAMILY'? > > > 111 | NETLIB_SOCK_TYPE, > > NETLIB_SOCK_PROTOCOL); > > > | ^~~~~~~~~~~~~~~~ > > > | NETLIB_SOCK_FAMILY > > > /home/murat/nuttxspace/apps/Application.mk:134: recipe for target > > 'netlib_setifstatus.home.murat.nuttxspace.apps.netutils.netlib.o' failed > > > make[3]: *** > > > [netlib_setifstatus.home.murat.nuttxspace.apps.netutils.netlib.o] > > Error 1 > > > make[3]: Leaving directory '/home/murat/nuttxspace/apps/netutils/netlib' > > > Makefile:42: recipe for target > > > '/home/murat/nuttxspace/apps/netutils/netlib_all' > > failed > > > make[2]: *** [/home/murat/nuttxspace/apps/netutils/netlib_all] Error 2 > > > make[2]: Leaving directory '/home/murat/nuttxspace/apps' > > > Makefile:35: recipe for target 'all' failed > > > make[1]: *** [all] Error 2 > > > make[1]: Leaving directory '/home/murat/nuttxspace/apps' > > > tools/LibTargets.mk:210: recipe for target > > > '/home/murat/nuttxspace/apps/libapps.a' > > failed > > > make: *** [/home/murat/nuttxspace/apps/libapps.a] Error 2 > > > > > > > > > On 2021/07/03 10:45:40, Alan Carvalho de Assis <[email protected]> > > wrote: > > > > Hi Murat, > > > > > > > > Did you enable Network support in the menuconfig? > > > > > > > > Normally when some function is not found it means some feature in the > > > > menuconfig is not enabled. > > > > > > > > BR, > > > > > > > > Alan > > > > > > > > On 7/3/21, murat tologlu <[email protected]> wrote: > > > > > Hi, > > > > > > > > > > I am doing experiments of porting standard posix applications to > > Nuttx, I > > > > > try to run same applications on both Ubuntu and Nuttx. In one > > application I > > > > > needed to use socket.h, I did "#include <sys/socket.h>" in my c file > > but it > > > > > seems that the linker doesn't find the library, I get "undefined > > reference > > > > > to `socketpair' 'send' 'recv' errors while all of them clearly > > defined in > > > > > sys/socket.h ! > > > > > > > > > > Of-course I can modify the c file, Makefile, I can move or copy > > library > > > > > files to appropriate locations to resolve the problem, but I would > > like to > > > > > learn the formal (preferred) way of resolving this issue on Nuttx > > > > > because the same code compiles and runs on Ubuntu without any > > modification > > > > > other than removing <nuttx/config.h>. > > > > > > > > > > BR > > > > > Murat > > > > > > > > > > > > > > >
