Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	"H.J. Lu via Binutils" <binutils@sourceware.org>,
	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 10:34:24 -0400	[thread overview]
Message-ID: <adf1f647-abb7-ed06-1ca7-bef4593b1d0a@simark.ca> (raw)
In-Reply-To: <CAMe9rOoH9bfAVgfFDh7++0VDTnQcNJG0ACQb5fy5cE3dnfvywg@mail.gmail.com>

On 2020-07-28 10:11 a.m., H.J. Lu wrote:
> On Tue, Jul 28, 2020 at 7:01 AM Simon Marchi <simark@simark.ca> wrote:
>>
>> On 2020-07-28 9:56 a.m., H.J. Lu wrote:
>>> 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
>>
>> So... is your build system a 32-bit one?  Why does the above say i686-pc-linux-gnu
>> and not x86_64-something?
>>
> 
> My system supports both -m32 and -m64.  Depending on CC, configure
> selects i686 or x86-64 target.

Can you clarify how this magic works, is this standard autoconf?  Because I am trying this
on Fedora, so pretty much the same setup as you, and I don't see this behavior:

$ /home/simark/src/binutils-gdb/configure CC="gcc -m32" CXX="g++ -m32"
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
...


And even if it worked, why would it set "build" to i686, it doesn't make sense.  The gcc you
compile with, and its environment, is still x86_64, not i686.

So *if* it works, it would be a shortcut for setting --host=i686-something, maybe.  So
regardless of how that above works, that doesn't remove the need to configure pkg-config
correctly for the host system.

If you don't want to learn about with pkg-config and deal with it, then please say "I think
we should not use pkg-config", and ideally give supporting points.  Please don't unilaterally
push patches just to paper over your own problems.  You just make it so that somebody will
need to untangle more mess later.

Simon


  reply	other threads:[~2020-07-28 14:34 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
2020-07-28 14:01                                     ` Simon Marchi
2020-07-28 14:11                                       ` H.J. Lu
2020-07-28 14:34                                         ` Simon Marchi [this message]
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=adf1f647-abb7-ed06-1ca7-bef4593b1d0a@simark.ca \
    --to=simark@simark.ca \
    --cc=amerey@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=schwab@linux-m68k.org \
    --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