GNU bug report logs - #44179
can't build proot-static

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 44179 in the body.
You can then email your comments to 44179 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: luhux <luhux <at> outlook.com>
To: bug-guix <at> gnu.org
Subject: can't build proot-static
Date: Fri, 23 Oct 2020 13:45:19 +0000

[Message part 1 (text/plain, inline)]

If it can be fixed, I can run my packaged Emacs environment on my Android phone.

I executed this command on my x86_64-linux:

guix pack -s aarch64-linux -RR busybox

but it fail:

[build.log (text/plain, attachment)]

Message #10 received at 44179-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: luhux <luhux <at> outlook.com>
Cc: 44179-done <at> debbugs.gnu.org
Subject: Re: bug#44179: can't build proot-static
Date: Wed, 04 Aug 2021 23:26:40 -0400

Hello,

luhux <luhux <at> outlook.com> writes:

> If it can be fixed, I can run my packaged Emacs environment on my Android phone.
>
> I executed this command on my x86_64-linux:
>
> guix pack -s aarch64-linux -RR busybox
>
> but it fail:


[...]

> starting phase `build'
> make: Entering directory '/tmp/guix-build-proot-static-5.1.0.drv-0/proot-5.1.0-checkout/src'
>   GEN	build.h
>   CC	cli/cli.o
>   CC	cli/proot.o
>   CC	cli/note.o
>   CC	execve/enter.o
> ./execve/enter.c: In function ‘compute_load_addresses’:
> ./execve/enter.c:335:36: error: ‘EXEC_PIC_ADDRESS’ undeclared (first use in this function)
>    add_load_base(tracee->load_info, EXEC_PIC_ADDRESS);
>                                     ^~~~~~~~~~~~~~~~
> ./execve/enter.c:335:36: note: each undeclared identifier is reported only once for each function it appears in
> ./execve/enter.c:349:44: error: ‘INTERP_PIC_ADDRESS’ undeclared (first use in this function); did you mean ‘EXEC_PIC_ADDRESS’?
>    add_load_base(tracee->load_info->interp, INTERP_PIC_ADDRESS);
>                                             ^~~~~~~~~~~~~~~~~~
>                                             EXEC_PIC_ADDRESS

I fixed that one some time ago with commit
c881516d4834cc628864bfc193cfb061c3dcde42.

Closing.

Thank you,

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.