From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Vyacheslav Petrishchev <vyachemail@gmail.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdbsupport: Fix setting up 'development' var.
Date: Tue, 25 Feb 2020 21:18:00 -0000 [thread overview]
Message-ID: <CAPTJ0XFpM-Nz99zvmTYPOq6xdeeCcRp8+RASW-o2RmH9EBpuMA@mail.gmail.com> (raw)
In-Reply-To: <43ef95f1-a57b-97c2-ad20-38b467f17460@gmail.com>
On Tue, Feb 25, 2020 at 2:33 PM Vyacheslav Petrishchev
<vyachemail@gmail.com> wrote:
>
> Since gdbsupport is now on top level, fixing setting up 'development' var
> in 'configure', thats prevent gbd build failure when development=false
> (undefined symbols (selftest) when linking).
Oh, that explains the error someone mentioned on IRC recently...
I can't approve patches, but it looks like you used Debian's autoconf
to regenerate the configure script, leading to extra changes. To avoid
that it is best if you install and use an unmodified upstream autoconf
directly, perhaps by installing with --prefix and running it from
there.
Christian
next prev parent reply other threads:[~2020-02-25 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 20:33 Vyacheslav Petrishchev
2020-02-25 21:18 ` Christian Biesinger via gdb-patches [this message]
2020-02-26 7:40 ` [PATCH v1] " Vyacheslav Petrishchev
2020-03-05 19:36 ` Simon Marchi
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=CAPTJ0XFpM-Nz99zvmTYPOq6xdeeCcRp8+RASW-o2RmH9EBpuMA@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=vyachemail@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).