Re: Problem on INotify
2010/2/12 Javier S. Pedro : > Torello Querci wrote: >> I'm trying to compile mono for MAEMO. > Thanks for the effort! > >> Any suggestion is welcome. > > I'd say try to guess what inotify is used for in Mono (my guess is > some obscure part of System.IO), and if it's not really needed for building > a bootstrapping capable toolchain, then just write the required empty > inotify stubs. > > If that's not acceptable, you may also want to implement the syscall wrappers > yourself (see the glibc code). > The inotify syscall is not used by mono but by glib, so is the glib that not compile properly. Looking into the configure.in file of glib I see that there is a check for the presence of sys/inotify.h header file. If I try to temporary rename the sys/inotify.h header file now glib was compiled properly. > If you patch sbox's glibc, distributing it will be a nightmare. > Absolutly right. This version of glib is necessary only for compile mono devkit, where the ARMEL version of mono is compiled the normal glib version is used. The problem is related only with host-gcc toolchains, not the target (both x86 and armel) toolchains. Best Regards, Torello ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problem on INotify
Torello Querci wrote: > I'm trying to compile mono for MAEMO. Thanks for the effort! > Any suggestion is welcome. I'd say try to guess what inotify is used for in Mono (my guess is some obscure part of System.IO), and if it's not really needed for building a bootstrapping capable toolchain, then just write the required empty inotify stubs. If that's not acceptable, you may also want to implement the syscall wrappers yourself (see the glibc code). If you patch sbox's glibc, distributing it will be a nightmare. Javier. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problem on INotify
2010/2/11 Javier S. Pedro : > Hi, it seems you didn't CC the last post to the mailing list... > Right ... sorry > 2010/2/11 Torello Querci : >> I know but really I have no other way :( > > What are you doing? Just to be completely sure you really need a > devkit, since 99.9% of development doesn't need one. > I'm trying to compile mono for MAEMO. I already do it in the past with an old version of mono (the 2.0.1) for MAEMO4 (DIABLO), Before I try to do it for MAEMO4 device (I have a N810 not the N900) device but there are a lots of problem so I decide to update everything ... some other will make the test on the real device. I not able to generate mono directory on ARMEL target because a lots of tool are generated during the compile stage and it is used. Unfortunately QEMU not implements all the opcode that are used in the generated application, so the only way that I have was to use devkit. This is the link to the previous port of mono on MAEMO: http://code.google.com/p/tomboy-maemo/wiki/MonoSbDevkit Any suggestion is welcome. Cheers, Torello. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problem on INotify
Torello Querci wrote: > The source C code compile well on X86 and ARMEL target but on > HOST environment get this error: > > undefined reference to `inotify_rm_watch' Remember that HOST target doesn't use the host GNU C Library, but scratchbox's own, which is rather outdated and most probably doesn't contain the inotify syscalls. I suggest you reconsider if you really need to create your own devkit. Most if not all software development for Maemo doesn't need custom devkits, and they are not supported in the autobuilder. If you _really_ need to create a devkit, you can patch scratchbox's glibc but it's not going to be a quick job. Javier ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Problem on INotify
Hi guys, For a lots of reason I need to compile C code for devkit that use INotify. The source C code compile well on X86 and ARMEL target but on HOST environment get this error: var/tmp/cc2TNRPk.o(.text+0x1b): In function `main': : undefined reference to `inotify_init' /var/tmp/cc2TNRPk.o(.text+0x4b): In function `main': : undefined reference to `inotify_add_watch' /var/tmp/cc2TNRPk.o(.text+0x1e6): In function `main': : undefined reference to `inotify_rm_watch' The source code that I use for test is taken from this article: http://www.ibm.com/developerworks/linux/library/l-ubuntu-inotify/index.html Can anyone help me? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
