Re: [leaf-devel] compiling accel-ppp for x86_64
13.06.2013 19:18, KP Kirchdoerfer пишет: > Thx for providung fixes that fast! > > Am 12.06.2013 22:01, schrieb Andrew: >> Fixed. >> >> P.S. IMHO it'll be good to upgrade GCC to 4.6.4 in near future... > > I'm compiling right now the versions for 5.0 and if everything goes > well, I'll tag 5.0. > > Will you start with gcc update after that? Yes. I tink that it'll be trivial. > Just out of interest, what do you think will be (visible) features? > > kp > This is minor, bugfix release. So no visible features will be available (maybe some code spped-up - if there was regression in optimization that was fixed in 4.6.4); but in future there is lesser chance to stuck on miscompiled code for one of future architectures. -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] compiling accel-ppp for x86_64
Thx for providung fixes that fast! Am 12.06.2013 22:01, schrieb Andrew: > Fixed. > > P.S. IMHO it'll be good to upgrade GCC to 4.6.4 in near future... I'm compiling right now the versions for 5.0 and if everything goes well, I'll tag 5.0. Will you start with gcc update after that? Just out of interest, what do you think will be (visible) features? kp > 12.06.2013 21:20, KP Kirchdoerfer пишет: >> Hi Andrew; >> >> latest accel-ppp fails to build for x86_64 (see below) while it compiles >> for i486. >> >> To me it's a showstopper for 5.0. >> >> Apart from that I think we are ready for 5.0. >> >> Can you have a look at it? >> >> thx kp >> >> buildtool Version 0.7 starting >> Wed Jun 12 20:07:29 2013 >> checking build environment >> trace support not enabled in configfile >> make: Gehe in Verzeichnis >> '/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp' >> mkdir -p >> /opt/buildtool-master/build/x86_64-unknown-linux-uclibc/accel-ppp/etc/init.d >> (cd >> /opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8; >> rm -rf CMakeFiles; cmake \ >> -DCMAKE_C_COMPILER=x86_64-unknown-linux-uclibc-gcc \ >> >> -DCMAKE_FIND_ROOT_PATH="/opt/buildtool-master/toolchain/x86_64-unknown-linux-uclibc >> /opt/buildtool-master/staging/x86_64-unknown-linux-uclibc" \ >> -DCMAKE_SYSTEM_NAME=Linux \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DLOG_FILE=FALSE \ >> -DSHAPER=TRUE \ >> -DRADIUS=TRUE \ >> -DNETSNMP=TRUE \ >> -DLUA=TRUE \ >> >> -DLUA_INCLUDE_DIR="/opt/buildtool-master/staging/x86_64-unknown-linux-uclibc/usr/include" >> \ >> >> -DLUA_LIBRARIES="/opt/buildtool-master/staging/x86_64-unknown-linux-uclibc/usr/lib/liblua.a" >> \ >> -DCMAKE_INSTALL_PREFIX=/usr \ >> -DLIB_SUFFIX="" \ >> .) >> -- The C compiler identification is GNU 4.6.3 >> -- Check for working C compiler: >> /opt/buildtool-master/toolchain/x86_64-unknown-linux-uclibc/bin/x86_64-unknown-linux-uclibc-gcc >> -- Check for working C compiler: >> /opt/buildtool-master/toolchain/x86_64-unknown-linux-uclibc/bin/x86_64-unknown-linux-uclibc-gcc >> -- works >> -- Detecting C compiler ABI info >> -- Detecting C compiler ABI info - done >> -- Looking for timerfd_create >> -- Looking for timerfd_create - found >> -- Found Lua51: >> /opt/buildtool-master/staging/x86_64-unknown-linux-uclibc/usr/lib/liblua.a >> (found version "5.1.5") >> -- Configuring done >> -- Generating done >> -- Build files have been written to: >> /opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8 >> make -j5 -C >> /opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8 >> make[1]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[2]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> Scanning dependencies of target pppoe >> make[3]: Leaving directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> Scanning dependencies of target pptp >> Scanning dependencies of target radius >> make[3]: Leaving directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> Scanning dependencies of target l2tp >> make[3]: Leaving directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Leaving directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> Scanning dependencies of target triton >> make[3]: Entering directory >> `/opt/buildtool-master/source/x86_64-unknown-linux-uclibc/accel-ppp/accel-ppp-code-9ba02ed111f321b71bd526c95bbf559d4cee4de8' >> make[3]: Entering directory >> `/
Re: [leaf-devel] logstash
On 06/13/2013 06:36 AM, Andrew wrote: > Hi. > I think that it isn't a good idea to use java software on small devices > with small amount of RAM. Andrew, Agreed. I was hoping the embedded version of Elasticsearch wasn't implemented in java. I apologize for not doing further research before posting. http://www.elasticsearch.org/guide/reference/setup/installation/ http://www.elasticsearch.org/guide/reference/java-api/client/ > 13.06.2013 16:13, Mike Noyes пишет: >> Everyone, >> Is it possible for us to implement logstash on Bering-uClibc? >> >>http://logstash.net/ >> >> Elasticsearch on the embedded appliance? >> >>http://logstash.net/docs/1.1.13/tutorials/getting-started-simple -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] logstash
Hi. I think that it isn't a good idea to use java software on small devices with small amount of RAM. 13.06.2013 16:13, Mike Noyes пишет: > Everyone, > Is it possible for us to implement logstash on Bering-uClibc? > >http://logstash.net/ > > Elasticsearch on the embedded appliance? > >http://logstash.net/docs/1.1.13/tutorials/getting-started-simple > -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] logstash
Everyone, Is it possible for us to implement logstash on Bering-uClibc? http://logstash.net/ Elasticsearch on the embedded appliance? http://logstash.net/docs/1.1.13/tutorials/getting-started-simple -- Mike Noyes http://sourceforge.net/users/mhnoyes https://plus.google.com/u/0/113364780158082152468 -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
