From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andreas Schwab <schwab@suse.de>
Cc: Nemo Nusquam via Gdb <gdb@sourceware.org>,
Nemo Nusquam <cym224@gmail.com>
Subject: Re: Unable to build GDB 13.1 on Solaris 11.3 Sparc
Date: Thu, 09 Mar 2023 11:37:02 +0100 [thread overview]
Message-ID: <yddlek66wj5.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <mvma60mgxe7.fsf@suse.de> (Andreas Schwab's message of "Thu, 09 Mar 2023 09:08:16 +0100")
Andreas Schwab <schwab@suse.de> writes:
> On Mär 08 2023, Rainer Orth wrote:
>
>> If you're building from the gdb 13.1 tarball, you can omit those. Btw.,
>> --disable-binutils is harmful: gdb depends on libbfd and won't link
>> without, as you've discovered.
>
> --disable-binutils does not disable building bfd (binutils is just
> another consumer of bfd, like gdb), and will not do any harm.
True, sorry for the confusion. However, my point stands: none of those
--disable-* options are needed when building from a tarball, and keeping
configure lines as simple as possible unless proven otherwise has more
often than not proven to help things.
It's only when you build from a git checkout that they help reduce build
time, but still aren't strictly necessary.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2023-03-09 10:37 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 [this message]
2023-03-09 18:45 ` Nemo Nusquam
2023-03-08 22:43 ` Andrew Pinski
2023-03-09 18:20 ` Nemo Nusquam
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=yddlek66wj5.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=cym224@gmail.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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).