mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Reinoud Koornstra <>
To: Rich Felker <>
Subject: Re: [musl] Gmp not included in default musl build
Date: Mon, 14 Aug 2023 17:44:13 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hi Rich,

Thanks for your answer. I just compiled and installed gmp with the musl
compiled gdb from your build process  Now I was able to compile gdb 13.2
fine. Even created a statically linked gdb which is easier to use. Thanks,

On Sat, Aug 12, 2023, 6:43 PM Rich Felker <> wrote:

> On Fri, Aug 11, 2023 at 05:44:12PM -0700, Reinoud Koornstra wrote:
> > Hello everyone,
> >
> > I'm building musl and a musl gdb by git cloning musl-cross-make.git
> > After fetching some manual downloads, the building and installing goes
> well.
> > After that I'm building gdb, but it seems to want gmp as well and it
> > doesn't come by default with the cross make of musl. Any good way to add
> > this?
> > Thanks,
> mcm's scope is producing a toolchain, not an extended library
> ecosystem for the target. Once you have a cross compiler, it should be
> possible to use it to build any further libraries you might want, like
> gmp, and either install them into the toolchain's sysroot or install
> them in some other location specific to the project you're building
> with the cross toolchain, then tell the build systems for programs you
> want to build (like gdb) to look there for them.
> Rich

[-- Attachment #2: Type: text/html, Size: 1650 bytes --]

      reply	other threads:[~2023-08-15  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  0:44 Reinoud Koornstra
2023-08-13  1:43 ` Rich Felker
2023-08-15  0:44   ` Reinoud Koornstra [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 NNTP newsgroup(s).