From: Josef Wolf <jw@raven.inka.de>
To: gdb@sourceware.org
Subject: Re: Insight can't find iwidgets when built outside source directory.
Date: Tue, 20 Mar 2007 06:40:00 -0000 [thread overview]
Message-ID: <20070320063755.GD26951@raven.wolf.local> (raw)
In-Reply-To: <20070319194417.GA17489@caradoc.them.org>
On Mon, Mar 19, 2007 at 03:44:17PM -0400, Daniel Jacobowitz wrote:
> On Mon, Mar 19, 2007 at 08:34:20PM +0100, Josef Wolf wrote:
> > I'm trying to build insight-6.6 for cross-debugging.
> I recomment you send mail to the insight@sourceware.org list; they may
> be more able to help you.
Oh. I thought insight is covered by the gdb project since it is pretty
much woven into gdb.
> > mkdir build-arm ; \
> > ( cd build-arm ; \
> > CC=arm-elf-gcc CFLAGS=foo LDFLAGS=bar ../configure --host=arm-linux ;\
> > make
> > )
> > )
>
> If all you need is gdbserver here, you can run
> ../gdb/gdbserver/configure.
>
> Note: that is not general advice. It applies only to gdbserver, not
> to any other subdirectories of src.
Thanks.
Since I want both, gdb _and_ insight, I'll probably build gdb+gdbserver
from gdb sources, totally avoiding the mentioned problem. I just thought
it would make sense to fix the real problem.
prev parent reply other threads:[~2007-03-20 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 19:40 Josef Wolf
2007-03-19 19:44 ` Daniel Jacobowitz
2007-03-20 6:40 ` Josef Wolf [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=20070320063755.GD26951@raven.wolf.local \
--to=jw@raven.inka.de \
--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