yade will no longerbe built on armel/armhf
Hi, yade takes obscene amounts of RAM during builds, causing excessive build times due to swapping on armel/armhf buildds. Since it does not seem to be a package likely to be run ARM machines in near future, we have disabled building it for now. Riku -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120606145438.ga1...@afflict.kos.to
Re: yade will no longerbe built on armel/armhf
Le mercredi 06 juin, Riku Voipio a écrit: yade takes obscene amounts of RAM during builds, causing excessive build times due to swapping on armel/armhf buildds. Since it does not seem to be a package likely to be run ARM machines in near future, we have disabled building it for now. May I ask how much that excessive build time is? Snark on #debian-mentors and #debian-science -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120606173103.75e3c5fd@newton.localdomain
Re: yade will no longerbe built on armel/armhf
On Wed, Jun 6, 2012 at 3:54 PM, Riku Voipio riku.voi...@iki.fi wrote: Hi, yade takes obscene amounts of RAM during builds, causing excessive build times due to swapping on armel/armhf buildds. Since it does not seem to be a package likely to be run ARM machines in near future, we have disabled building it for now. have you considered disabling debug builds instead of cutting absolutely everyone who uses that package off at the knees. webkit is another library that takes insane amounts of RAM during debug builds: it requires resident 1.4gb minimum just for the linker process, but *ONLY* when doing debug builds. a libwebkit non-debug build only takes about 5-10 minutes for the linker phase on a dual-core 2ghz xeon with 2gb of RAM. that goes up to something like 30 minutes for a debug build, and OVER A DAY if the system has only 1gb of RAM. ... so all i did was override the CFLAGS and CXXFLAGS in the debian/rules file (CFLAGS=-O2 -Wetcetc not CFLAGS+=) and the problem was solved: goodbye stupid build times. l. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPweEDw_8=dizt8d5jjuzthpsbu3mksulx-sxlmhxqukam1...@mail.gmail.com
OMAP4 - armel vs armhf
Hi all, I'm using armhf port for OMAP4 (pandboard) installed like in this guide: http://www.chalk-elec.com/?p=1478. I need to run precompiled application, build with CodeSourcery (arm-linux-gnueabi-gcc 4.6.1). There are some floating point math operation like sin/cos/sqrt - all from math.h, but app was built without hard fpu flag. When trying to run it on pandaboard segmentation fault occur (I've checked with gdb that it's caused by that sin() function, which is first math operation in code). I have also second board with Ubuntu11.10 which is armel, and there everything works fine. So, the question is - can I do anything on pandaboard's side to run that application? Just to make it clear - I can't rebuild with flag, because that app must be compatible with also with cores without FPU. Thanks, regards Michal
Re: yade will no longerbe built on armel/armhf
Hi, ok. I will try to reduce RAM-consumption with the next YADE-version. We'll see... Anton 2012/6/6 Riku Voipio riku.voi...@iki.fi: Hi, yade takes obscene amounts of RAM during builds, causing excessive build times due to swapping on armel/armhf buildds. Since it does not seem to be a package likely to be run ARM machines in near future, we have disabled building it for now. Riku -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CALF6qJ=OWMDPAU-v1b+D3o=as3RaVVk3r4vzypeDB2=o13-...@mail.gmail.com
