From: Jan Beulich <jbeulich@suse.com>
To: Jerry Zhang Jian <jerry.zhangjian@sifive.com>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] contrib: add download_prerequisites script from GCC
Date: Thu, 17 Jul 2025 11:30:33 +0200 [thread overview]
Message-ID: <3b3d7232-4783-44c0-b621-9375b52e6e53@suse.com> (raw)
In-Reply-To: <3856A741-F62C-4207-B901-723BB393F71E@sifive.com>
On 17.07.2025 10:40, Jerry Zhang Jian wrote:
> It is required to specify the gmp and mpfr path without the patch
And gcc's and gdb's required / desired versions match (and will always do so)?
Also please don't send private replies for on-list discussions, and please
don't top-post.
Jan
> Configure error:
> Try the --with-gmp and/or --with-mpfr options to specify
> their locations. If you obtained GMP and/or MPFR from a vendor
> distribution package, make sure that you have installed both the libraries
> and the header files. They may be located in separate packages.
>
>> On Jul 17, 2025, at 16:38, Jan Beulich <jbeulich@suse.com> wrote:
>>
>> On 17.07.2025 10:32, Jerry Zhang Jian via Binutils wrote:
>>> Add new download_prerequisites from GCC source tree to simplify the
>>> build dependencies setup for building GDB.
>>
>> Oh, gdb. Cc-ing their patches mailing list. But then I'm still unclear
>> how much of an overlap there is between gdb's and gcc's prereqs.
>>
>> Jan
>
next prev parent reply other threads:[~2025-07-17 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250717075754.2857544-1-jerry.zhangjian@sifive.com>
[not found] ` <20250717083202.2949512-1-jerry.zhangjian@sifive.com>
2025-07-17 8:38 ` Jan Beulich
[not found] ` <3856A741-F62C-4207-B901-723BB393F71E@sifive.com>
2025-07-17 9:30 ` Jan Beulich [this message]
2025-07-22 4:56 ` Jerry Zhang Jian
2025-07-22 5:36 ` Jan Beulich
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=3b3d7232-4783-44c0-b621-9375b52e6e53@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jerry.zhangjian@sifive.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