From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Nat! <nat@mulle-kybernetik.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Problem building the gdb-14-branch probably due to GMP
Date: Mon, 18 Mar 2024 15:17:50 +0000 [thread overview]
Message-ID: <MN2PR11MB456602C28BDF2D07D07ACEEB8E2D2@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <09734b18-ceb2-4f72-ac1c-6dbb26a41ea4@mulle-kybernetik.com>
> -----Original Message-----
> From: Gdb <gdb-bounces+felix.willgerodt=intel.com@sourceware.org> On Behalf
> Of Nat!
> Sent: Montag, 18. März 2024 16:03
> To: gdb@sourceware.org
> Subject: Problem building the gdb-14-branch probably due to GMP
>
> When I build a somewhat slimmed down gdb, I get the following error:
>
> ```
> CXX init.o
> CXXLD gdb
> ./libtool: line 5209: cd: no/lib: No such file or directory
> libtool: link: cannot determine absolute directory name of `no/lib'
> make[2]: *** [Makefile:2186: gdb] Fehler 1
> make[2]: Verzeichnis „/home/src/srcL/gdb-14-branch/gdb“ wird verlassen
> ```
>
> From the Makefile I deduced that this has something to do with GMP,
> which I don't need, so I configured that out. But it made no difference.
Both GMP and MPFR are mandatory to build GDB nowadays:
https://sourceware.org/gdb/current/onlinedocs/gdb.html/Requirements.html
But yes, the error message is not so nice if you don't know about that.
Felix
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2024-03-18 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:02 Nat!
2024-03-18 15:17 ` Willgerodt, Felix [this message]
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=MN2PR11MB456602C28BDF2D07D07ACEEB8E2D2@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.com \
--cc=gdb@sourceware.org \
--cc=nat@mulle-kybernetik.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).