From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: path to find libcc1.so?
Date: Sat, 13 Dec 2014 20:16:00 -0000 [thread overview]
Message-ID: <20141213201600.GA15686@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22Sjb+mgnp3fm06VPZLE_1u-iOStA-VcuHZAhPyBJB0R_w@mail.gmail.com>
On Sat, 13 Dec 2014 20:57:35 +0100, Doug Evans wrote:
> Early adopters and those who want to contribute may find it preferable
> to use, e.g., ~/.gdbinit.
>
> If this is something we eventually want to do, doing it now will help
> people we want/need.
>
> Plus it's, what, 10 lines of (real) code?
It is then questionable whether there should also be a GDB option where to
find the GCC driver. Currently gcc/libcc1/findcomp.cc searches it in $PATH.
Jan
next prev parent reply other threads:[~2014-12-13 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 0:22 Doug Evans
2014-12-13 7:53 ` Eli Zaretskii
2014-12-13 18:56 ` Jan Kratochvil
2014-12-13 19:57 ` Doug Evans
2014-12-13 20:16 ` Jan Kratochvil [this message]
2014-12-13 21:49 ` Doug Evans
2014-12-13 22:12 ` Doug Evans
2014-12-14 20:46 ` Jan Kratochvil
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=20141213201600.GA15686@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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