From: "H.J. Lu" <hjl.tools@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "H.J. Lu via Binutils" <binutils@sourceware.org>,
Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
GDB <gdb-patches@sourceware.org>,
Aaron Merey <amerey@redhat.com>
Subject: Re: V2 [PATCH] PKG_CHECK_MODULES: Check if $pkg_cv_[]$1[]_LIBS works
Date: Tue, 28 Jul 2020 06:56:20 -0700 [thread overview]
Message-ID: <CAMe9rOry1ypDTmXQFPzS=J0rVzNS8XP_7kJxqJnW0cPN6d3PSQ@mail.gmail.com> (raw)
In-Reply-To: <87r1svyche.fsf@igel.home>
On Tue, Jul 28, 2020 at 6:51 AM Andreas Schwab <schwab@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.
next prev parent reply other threads:[~2020-07-28 13:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200502022903.175852-1-amerey@redhat.com>
[not found] ` <3d9da16939fa6b503188033b56d30531e03d5d2a.camel@redhat.com>
2020-05-05 21:23 ` [PATCH] config/debuginfod.m4: Use PKG_CHECK_MODULES Aaron Merey
2020-05-08 20:56 ` Tom Tromey
2020-07-16 22:17 ` Aaron Merey
2020-07-16 22:37 ` Aaron Merey
2020-07-19 15:43 ` Simon Marchi
2020-07-21 15:20 ` Tom Tromey
2020-07-21 18:11 ` Aaron Merey
2020-07-24 20:03 ` Aaron Merey
2020-07-25 16:01 ` H.J. Lu
2020-07-27 15:31 ` [PATCH] config/debuginfod.m4: Restore AC_CHECK_LIB check H.J. Lu
2020-07-27 16:11 ` Aaron Merey
2020-07-27 19:14 ` [PATCH] PKG_CHECK_MODULES: Check if $pkg_cv_[]$1[]_LIBS works H.J. Lu
2020-07-27 19:32 ` V2 " H.J. Lu
2020-07-28 10:45 ` H.J. Lu
2020-07-28 12:46 ` Simon Marchi
2020-07-28 13:33 ` H.J. Lu
2020-07-28 13:51 ` Andreas Schwab
2020-07-28 13:56 ` H.J. Lu [this message]
2020-07-28 14:01 ` Simon Marchi
2020-07-28 14:11 ` H.J. Lu
2020-07-28 14:34 ` Simon Marchi
2020-07-28 15:05 ` H.J. Lu
2020-07-28 15:13 ` Simon Marchi
2020-07-28 16:07 ` H.J. Lu
2020-07-28 16:28 ` Simon Marchi
2020-07-28 17:26 ` H.J. Lu
2020-07-28 17:43 ` Simon Marchi
2020-07-28 18:31 ` H.J. Lu
2020-07-28 18:47 ` Simon Marchi
2020-07-28 18:57 ` H.J. Lu
2020-07-28 14:54 ` Andreas Schwab
2020-07-28 13:53 ` H.J. Lu
2020-07-28 13:54 ` Simon Marchi
2020-07-28 12:54 ` Mark Wielaard
2020-07-28 13:27 ` [PATCH] PKG_CHECK_MODULES: Properly check " H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMe9rOry1ypDTmXQFPzS=J0rVzNS8XP_7kJxqJnW0cPN6d3PSQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=amerey@redhat.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox