On 07/11/2018 12:59 PM, Bruce Dubbs wrote:
On 07/11/2018 10:28 AM, Alan Corey wrote:
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
No /tools in there. How does it get
On 07/11/2018 10:28 AM, Alan Corey wrote:
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
No /tools in there. How does it get there? I configured glib with
the little
On 11.7.2018. 17:28, Alan Corey wrote:
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
This is adjusted in gcc pass 1. Current sed that fixes this is made for
x86/x86_64,
OK, it fails. And when I do
readelf -l a.out
and look at the output manually the interpreter line is just
[Requesting program interpreter: /lib/ld-linux-aarch64.so.1]
No /tools in there. How does it get there? I configured glib with
the little script
#!/bin/bash
../configure --prefix=/tools
On Tue, 10 Jul 2018 20:37:47 -0400
Michael Shell wrote:
> Hazel,
>
> Looking again at what you've posted, and the bug report you filed after
> you bisected the kernel:
>
> https://www.spinics.net/lists/linux-acpi/msg81646.html
>
> I'd say it is *not* an acpi problem even though it appears
