Add support for aarch64
Rob Landley
rob at landley.net
Wed May 15 12:34:28 WST 2013
On 05/14/2013 12:56:49 PM, Mike Frysinger wrote:
> that doesn't help with your outdated config.sub files which is a lot
> more what
> this report is about -- they're cross-compiling for aarch64, not
> running
> natively under it.
I bootstrap native build environments and run 'em under qemu, therefore
this is sufficient for my needs.
My intended gripe was more along the lines of "autoconf is useless and
making it _more_ complicated doesn't improve matters, the correct
response to stroppy FSF code is almost always ripping it out". But
that's a largeish tangent for this thread/list.
> other random notes:
> - should have an exec in there
Utterly doesn't matter.
> - bit surprised you didn't use printf rather than the non-portable
> echo -e
I implemented -e in busybox and toybox. (And the toybox one understands
"--".) Considering I'm running it in an environment I built from source
using known package versions...
> - that code isn't tolerant of whitespace splitting
If you're really going to care about that you need -print0 because a
filename can have an embedded newline in it, but none of the packages
I've ever encountered do that; the paths it's processing are
package-relative.
(I'd ask why you're trying to prove you're a better programmer than
other people instead of trying to prove you're a better programmer than
the computer, but I honestly don't care. This is the dropbear list,
this tangent is not about dropbear...)
Rob
More information about the Dropbear
mailing list