public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28500] Failure to find libgmp
Date: Tue, 08 Nov 2022 02:58:10 +0000 [thread overview]
Message-ID: <bug-28500-4717-vmmC1g2dwr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28500-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28500
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu.org
--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I found building with GMP to be useful too. Especially when doing Canadian
cross builds. Then you don't need to build GMP seperately for the target you
can just use the one that is newly built. Especially when it comes to doing
combined builds too (which I still do). I should figure out how to clean up my
patches and submit them upstream for this.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-08 2:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 18:34 [Bug build/28500] New: " 64m at tutamail dot com
2021-10-26 18:50 ` [Bug build/28500] " 64m at tutamail dot com
2021-10-26 18:52 ` 64m at tutamail dot com
2022-02-27 20:54 ` tromey at sourceware dot org
2022-03-06 9:55 ` 64m at tutamail dot com
2022-03-06 10:42 ` 64m at tutamail dot com
2022-03-06 10:44 ` 64m at tutamail dot com
2022-03-06 15:52 ` tromey at sourceware dot org
2022-03-06 15:54 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-03-06 16:09 ` tromey at sourceware dot org
2022-05-02 20:13 ` karel.gardas at centrum dot cz
2022-07-28 15:40 ` sourceware at boris dot nikolaus.name
2022-07-28 16:02 ` simon.marchi at polymtl dot ca
2022-11-08 2:58 ` pinskia at gcc dot gnu.org [this message]
2022-11-08 3:01 ` pinskia at gcc dot gnu.org
2022-11-08 7:26 ` pinskia at gcc dot gnu.org
2022-11-08 8:03 ` pinskia at gcc dot gnu.org
2022-11-08 16:30 ` pinskia at gcc dot gnu.org
2022-12-21 16:51 ` cvs-commit at gcc dot gnu.org
2022-12-21 16:55 ` pinskia at gcc dot gnu.org
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=bug-28500-4717-vmmC1g2dwr@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).