public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: 20090609-cvs bad on linux (build fail cygwin)
Date: Fri, 12 Jun 2009 23:38:00 -0000	[thread overview]
Message-ID: <h0ujd1$p3h$1@ger.gmane.org> (raw)
In-Reply-To: <h0u37b$8g1$1@ger.gmane.org>

Gene Smith wrote:
  > Going back to windows/cygwin I was able to build 6.8 and run insight 
6.8
> OK (pure cygwin, no mingw). Then I tried 6.8 on msys shell and it stops 
> pretty quick due to and error about MAKEINFO being missing or wrong 
> version. So I tried again under cygwin with -mno-cygwin and finally got 
> it make/install and run OK. Here is how I built it under cygwin as a 
> mingw32 executable:
> 
> insight_make
>     insight_sources
>         unpacked insight-6.8 tarball
>     insight_build (directory)
>     makeInsight.sh
> 
> makeInsight.sh (run from insight_make)looks like this:
> 
> #!/bin/sh
> export TARGET=arm-none-eabi
> export PREFIX=/cygdrive/c/Progra~1/Raisonance/Ride/arm-gcc
> export PATH=$PATH:$PREFIX/bin
> export PATH=$PATH:$PREFIX/$TARGET
> 
> #cd insight_build && rm -rf *
> #../insight_sources/configure -v --quiet --prefix=$PREFIX \
> #   --target=$TARGET --enable-interwork --enable-multilib \
> #   --with-gnu-ld --with-gnu-as
> #make all
> cd insight_build
> ../insight_sources/configure -v --quiet --prefix=$PREFIX \
>    --target=$TARGET --enable-interwork --enable-multilib \
>    --with-gnu-ld --with-gnu-as \
>    --host=i686-pc-mingw32 --build=i686-pc-cygwin \
>    CC="gcc -mno-cygwin" AR="ar"
> make
> make install
> <eof>
> 

I tried this again on cygwin using your CVS head code. For some reason 
it could not find a header file in insight_sources/tk/win when making 
libgui module. The search path in libgui/src/Makefile only pointed into 
tk/unix. So I manually changed the TK_INCLUDES macro in Makefile to 
include the win path:

TK_INCLUDES = -I/cygdrive/c/insight_make/insight_sources/tk/generic \ 
-I/cygdrive/c/insight_make/insight_sources/tk/win \  <--new
-I/cygdrive/c/insight_make/insight_sources/tk/unix

I don't know how configure sets this up. Maybe it doesn't realize this 
is a "win" build and should use the win includes instead of (or before) 
unix...??

Also, and this is not specifc to cvs HEAD, I frequently see this 
corruption in the generated Makefiles (looking with vim):

program_transform_name = s,^,arm-none-eabi^M-

I think maybe sed is doing this putting an extraneous newline or end of 
line character in when it is inserting a dash character. Maybe the 
cygwin sed is assumes dos style line endings, cr/lf ???. If I remove the 
^M and and make or make install again it is OK.

In this case the offending files were Makefiles under 
insight_build/sim/. Also, several Makefiles under insight_build/gdb had 
this problem. It detected the error during "make install" phase. All the 
Makesfiles that had to be modifed were unix according to vim.

I don't see this ^M problem building the same files with linux.

Ok, after fixing the ^M errors it installs OK and run as a windows "MZ" 
exe. But it has the exact same problem I saw on linux: no functionality 
in the main code frame display area. But the buttons at the top work OK.

I can still control gdb witht eh Console Window. Stopped at a bp I see 
this, as you asked about:

(gdb) tk gdb_target_has_execution
1

However, don't know what you mean by this:

"Try opening the debug window or enable logging (see the README). That 
might provide some "insight" into what may be going wrong."

FWIW, the register window seems to work but don't see a "debug" window. 
Also, nothing in the top level README about logging. Is this a configure 
option? (To reconfigure and build on my system also takes forever. :))

Also, you say:
"I have been using 20090605-cvs in my daily work (on F10 -- using 
*system* [my emphasis]  Tcl, Tk, etc), and I have not noticed your 
problems. Are you using the supplied versions of Tcl or the system 
versions? [i.e., Are src/tcl, src/tk, and src/itcl in your source tree?]"

When you say using "system" Tcl/Tk etc, do you mean the tcl/tk etc not 
included with insight? On windows, as far as I know, insight provides 
the only tcl, tk. How do you control which is used by insight? (On my 
linux there is an installed system tcl, tk in /usr somewhere.)

-gene










  reply	other threads:[~2009-06-12 22:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 19:04 Gene Smith
2009-06-12 17:28 ` Keith Seitz
2009-06-12 22:04   ` Gene Smith
2009-06-12 23:38     ` Gene Smith [this message]
2009-06-16 18:01 ` Gene Smith
2009-06-16 18:40   ` Keith Seitz
2009-06-16 18:48     ` Gene Smith
2009-06-16 18:53       ` Keith Seitz
2009-07-07  3:22         ` Gene Smith
2009-07-07  3:29           ` Gene Smith

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='h0ujd1$p3h$1@ger.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).