From: Doug Evans <dje@google.com>
To: Pedro Alves <palves@redhat.com>
Cc: Patrick Palka <patrick@parcs.ath.cx>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix GDBHISTSIZE test failure on i686
Date: Tue, 23 Jun 2015 17:42:00 -0000 [thread overview]
Message-ID: <CADPb22RqB1dE4cVaVz2C6_0J+OU1QNjTMBD4iqLSatNvJhP3hg@mail.gmail.com> (raw)
In-Reply-To: <5589952A.8010003@redhat.com>
On Tue, Jun 23, 2015 at 12:19 PM, Pedro Alves <palves@redhat.com> wrote:
>... note that assuming you
> install the 32-bit dependencies in your distro, you can easily build
> a 32-bit gdb on a 64-bit host. E.g., on x86-64 GNU/Linux, configure with:
>
> CC="gcc -m32" /path/to/configure \
> --host=i686-pc-linux-gnu \
> --build=i686-pc-linux-gnu \
> --target=i686-pc-linux-gnu
--host and --target can be elided here.
next prev parent reply other threads:[~2015-06-23 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 14:31 Patrick Palka
2015-06-23 14:46 ` Patrick Palka
2015-06-23 17:19 ` Pedro Alves
2015-06-23 17:42 ` Doug Evans [this message]
2015-06-23 19:36 ` Patrick Palka
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=CADPb22RqB1dE4cVaVz2C6_0J+OU1QNjTMBD4iqLSatNvJhP3hg@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=patrick@parcs.ath.cx \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).