This is the mail archive of the
insight@sourceware.org
mailing list for the Insight project.
Re: No insight executable with target=avr host=mingw
Eric Weddington wrote:
But I don't have an avr-insight.exe executable anywhere.
And when I run
'avr-gdb -i=insight' I get "Interpreter insight unrecognized."
Any idea what might be going on here? Or what I can do different?
How about "avr-gdb -w"? Any better?
Forgot to mention: I tried that to, with the result that the regular command
line GDB starting.
Hi Eric,
I was actually about to reply to your other mail when I saw this one :)
You need to use the attached patch and regenerate configure. It was
originally posted to this list by Keith Selz but I can't seem to find
the original mail to point you to :(
I'll dig out my full patchset for mingw and mail that to you later.
Unfortunately I've been having some problems getting a working Insight
6.5/6.6 when building with msys/mingw which is why I haven't hosted the
patches at devkitPro.
The main issue I'm having is that the tcl source in the insight tree
appears to be building a broken dll for me at present. When I start the
newly built Insight I get an application failed to initialise error but
if I replace tcl84.dll with the one from an earlier cvs build then
everything starts up ok. There are some other problems even with the
working dll but I'd rather get it working from a fresh build than mixing
& matching like this.
The main tcl patch is the one Andrew Stubbs posted to the list some time
ago which I updated for 6.5/6.6 which I suspected I might have got
wrong. Reverting this patch still gives the failed to initialise error
unfortunately. For reference Andrew's patch is here ->
http://sourceware.org/ml/insight/2005-q3/msg00052.html
Since Andrew seemed to have backported the fix in question from a later
version of tcl I attempted building from the main tcl sources. This
produces a working tcl84.dll in that Insight doesn't produce the failed
to initialise error. but unfortunately it just quits silently and I
haven't quite determined why as yet.
Does anyone on the list have any tips for investigating this problem
further. I've tried running the problematic insight through a known
working gdb but it seems unable to catch the initialisation error.
Dave
diff -Nbaur insight-6.5/configure.in insight-6.5-test/configure.in
--- insight-6.5/configure.in Tue May 2 01:16:50 2006
+++ insight-6.5-test/configure.in Sun Jul 9 04:24:40 2006
@@ -2018,7 +2018,7 @@
# Host dirs don't like to share a cache file either, horribly enough.
# This seems to be due to autoconf 2.5x stupidity.
-host_configargs="--cache-file=./config.cache --build=${build_alias} --host=${host_alias} --target=${target_alias} ${extra_host_args} ${baseargs}"
+host_configargs="${cache_file_option} --build=${build_alias} --host=${host_alias} --target=${target_alias} ${extra_host_args} ${baseargs}"
target_configargs=${baseargs}