From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: undefined reference to `set_breakpoint'
Date: Fri, 19 Mar 2010 04:32:00 -0000 [thread overview]
Message-ID: <hnsbt3$662$1@dough.gmane.org> (raw)
In-Reply-To: <4BA11802.8050909@redhat.com>
Keith Seitz wrote, On 03/17/2010 01:57 PM:
> Do you want to test the attach patch? [I'm off the rest of the week, or
> I would probably have occasion to put it through its paces.]
>
> Let me know if this works -- it was okay in preliminary testing.
>
> Keith
Built OK on/for f12-64bit native. Tried my build for mingw32 (using f12
cross compiler pkg that works OK for insight 6.8) and see this error
when entering the itcl directory and apparently trying to "make all":
i686-pc-mingw32-windres -o wish.res.o --include
"../../../insight_sources/tk/win/../generic" --include
"/home/gene/addons/insight-cvs/insight_sources/tcl/generic" --include
"../../../insight_sources/tk/win/rc"
../../../insight_sources/tk/win/rc/wish.rc
i686-pc-mingw32-gcc -g -O2 -D__USE_MINGW_ACCESS winMain.o
"/home/gene/addons/insight-cvs/insight_build/tcl/win/libtcl84.a"
libtk84.a -lgdi32 -lcomdlg32 -limm32 -lcomctl32 -lshell32 \
wish.res.o -o wish84.exe -mwindows -mwin32
make[3]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/tk/win'
make[2]: Leaving directory `/home/gene/addons/insight-cvs/insight_build/tk'
make[2]: Entering directory
`/home/gene/addons/insight-cvs/insight_build/itcl'
Making all in itcl
make[3]: Entering directory
`/home/gene/addons/insight-cvs/insight_build/itcl/itcl'
make[3]: *** No rule to make target `all'. Stop.
make[3]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/itcl/itcl'
Making all in itk
make[3]: Entering directory
`/home/gene/addons/insight-cvs/insight_build/itcl/itk'
make[3]: *** No rule to make target `all'. Stop.
make[3]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/itcl/itk'
Making all in iwidgets
make[3]: Entering directory
`/home/gene/addons/insight-cvs/insight_build/itcl/iwidgets'
make[3]: *** No rule to make target `all'. Stop.
make[3]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/itcl/iwidgets'
make[3]: Entering directory
`/home/gene/addons/insight-cvs/insight_build/itcl'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/itcl'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/gene/addons/insight-cvs/insight_build/itcl'
make[1]: *** [all-itcl] Error 2
make[1]: Leaving directory `/home/gene/addons/insight-cvs/insight_build'
make: *** [all] Error 2
Configured like this:
./configure -v --quiet --prefix=$PREFIX \
--target=$TARGET --enable-interwork --enable-multilib \
--with-gnu-ld --with-gnu-as \
--disable-werror \
--host=i686-pc-mingw32 --build=i686-pc-linux-gnu \
CC="i686-pc-mingw32-gcc"
next prev parent reply other threads:[~2010-03-18 4:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 17:34 Gene Smith
2010-03-17 17:57 ` Tom Tromey
2010-03-18 3:39 ` Keith Seitz
2010-03-18 4:58 ` Gene Smith
2010-03-19 4:32 ` Gene Smith [this message]
2010-03-20 5:33 ` Hui Zhu
2010-03-30 8:29 ` Hui Zhu
2010-03-30 16:48 ` Hui Zhu
2010-03-31 3:20 ` Keith Seitz
2010-03-31 4:12 ` Hui Zhu
2010-03-31 4:28 ` Keith Seitz
2010-03-31 5:33 ` Hui Zhu
2010-03-31 5:37 ` Keith Seitz
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='hnsbt3$662$1@dough.gmane.org' \
--to=gds@chartertn.net \
--cc=insight@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).