On Tue, Jul 28, 2020 at 6:51 AM Andreas Schwab <sch...@linux-m68k.org> wrote:
>
> On Jul 28 2020, H.J. Lu via Binutils wrote:
>
> > On x86, the native GCC can support -m32 and -m64. "gcc -m32" or "gcc -m64"
> > are not cross compiling.
>
> You cannot link -m64 and -m32 together.
>
> > I didn't set PKG_CONFIG_LIBDIR and I don't want to set it.
>
> Then use the correct pkg-config for your target. If you think
> pkg-config is broken, then fix _that_.
>
I did:
RUNTESTFLAGS="--target_board 'unix{-m32}'" CC="gcc -m32 -fno-lto
-fcf-protection"
CXX="g++ -fno-lto -m32 -fcf-protection" /exp
ort/gnu/import/git/gitlab/x86-binutils/configure \
--enable-targets=x86_64-linux \
i686-linux \
--enable-plugins --disable-gdb --disable-gdbserver --disable-libdecnumbe
r --disable-readline --disable-sim --with-sysroot=/ --with-system-zlib \
--prefix=/usr/local \
--with-local-prefix=/usr/local
configure: WARNING: you should use --build, --host, --target
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
pkg.m4 should handle the system pkg-config, broken or not.
--
H.J.
