From: Stan Cox <scox@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: [SCM] master: Add -sysroot option to fhpd.
Date: Mon, 14 Jan 2008 20:33:00 -0000 [thread overview]
Message-ID: <1200342672.16575.112.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <478B96A6.3090509@redhat.com>
> Right on; it needs to construct what looks like an installed sysroot so
> that we're testing against how things will appear in a live system. Two
> extra things to consider though: how to get this data installed; and now
> to have it also built 32-bit.
I'm on this one now.
> can this be coded to just assume that there's a sysroot ("/" by default)?
>
> Given that the underlying Dwfl knows its sysroot, would it be both
> simpler and more consistent to use that, and to do so internally?
Say, that is a clever idea; I'll look into that.
prev parent reply other threads:[~2008-01-14 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080114051518.31275.qmail@sourceware.org>
2008-01-14 9:06 ` Mark Wielaard
2008-01-14 13:17 ` Stan Cox
2008-01-14 16:50 ` /an/absolute/path/program.debug; Was: " Andrew Cagney
2008-01-14 20:27 ` Stan Cox
2008-01-14 17:09 ` Andrew Cagney
2008-01-14 20:33 ` Stan Cox [this message]
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=1200342672.16575.112.camel@multics.rdu.redhat.com \
--to=scox@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).