From: Josef Wolf <jw@raven.inka.de>
To: gdb@sourceware.org
Subject: Insight can't find iwidgets when built outside source directory.
Date: Mon, 19 Mar 2007 19:40:00 -0000 [thread overview]
Message-ID: <20070319193420.GC26951@raven.wolf.local> (raw)
Hello!
I'm trying to build insight-6.6 for cross-debugging. Since gdbserver and
insight need different configure settings, I decided to configure+build
it outside insight's source directory. With this, insight complains
that it can't find iwidgets. When I configure and build it from withhin
its source directory, it works as expected.
How do I tell insight that it should search the iwidgets in its source
directory?
This is what I am currently doing:
tar xjvf insight-6.6.tar.bz2
( cd insight-6.6 ;\
mkdir build ; \
( cd build; \
CC= CFLAGS= LDFLAGS= ../configure --target=arm-linux --with-sysroot ; \
make
) ; \
mkdir build-arm ; \
( cd build-arm ; \
CC=arm-elf-gcc CFLAGS=foo LDFLAGS=bar ../configure --host=arm-linux ;\
make
)
)
Any ideas?
next reply other threads:[~2007-03-19 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 19:40 Josef Wolf [this message]
2007-03-19 19:44 ` Daniel Jacobowitz
2007-03-20 6:40 ` Josef Wolf
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=20070319193420.GC26951@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