Your message dated Sun, 17 Aug 2014 17:52:46 -0500 with message-id <87y4umloe9....@trouble.defaultvalue.org> has caused the report #758463, regarding guile-2.0: Unable to cross-build to arm or arm64 (runtime endianness detection failure) to be marked as having been forwarded to the upstream software author(s) guile-de...@gnu.org
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 758463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---[If possible, please preserve at least the *-forwarded address in any replies.] Wookey <woo...@wookware.org> writes: > Package: guile-2.0 > Version: 2.0.11+1 > Guile can cross-build scheme scripts, but if you try to cross-build > scheme for arm or arm64, it fails It looks like the primary problem is that cpu-endianness in target.scm has no match for either "arm", which is what armhf reports (at least in Debian), or "aarch64.*". The patch here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758463 fixes that, but may need to be adjusted to keep the "arm.*el" clause. In any case, I wanted to see how we'd like to handle this upstream so we can do something similar in Debian. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--- End Message ---
