Thanks, by following the documentation, I am now able to compile C programs. I have compiled the nice X10 control program Heyu for a friend. http://heyu.tanj.com/heyu2/
Sadly, DansGuardian is a C++ program, so things are getting harder. Since I have plenty of space on my flash I told to myselff that I will copy the binary and libstd++ on the router and then everything should work... Not at all. Trying to compile an "Hello World" c++ program with the uClibc-gcc gives me more headaches. # make hello # g++ hello.cpp -o hello # hello.cpp:1:20: iostream: No such file or directory # hello.cpp: In function `int main()': # hello.cpp:5: error: `cout' undeclared in namespace `std' # make: *** [hello] Error 1 Since g++ is configured to look in /usr/i386-linux-uclibc/include/g++ directory, I copied local c++ include files is this directory. It does not work. Local include files are not compatible with uClibc. # g++ -o hello hello.cpp # In file included from /usr/i386-linux-uclibc/include/g++/bits/c+ +locale.h:43, # from /usr/i386-linux-uclibc/include/g++/iosfwd:46, # from /usr/i386-linux-uclibc/include/g++/ios:44, # from /usr/i386-linux-uclibc/include/g++/ostream:45, # from /usr/i386-linux-uclibc/include/g++/iostream:45, # from hello.cpp:1: #/usr/i386-linux-uclibc/include/iconv.h:27:2: #error Attempted to include iconv.h when uClibc built without locale support. What should I do to compiled a c++ program compatible with the Bering- uClib environment? Thanks. > Herve, > > > I am working to make DansGuardian working in bering-uCLibc with no > > success. > > > > Firstly, I am wondering why there is no parental filtering package > > available with bering-uClibc? I think this functionality would be a nice > > feature to implement in a router. Did I missed something ? > > > Because nobody created such a package. > > > Secondly, where should I start to create a build environment for > > compiling a program for bering-uCLibc. The buildtool seems to have a > > toolchain include but I don't see how to use it without making cvs > > repository and so on ... > > > You should start with the documentation: > http://leaf.sourceforge.net/doc/guide/buc-devel.html > You don't need to create a cvs repository. > > > Maybe I could understand with a local "hello World!" example ... > > > > > > I would love a solution like the pre-compiled uClibc development system > > given by uClibc (http://www.uclibc.org/toolchains.html). > > > Such a pre-compiled toolchain would be quickly outdated, if you look at > the above toolchain you will see that it's from 12 jan 2005. There isn't > even a pre-compiled toolchain for the latest uClibc version. > We really don't have the time to daily or weekly recompile a toolchain, > besides building your own only costs some compile time and you are sure > you have the latest changes. > > > Thanks for any help. > > > No problem. > > Eric Spakman > ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
