Re: how to build qemu-xxx-static

[Peter Maydell]

On Fri, 27 Aug 2021 at 19:49, Frans de Boer <frans@fransdb.nl> wrote:
> Following your pointers, I noticed that it was all about missing static 
> libraries/header files. The error messages where not helpful at all. 
> config.log provided some pointers.

Yeah. We tend to assume "the compiler works" a bit more than
perhaps we should.

> Now I can configure, compile and start some activity like starting a shell 
> script, which runs tar and continue with a child bash script to start 
> configure, only to end with:
>
> /sources-base/gcc-11.2.0/libstdc++-v3/configure 'CXXFLAGS=-g -O2 
> -D_GNU_SOURCE' --prefix=/usr --host=aarch64-cross-linux --disable-multilib 
> --disable-nls --disable-libstdcxx-pch
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: This script requires a shell 
> more modern than all
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: the shells that I found on 
> your system.
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: Please tell 
> bug-autoconf@gnu.org about your system,
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: including any error possibly 
> output before this
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: message. Then install a 
> modern shell, or manually run
> /sources-base/gcc-11.2.0/libstdc++-v3/configure: the script under such a 
> shell if you do have one.
> ------------------------------------------------------
> However, it is the newest bash script, but configure can't find it, so it 
> seems (see attached file).
>
> Just extra info: all files have been checked to be compatible with ARM 
> aarch64.

The shell script seems to be unable to find /bin/sh etc binaries.
In general configure and other shell scripts work in QEMU, so my
first guess is that the environment you're running QEMU in (which
you don't describe -- chroot? something else?) is not set up right.

> Also, I am not sure, but when linking the static binary 
> 'aarch64-linux-binfmt', I get a whole slew of message like below:
>
> /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: 
> /home/abuild/rpmbuild/BUILD/glib-2.68.4/x86_64-suse-linux/../glib/gutils.c:639:
>  warning: Using 'getpwnam_r' in statically linked applications requires at 
> runtime the shared libraries from the glibc version used for linking
> /usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld: 
> /home/abuild/rpmbuild/BUILD/glib-2.68.4/x86_64-suse-linux/../glib/gutils.c:645:
>  warning: Using 'getpwuid_r' in statically linked applications requires at 
> runtime the shared libraries from the glibc version used for linking

These are expected. They're because QEMU is linked against the host
glib library, and some parts of libglib use these libc functions like
getpwnam_r that won't work in a statically linked setup. But we know
that QEMU doesn't actually use the glib functions that use those
libc functions, so it's not a problem. Unfortunately there's no way
to suppress these messages (it would require changes in how libglib
splits their source code between .c files.)

> I don´t understand where the '/home/abuild/rpmbuild/BUILD/...' came from.

That's the path where whoever built the glib rpm for SUSE happened
to have their source code.

-- PMM