public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
	"Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>
Cc: indu.bhagat@oracle.com, elena.zannoni@oracle.com
Subject: Re: [Mike Frysinger] Re: [PATCH, V3 10/15] gdb: sim: buildsystem changes to accommodate libsframe
Date: Fri, 4 Nov 2022 12:04:34 -0400	[thread overview]
Message-ID: <b920cab0-e970-e1a5-2297-1fbac590f222@simark.ca> (raw)
In-Reply-To: <877d0apw9p.fsf@oracle.com>

> It may be as easy as the following, plus start referring to libraries
> like ../libbacktrace/libbacktrace.la in CLIBS, plus the bits in
> configure.ac to search and SUBST LIBTOOL, etc.
> 
> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
> index c528ee5aa80..d554e62b698 100644
> --- a/gdb/Makefile.in
> +++ b/gdb/Makefile.in
> @@ -146,7 +146,7 @@ MAKEHTMLFLAGS =
>  # Set this up with gcc if you have gnu ld and the loader will print out
>  # line numbers for undefined references.
>  #CC_LD = g++ -static
> -CC_LD = $(CXX) $(CXX_DIALECT)
> +CC_LD = $(LIBTOOL) --tag=CC --mode=link $(CXX) $(CXX_DIALECT)

I'd be fine with that, especially if it simplifies other spots so we
don't have to do different things based on enable_static.

Simon


  reply	other threads:[~2022-11-04 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 12:02 Jose E. Marchesi
2022-11-04 13:59 ` Elena Zannoni
2022-11-04 14:46 ` Simon Marchi
2022-11-04 15:20   ` Jose E. Marchesi
2022-11-04 15:36     ` Jose E. Marchesi
2022-11-04 16:04       ` Simon Marchi [this message]
2022-11-05  8:25         ` Mike Frysinger

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=b920cab0-e970-e1a5-2297-1fbac590f222@simark.ca \
    --to=simark@simark.ca \
    --cc=elena.zannoni@oracle.com \
    --cc=gdb-patches@sourceware.org \
    --cc=indu.bhagat@oracle.com \
    --cc=jose.marchesi@oracle.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).