From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: RE: Disabling sysroot
Date: Wed, 04 Jun 2008 15:20:00 -0000 [thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BD4C@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <20080604151313.GA31914@caradoc.them.org>
/dev/null it is.
Thanks
-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org]
Sent: Wed 6/4/2008 11:13 AM
To: Marc Khouzam
Cc: gdb@sourceware.org
Subject: Re: Disabling sysroot
On Wed, Jun 04, 2008 at 09:34:02AM -0400, Marc Khouzam wrote:
> Hi,
>
> in the doc it says:
>
> If you want to use `solib-search-path' instead of
> `sysroot', be sure to set `sysroot' to a nonexistent directory to prevent GDB
> from finding your host's libraries.
>
> Is there a recommended way to turn off sysroot?
> I can set it to something like /what/are/the/odds/of/this/dir/actually/existing
> But it is not very elegant.
I use /dev/null, which will never be a directory.
There's no way to disable sysroot; setting it to empty is the same as
not setting it at all, i.e. use the host's libraries.
> Or is setting sysroot to anything not starting with a / sufficient?
A relative path may be a valid sysroot; GDB will search from its
current directory (there's no special check for absolute paths).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-06-04 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6D19CA8D71C89C43A057926FE0D4ADAA04291110@ecamlmw720.eamcs.ericsson.se>
[not found] ` <200805141603.35204.pedro@codesourcery.com>
2008-06-04 13:34 ` Marc Khouzam
2008-06-04 15:13 ` Daniel Jacobowitz
2008-06-04 15:20 ` Marc Khouzam [this message]
2008-06-04 17:38 ` Eli Zaretskii
2008-06-05 15:08 ` Marc Khouzam
2008-06-05 15:23 ` Daniel Jacobowitz
2008-06-05 16:10 ` Marc Khouzam
2008-06-05 16:12 ` Paul Koning
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=6D19CA8D71C89C43A057926FE0D4ADAA04E1BD4C@ecamlmw720.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=drow@false.org \
--cc=gdb@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