Quick update with some additional information. The installer appears
to have put that file here:
instead of in /lib
A symbolic link solved that problem but then then next installation
issue pops up:
"./test: error while loading shared libraries: libstdc++.so.6: cannot
open shared object file: No such file or directory"
The location of that file installed here on my system:
Unfortunately the error doesn't indicate the path where it's looking
On Sun, Sep 18, 2016 at 4:10 PM, Joe Ciarcia <jazzka...@gmail.com> wrote:
> Package: qemu-user-static
> Version: 1.2.6+dfsg-3.1
> Severity: important
> Dear Maintainer,
> *** Reporter, please consider answering these questions, where appropriate ***
> * What led up to the situation?
> Compiled a simple test.cpp program for armhf to test qemu. The code is as
> using namespace std;
> int main()
> cout << "Hello from an ARMHF architecture\n";
> * What exactly did you do (or not do) that was effective (or
> When transfering the resulting binary to a BeagleBone Black it runs just
> fine. Also, this same file ran just fine with qemu under Debian Jessie, but
> with the 4.7 experimental kernel installed.
> * What was the outcome of this action?
> Under the testing version of stretch I get the following error when
> attempting to run the binary:
> /lib/ld-linux-armhf.so.3: No such file or directory
> * What outcome did you expect instead?
> I expected it to send the following output to the terminal:
> Hello from an ARMHF architecture
> -- System Information:
> Debian Release: stretch/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: armhf
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)