Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: path to find libcc1.so?
Date: Sat, 13 Dec 2014 00:22:00 -0000	[thread overview]
Message-ID: <CADPb22SpZAozZmtq+QMwndmi2mZpD2QF221ZpLSszr0cS0+gEw@mail.gmail.com> (raw)

Hi.

I was reading the new "compile" code and a question occurred to me.
Do we want to give the user a parameter to specify the path of libcc1.so?
(say if it's in a non-standard location)
Or is the plan to tell users to use existing mechanisms
(LD_LIBRARY_PATH, et.al.)?

[If we provide a parameter, presumably we'll then need to do safe-path-checking,
but we already have code for that for libthread_db.]


             reply	other threads:[~2014-12-13  0:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13  0:22 Doug Evans [this message]
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
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=CADPb22SpZAozZmtq+QMwndmi2mZpD2QF221ZpLSszr0cS0+gEw@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.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