Bug#715426: Bug # 715426: Interested in getting this done

["Roderick W. Smith" <rod.smith@canonical.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/30/2015 05:22 PM, Tianon Gravi wrote:
> On 30 November 2015 at 11:31, Tianon Gravi <tianon@debian.org>
> wrote:
>> Oh nice; since it's working in QEMU, I'm personally all for
>> arch-enablement! :D
> 
> Hmm, I tried compiling on an arm64 porterbox, and got the
> following:

That's VERY strange....

> make[3]: Entering directory '/home/tianon/refind/libeg' 
> /usr/bin/gcc -I. -I./../include -I/usr/include/efi 
> -I/usr/include/efi/aarch64 -I/usr/include/efi/protocol
> -I../include -I../refind -I../libeg -DCONFIG_aarch64
> -D__MAKEWITH_GNUEFI   -O2 -fno-strict-aliasing -fno-stack-protector
> -fpic -fshort-wchar -mno-red-zone -Wall -c screen.c -o screen.o 
> gcc: error: unrecognized command line option '-mno-red-zone' 
> ../Make.common:89: recipe for target 'screen.o' failed

What's weird about this is that there are signs of both ARM64 and
x86-64 compilation -- "-I/usr/include/efi/aarch64" is obviously ARM64,
but "-mno-red-zone" should be added as an option only on x86-64 systems.

I tried building a Debian package myself in my QEMU environment and
had no problems with it. I tried pushing it up to my testing PPA
(https://launchpad.net/~rodsmith/+archive/ubuntu/testing/+packages),
but it didn't even try to build for ARM64, since that ability is not
enabled by default. I've asked that it be enabled, but I'm not sure
how long that will take.

> The only changes I've applied over what's in master right now are:
> 
> diff --git a/debian/control b/debian/control index 3c130f3..7ca3fa4
> 100644 --- a/debian/control +++ b/debian/control @@ -10,7 +10,7 @@
> Vcs-Browser: 
> https://anonscm.debian.org/cgit/collab-maint/refind.git Vcs-Git:
> git://anonscm.debian.org/collab-maint/refind.git
> 
> Package: refind -Architecture: amd64 i386 +Architecture: amd64
> arm64 i386

This change should not have been necessary if you were using recent
files, since I pushed a similar change up to my git repository a while
ago. This makes me wonder if your problem might have been caused by
out-of-date files. I've added your change to debian/rules to my own
git repository. Could you try again?

> So maybe we should hold off on that bit until we're sure it's
> working more generically? (unless there's something obvious I
> missed O:) )

I'm willing to hold off on ARM64 builds if you continue to have
problems. It's not like the world's knocking down my door for ARM64
versions of rEFInd. ;-)

- -- 
Rod Smith
Server and Cloud Certification Engineer
rod.smith@canonical.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWXPYgAAoJEFgyRI+V0FjmzuMH+gK/EVKEjAWiMm3oeHck5/7F
t3knRDmFPjJDCPErL6t4Co2F36O0/yj8B+NBZ4aRHl/y3z53bt73DCR5iLRnQvWb
XsnLmWsAu6fWXdd+Gk5dcIXs7YaWjtF26uWniQkyseki7qhc6WocjAIB0s9bwpEW
h5lhJKnL7HstVwl+j+kLQTyt3O0N56JittyU+xIokPOS8F7Zsa8AEJ5Y1A/m9xEq
PBxYTbeUQNvBrS4gh4/wGaH1PG2xmZPe3qQvp0um0xxG1aEgNgcouZI4GBHKVDYj
8h5ngCALsiAPAxFXfRk+6ooY7qkSLdN/djM2JJSogbOtVp16qWGGSMNdwvKr98Y=
=/D6t
-----END PGP SIGNATURE-----