dev-lang/erlang, who is using ? - Page 1
Forum section: electronics / general

author: legacy
author_rank: Super Contributor
timestamp: December 05, 2015, 04:50:28 pm
content: hi guysI am going to emergedev-lang/erlangfor a laptop/x86 machine, glibc profiledCode:* dev-lang/erlangLatest version: 17.5Homepage: http://www.erlang.org/Description: Erlang programming language, runtime environment, and large collection of librariesLicense: ErlPL-1.1Theerlangpackage seems to be unsupported by "arm" and "mips", perhaps a missing ebuild check in gentoo portage(they look "~", which never looks good -> sometimes it means bracken/not-working, and bad things will happen)btw, who is using this language, and in case, for which purpose ?I am going to install because I got requested by my "tutor" for a computer science course

author: neil555
author_rank: Contributor
timestamp: December 05, 2015, 08:02:18 pm
content: Jeez, what a horrific looking language

author: Alexei.Polkhanov
author_rank: Frequent Contributor
timestamp: December 05, 2015, 08:25:09 pm
content: I used Erlang few times for short projects. It is a functional (as oppose to procedural like C or Pascal) language designed by Ericsson and it is designed to support somewhat extreme degrees of parallelism on single CPU - in Erlang program it is not uncommon to have 1000s of threads - it is because threads in Erlang are very cheap. Ericsson used it to program phone switching equipment. Needless to say that all information is freely available on internet. Erlang is very nice, elegant language.

author: kaz911
author_rank: Super Contributor
timestamp: December 05, 2015, 08:49:58 pm
content: Erlang is great for multi-threaded SAFE transactional programming.It takes a while getting used to but even small machines can support 1000's of threads running in " parallel "It is designed to run 24-7 applications - and can be updated and upgraded while running (if you design right)It is easy to make " RPC " and run same program over many machinesThere are a lot of big big Erlang systems around - I think Facebook chat backend is one of them and WhatsApp as well (http://www.fastcompany.com/3026758/inside-erlang-the-rare-programming-language-behind-whatsapps-success)

author: Monkeh
author_rank: Super Contributor
timestamp: December 05, 2015, 11:11:08 pm
content: Quote from: legacy on December 05, 2015, 04:50:28 pmThat is not at all what it means.

author: miguelvp
author_rank: Super Contributor
timestamp: December 05, 2015, 11:46:28 pm
content: I've played a little with it,not proficient with it.I think erlang will become very relevant in the near future with cpus with hundreds of cores.Also I think it's a good language for fpga soft cores.It's strength is the messaging system and the in memory database mnesia.Don't know enough yet to see if it could actually act as an HDL directly. But if possible I think that would be cool.

author: miguelvp
author_rank: Super Contributor
timestamp: December 05, 2015, 11:50:25 pm
content: Interesting interviews with Joe Armstrong:Article:https://globalengineer.wordpress.com/2008/09/12/joe-armstrong-interviews-erlang-and-fpgas/JAOO 2007: Joe Armstrong - On Erlang, OO, Concurrency, Shared State and the Future, Part 1https://channel9.msdn.com/blogs/charles/jaoo-2007-joe-armstrong-on-erlang-oo-concurrency-shared-state-and-the-future-part-1JAOO 2007: Joe Armstrong - On Erlang, OO, Concurrency, Shared State and the Future, Part 2https://channel9.msdn.com/blogs/charles/jaoo-2007-joe-armstrong-on-erlang-oo-concurrency-shared-state-and-the-future-part-2ejabberd is done in erlang (XMPP server)So is mongoose (XMPP server as well) whatsup uses this.https://www.erlang-solutions.com/products/mongooseim.html

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 12:44:40 am
content: Quote from: Monkeh on December 05, 2015, 11:11:08 pmI am a gentoo user since 2005, and I am experienced with gentoo-{ ppc, mips, hppa, arm, x86 }try to force emerge erlang on arm, all the ebuilds are marked as "~", results: it does not compile!try to force compile on mips, all the ebuilds are marked as "~", results: it compiles, but it's bugged, and you have to downgradeCode:cat # my-emerge-log.txt2015-12-05 - emerge dev-lang/erlang - arm - failure - root2015-12-05 - emerge dev-lang/erlang - mips - success - root - downgraded2015-12-05 - emerge dev-lang/erlang - ppc - success - root2015-12-05 - emerge dev-lang/erlang - x86 - success - root2015-12-05 - emerge dev-lang/erlang - hppa - failure - rootcorollary: practically it means "keep attention to the bell"btw, are you able to emerge erland on arm ? if so, let me know

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 12:47:44 am
content: Quote from: miguelvp on December 05, 2015, 11:46:28 pmcool

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 12:56:34 am
content: QuoteIn my experience, the "believed" assumption is almost always False with { arm, mips, hppa }, due to the man power that these architecture require before the package version is considered suitable for arch.

author: Monkeh
author_rank: Super Contributor
timestamp: December 06, 2015, 02:49:23 am
content: Quote from: legacy on December 06, 2015, 12:44:40 amSame here, and I will tell you quite authoritively, the ~ keyword indicates that it has not been tested to be marked stable. It doesnotmean it is broken.You can, in fact, run a very stable, working machine on ~x86 or ~amd64.QuoteI don't use ARM.

author: matseng
author_rank: Frequent Contributor
timestamp: December 06, 2015, 03:02:54 am
content: Quote from: kaz911 on December 05, 2015, 08:49:58 pmHow would you compare it to golang? - the list above sounds like an ad for go, (except for the update-while-running)..

author: Sal Ammoniac
author_rank: Super Contributor
timestamp: December 06, 2015, 03:30:13 am
content: Github is partially implemented in Erlang.

author: kaz911
author_rank: Super Contributor
timestamp: December 06, 2015, 07:38:08 am
content: Quote from: matseng on December 06, 2015, 03:02:54 amI do not have any experience with Go apart from trying it for 15 min. Erlang is a bit complex to learn - but once you get the hang of it - it is not too bad. There are btw a lot of MQTT implementations in Erlang as well as it is very suited for (buzzword alert) IoT stuff as well.I once did a " number portability system " for a Telco in Java - and had I known Erlang at the time - I should have used that. Thread overhead is so small and once it is running - breaking down rarely happens. Where as in Java you can get all kinds of weirdo stuff happening. It has been a while since I have done anything serious in Erlang - but the " worst " thing about Erlang is there was no great IDE's at the time - so if you only dip in and out - you did not get help from Syntax Highlights and mouse overs like you do in many great IDE's now. But at the time there was quite a few IDE's on the way. I don't know the status now.But for me - any programming language is a tool - and each language / tool has it's specific uses and use cases. I started with Z80 assembler when I was a kid (ZX80 kit) - moved on to 6502's basic and assembler - them fell in love with BBC B Micro Procedural Basicand then by chance got a free copy of Poly Pascal from the Man himself (Anders Hejlsberg) - then Turbo Pascal (Borland bought Poly Pascal) - then Turbo C - then Turbo C++ (which I never got the hang off) - then Python, some Java and today - most of my things are in C or C# and Python. I do find Java a pain in the backside due to version fragmentation so I only do Java if i ABSOLUTELY have to.But if I need transaction based stuff - I will go to Erlang without a doubt. So each language has it's own usage. And each language has it's " followers/fanatics " of whom you should never listen to for too longbut be pragmatic as read use cases for each - and select the right language for the current job at hand. You would not use a hammer to put in a screw in a wall would you? (if you had a screw driver available and knew how to use it....) If it is just one screw you might be fine using a hammer - result won't be pretty but it might workBut if you are building a house you would take the time to learn how to use a screw driver.

author: paf
author_rank: Regular Contributor
timestamp: December 06, 2015, 09:35:47 am
content: You have more info on Erlang and embedded systems at:http://www.erlang-embedded.comThe "thing" about Erlang is the message passing model for parallelism and the "let it fail" philosophy.In Erlang you build lots of independent processes that communicate sending messages. No locks, no shared memory, no semaphores, no contention. That's also how hardware works or should work. There is no globally shared data.If you want/need globally shared data, give it to a process and communicate with it with messages. Make a server.When a process starts another, it can "ask the system" for a message when the created process "crashes". So you can have very easily an hierarchy of "supervisor" processes watching "workers" and restarting them when one "dies".It may not suitable for the "embedded" side near the sensors, but if you need to connect hundreds or thousands of embedded systems, or clients or whatever, you better look into Erlang.

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 10:31:08 am
content: Quote from: Monkeh on December 06, 2015, 02:49:23 amYoMan, "authoritatively"Quote from: Monkeh on December 06, 2015, 02:49:23 am"authoritatively" smells you have written the guide without any practical experience!"practically" it often means thatit is not known whether the package will workportage/dev-lang/gnat-gcc/gnat-gcc-4.6.4.ebuildCode:SRC_URI="ftp://gcc.gnu.org/pub/gcc/releases/gcc-${PV}/gcc-core-${PV}.tar.bz2ftp://gcc.gnu.org/pub/gcc/releases/gcc-${PV}/gcc-ada-${PV}.tar.bz2amd64? ( https://dev.gentoo.org/~george/src/gnatboot-${BOOT_SLOT}-amd64.tar.bz2 )sparc? ( https://dev.gentoo.org/~george/src/gnatboot-${BOOT_SLOT}-sparc.tar.bz2 )x86? ( https://dev.gentoo.org/~george/src/gnatboot-${BOOT_SLOT}-i686.tar.bz2 )"# ppc? ( mirror://gentoo/gnatboot-${BOOT_SLOT}-ppc.tar.bz2 )KEYWORDS="amd64 x86"dev-lang/gnat-gcc/gnat-gcc-4.1.2.ebuildCode:# SLOT is set in gnatbuild.eclass, depends only on PV (basically SLOT=GCCBRANCH)# so the URI's are static.SRC_URI="ftp://gcc.gnu.org/pub/gcc/releases/gcc-${PV}/gcc-core-${PV}.tar.bz2ftp://gcc.gnu.org/pub/gcc/releases/gcc-${PV}/gcc-ada-${PV}.tar.bz2ppc? ( mirror://gentoo/gnatboot-${BOOT_SLOT}-ppc.tar.bz2 )x86? ( mirror://gentoo/gnatboot-${BOOT_SLOT}-i386.tar.bz2 )amd64? ( mirror://gentoo/gnatboot-${BOOT_SLOT}-amd64.tar.bz2 )"KEYWORDS="amd64 ~ppc x86"do you see a bootstrap for arm? mips? hppa?OK, it's coherent with the KEYWORDSCode:If a package has NO-KEYWORDS for a given arch, it means it is not known whether the package will work, or that insufficient testing has occurred for ~arch.in this case it means: there is no bootstrap for a given arch[]={ mips, hppa, arm }do you see the difference between dev-lang/gnat-gcc-4.1.2 && dev-lang/gnat-gcc-4.6.4 ?~ppc had been removed from KEYWORDS (4.6.4), do you know why ?~ppc did not compile at all -> it was broken on ppc!indeed, on ppc (my Apple PowerBook-G4 laptop) I had to manually fix the problem, cloning the ebuild into an Overlayedit:I am going to do something similar in order to support { mips, arm }, more specifically I am going to create a few bootstrapsCode:mips? ( mylan://overlay/supfiles/dev-lang/gnat-gcc/gnatboot-${BOOT_SLOT}mips.tar.bz2 )arm? ( mylan://overlay/supfiles/dev-lang/gnat-gcc/gnatboot-${BOOT_SLOT}-arm.tar.bz2 )

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 10:31:49 am
content: Quote from: Sal Ammoniac on December 06, 2015, 03:30:13 amnice to know, I will grab the source code( I am curious )

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 10:36:02 am
content: Quote from: paf on December 06, 2015, 09:35:47 amextremely impressive, thank you for the linkI can do something similar with a few hundred PPC embedded boardsedit:~200 tiny boards on a rack-stack, they are PPC405GP, provided by my university for R&D purposes

author: tggzzz
author_rank: Super Contributor
timestamp: December 06, 2015, 10:37:45 am
content: Quote from: kaz911 on December 06, 2015, 07:38:08 amHow boringly sensible and rational.BTW, the key point about Erlang is the lack of shared state (let alone global state). That meansthere are no unpleasant surprises when multiprocessor caches and memory hierarchy interact in rare strange waysthere are no unpleasant surprises when processing scalability requires another computer is addedupgrading arunning systemis trivial: just direct the stream of messages to the upgraded actor, and remove the existing actor when its message queue is emptydistributed systems which viciously demonstrate L Peter Deutsch's "eight fallacies of distributed computing" (think IoT) are easier to make reliable if they embody Erlang's philosophyI don't know ofanyother language that makes those important benefits trivial to implement.

author: tggzzz
author_rank: Super Contributor
timestamp: December 06, 2015, 10:39:21 am
content: Quote from: matseng on December 06, 2015, 03:02:54 amGolang is unproven. Erlang is proven, with decades of experience in large critical systems.

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 02:51:03 pm
content: Code:make: *** [../ebin/hipe_consttab.beam] Abortedmake: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe/misc'/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: recipe for target 'opt' failedmake: ***  Error 2make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe'/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: recipe for target 'opt' failedmake: ***  Error 2make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib'Makefile:533: recipe for target 'secondary_bootstrap_build' failedmake: ***  Error 2emake failed* ERROR: dev-lang/erlang-15.2.3.1::gentoo failed (compile phase):* (no error message)** Call stack:* ebuild.sh, line 93: Called src_compile* environment, line 4133: Called die* The specific snippet of code:* emake || die;** If you need support, post the output of `emerge --info '=dev-lang/erlang-15.2.3.1::gentoo'`,* the complete build log and the output of `emerge -pqv '=dev-lang/erlang-15.2.3.1::gentoo'`.!!! When you file a bug report, please include the following information:GENTOO_VM= CLASSPATH="" JAVA_HOME=""JAVACFLAGS="" COMPILER=""and of course, the output of emerge --info =erlang-15.2.3.1* The complete build log is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'.* The ebuild environment file is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/environment'.* Working directory: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'* S: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'>>> Failed to emerge dev-lang/erlang-15.2.3.1, Log file:>>> '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'* Messages for package dev-lang/erlang-15.2.3.1:* ERROR: dev-lang/erlang-15.2.3.1::gentoo failed (compile phase):* (no error message)** Call stack:* ebuild.sh, line 93: Called src_compile* environment, line 4133: Called die* The specific snippet of code:* emake || die;** If you need support, post the output of `emerge --info '=dev-lang/erlang-15.2.3.1::gentoo'`,* the complete build log and the output of `emerge -pqv '=dev-lang/erlang-15.2.3.1::gentoo'`.* The complete build log is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'.* The ebuild environment file is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/environment'.* Working directory: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'* S: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'done,logged!no way to get erlang on arm, I have to investigate(erlang is ~arm)

author: Monkeh
author_rank: Super Contributor
timestamp: December 06, 2015, 02:54:03 pm
content: You might start a few lines higher where the actual error will be.

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 03:18:51 pm
content: Code:armv5tel-softfloat-linux-gnueabi-gcc -Wl,-O1 -Wl,--as-needed -o /var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/bin/armv5tel-softfloat-linux-gnueabi/epmd /var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/obj/armv5tel-softfloat-linux-gnueabi/epmd.o /var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/obj/armv5tel-softfloat-linux-gnueabi/epmd_cli.o /var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/obj/armv5tel-softfloat-linux-gnueabi/epmd_srv.o -lutil -ldl -lm -L../../lib/internal/armv5tel-softfloat-linux-gnueabi -lerts_internal -lmmake: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/epmd/src'make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/epmd/src'make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/epmd'make: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/lib_src'make -f armv5tel-softfloat-linux-gnueabi/Makefile TYPE=optmake: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/lib_src'make: Nothing to be done for 'all'.make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/lib_src'make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts/lib_src'make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/erts'cd lib && \ERL_TOP=/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03 PATH=/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/bootstrap/bin:"${PATH}" \make opt SECONDARY_BOOTSTRAP=truemake: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib'make: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe'Makefile:71: warning: overriding recipe for target 'clean'/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: warning: ignoring old recipe for target 'clean'=== Entering application hipemake: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe/misc'erlc -W +debug_info +warn_exported_vars +warn_missing_spec +warn_untyped_record -o../ebin hipe_consttab.erlA newer kernel is required to run this binary. (__kernel_cmpxchg64 helper)/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/armv5tel-softfloat-linux-gnueabi/otp.mk:116: recipe for target '../ebin/hipe_consttab.beam' failedmake: *** [../ebin/hipe_consttab.beam] Abortedmake: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe/misc'/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: recipe for target 'opt' failedmake: ***  Error 2make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe'/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: recipe for target 'opt' failedmake: ***  Error 2make: Leaving directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib'Makefile:533: recipe for target 'secondary_bootstrap_build' failedmake: ***  Error 2emake failed* ERROR: dev-lang/erlang-15.2.3.1::gentoo failed (compile phase):* (no error message)** Call stack:* ebuild.sh, line 93: Called src_compile* environment, line 4133: Called die* The specific snippet of code:* emake || die;** If you need support, post the output of `emerge --info '=dev-lang/erlang-15.2.3.1::gentoo'`,* the complete build log and the output of `emerge -pqv '=dev-lang/erlang-15.2.3.1::gentoo'`.!!! When you file a bug report, please include the following information:GENTOO_VM= CLASSPATH="" JAVA_HOME=""JAVACFLAGS="" COMPILER=""and of course, the output of emerge --info =erlang-15.2.3.1* The complete build log is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'.* The ebuild environment file is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/environment'.* Working directory: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'* S: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'>>> Failed to emerge dev-lang/erlang-15.2.3.1, Log file:>>> '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'* Messages for package dev-lang/erlang-15.2.3.1:* ERROR: dev-lang/erlang-15.2.3.1::gentoo failed (compile phase):* (no error message)** Call stack:* ebuild.sh, line 93: Called src_compile* environment, line 4133: Called die* The specific snippet of code:* emake || die;** If you need support, post the output of `emerge --info '=dev-lang/erlang-15.2.3.1::gentoo'`,* the complete build log and the output of `emerge -pqv '=dev-lang/erlang-15.2.3.1::gentoo'`.* The complete build log is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/build.log'.* The ebuild environment file is located at '/var/tmp/portage/dev-lang/erlang-15.2.3.1/temp/environment'.* Working directory: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'* S: '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03'done,logged!Code:/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/otp_subdir.mk:28: warning: ignoring old recipe for target 'clean'=== Entering application hipemake: Entering directory '/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/lib/hipe/misc'erlc -W +debug_info +warn_exported_vars +warn_missing_spec +warn_untyped_record -o../ebin hipe_consttab.erlA newer kernel is required to run this binary. (__kernel_cmpxchg64 helper)/var/tmp/portage/dev-lang/erlang-15.2.3.1/work/otp_src_R15B03/make/armv5tel-softfloat-linux-gnueabi/otp.mk:116: recipe for target '../ebin/hipe_consttab.beam' failedmake: *** [../ebin/hipe_consttab.beam] Aborted...the same ebuild had success on ppc/x86/mips

author: Monkeh
author_rank: Super Contributor
timestamp: December 06, 2015, 03:27:31 pm
content: You're running a kernel that old?

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 03:41:17 pm
content: can you define "old", pre NPTL ?if so, no, I am on 2.6.39 & 3.3.8 with the same result

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 03:49:19 pm
content: I wonder if it means "kernel with devtmpfs", which might be a modern feature

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 03:54:16 pm
content: oh man / gcc-4.7 / libgcc / config / arm / linux-atomic-64bit.cCode:/* Check that the kernel has a new enough version at load. */static void __check_for_sync8_kernelhelper (void){if (__kernel_helper_version < 5){const char err[] = "A newer kernel is required to run this binary. ""(__kernel_cmpxchg64 helper)\n";/* At this point we need a way to crash with some informationfor the user - I'm not sure I can rely on much else beingavailable at this point, so do the same as generic-morestack.cwrite () and abort (). */WTFrog

author: Monkeh
author_rank: Super Contributor
timestamp: December 06, 2015, 03:57:21 pm
content: Quote from: legacy on December 06, 2015, 03:49:19 pmNo, it means "kernel with support for 64-bit atomic operations on <ARMv7 CPUs".3.3.8 should cover that.. but is still utterly ancient.For now I suggest trying a kernel from the last oh, two or so years..What else is four years out of date on your machines?!

author: legacy
author_rank: Super Contributor
timestamp: December 06, 2015, 04:00:44 pm
content: Quote from: Monkeh on December 06, 2015, 03:57:21 pmIt's a product of ACME System, still for sale!