if you get a chance and have some spare HDD space and cpu time left -- you could give a try and setup virtualized emulated armel box, e.g. starting with squeeze images from http://people.debian.org/~aurel32/qemu/armel/ and then upgrading them to sid (might end up being non trivial).
I think at some point I have done smth like that but forgotten what was the outcome (besides that it was a bit slowish) On Mon, 23 Jan 2012, andrei zavada wrote: > Hmm... It's an armel g++-4.6 freaking out wrt c++0x. I'll try to devise some > workaround (I bumped into a similar issue with g++-4.5.x, and dealt with it > somehow without properly understanding what went wrong and who's to blame; > and the issue itself went away after an upgrade). > Or it may well be down to g++ version change: g++ was at 4.6.2-11 on > 2012-01-12 19:01:38 when aghermann-0.5.0-1 was (successfully) built, whereas > the build failure we are discussing now comes up with g++ 4.6.2-12 (I'm > looking at this line in build logs: > Setting up g++-4.6 (4.6.2-nn) ... > Anyway, it's difficult for me to troubleshoot the issue with any degree of > certainty, given the fact all is fine on other arches (and, I have no armel > box available); I'll just try to make code less heavy on g++. > More on that soon, > Andrei -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
