public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Nemo Nusquam <cym224@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Unable to build GDB 13.1 on Solaris 11.3 Sparc
Date: Thu, 9 Mar 2023 13:20:19 -0500	[thread overview]
Message-ID: <054b1e04-e336-c7d2-80dd-a3d29a483142@gmail.com> (raw)
In-Reply-To: <CA+=Sn1=hLskn_PnS+r3jvT6Er8xRycmL8n_8fDLeo0LsFkZEvA@mail.gmail.com>

On 2023-03-08 17:43, Andrew Pinski wrote:
> On Wed, Mar 8, 2023 at 1:34 PM Nemo Nusquam via Gdb <gdb@sourceware.org> wrote:
>> I am trying (and failing) to build GDB 13.1 on Solaris 11.3 Sparc.
>>
>> Here is my configuration script.
>>
>> CXXFLAGS='-g3 -O0' \
>> CFLAGS='-g3 -O0' \
>> NM=/usr/bin/gnm \
>> SHELL=/usr/bin/bash \
>> AR=/usr/bin/gar \
>> AS=/usr/bin/as \
>> CC=/home/build/gcc/git/bin/gcc \
>> CXX=/home/build/gcc/git/bin/g++ \
>> ../configure \
>> --with-mpc=/usr/local \
>> --with-gmp=/usr/local \
>> --with-mpfr=/usr/local \
>> --enable-64-bit-bfd \
>> --enable-tui \
>> --with-curses \
>> --disable-bootstrap \
>> --disable-binutils \
>> --disable-ld \
>> --disable-gprof \
>> --disable-gprofng \
>> --disable-gold \
>> --disable-gas \
>> --disable-sim
>>
>> (Some flags taken from https://sourceware.org/gdb/wiki/BuildingNatively .)
>>
>> The makefile creates ./gdb inside the build directory and then stops as
>> follows:
>>
>> checking for libgmp... no
>> configure: error: GMP is missing or unusable
>> gmake[1]: *** [Makefile:11447: configure-gdb] Error 1
>> gmake[1]: Leaving directory '/home/build/opt/gdb-13.1/bld'
> This was a known issue in GDB 13.1, It has been fixed/changed on the
> trunk and will be included with GDB 14. For pre-GDB 14, the option you
> want to use for configure is --with-libgmp-prefix= . libmpfr is
> similar you need to use --with-libmpfr-prefix .
> These options are documented in the installation documentation for GDB
> 13 but they were not part of the toplevel configure which is why they
> were not mentioned there. The options --with-gmp= and --with--mpfr=
> were only originally used for building GCC (GCC, GDB, binutils [and
> newlib] all share the same toplevel configure/make file system) and
> this was why folks got confused and even more I made the fix for this
> to use these options also for GDB.

Thank you, Andrew.  I will try rebuilding as you suggest.

> This issue was recorded as
> https://sourceware.org/bugzilla/show_bug.cgi?id=28500 .
I tried searching but I erroneously assumed it was a Solaris problem and 
found nothing relevant.


> Thanks,
> Andrew Pinski

Thank you,
N.

[...]

      reply	other threads:[~2023-03-09 18:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 21:33 Nemo Nusquam
2023-03-08 22:19 ` Rainer Orth
2023-03-09  8:08   ` Andreas Schwab
2023-03-09 10:37     ` Rainer Orth
2023-03-09 18:45   ` Nemo Nusquam
2023-03-08 22:43 ` Andrew Pinski
2023-03-09 18:20   ` Nemo Nusquam [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=054b1e04-e336-c7d2-80dd-a3d29a483142@gmail.com \
    --to=cym224@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=pinskia@gmail.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).