From: Keith Seitz <keiths@redhat.com>
To: Gene Smith <gds@chartertn.net>
Cc: insight@sources.redhat.com
Subject: Re: 20090609-cvs bad on linux (build fail cygwin)
Date: Fri, 12 Jun 2009 17:28:00 -0000 [thread overview]
Message-ID: <4A31F1FF.6060707@redhat.com> (raw)
In-Reply-To: <h0olqb$9uo$1@ger.gmane.org>
Gene Smith wrote:
> I built the current cvs head code on linux (fedora 8) OK (target arm)
> but when I run it I see nothing useful in the main "Source Window". I
> can set breakpoints, step, continue and stop but I never see the green
> highlight marker for the current position. Assembly and Mixed views show
> an empty screen.
I have been using 20090605-cvs in my daily work (on F10 -- using system
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?]
Try opening the debug window or enable logging (see the README). That
might provide some "insight" into what may be going wrong.
Remind me: what's your target's triple? arm-what? What target are you
using to run executables, simulator, a board?
Out of curiosity, if you open a console window in insight (when your
target is stopped at a breakpoint) and type "tk
gdb_target_has_execution" what does it return?
> Also, after unsuccessful build in cygwin with -mno-cygwin (mingw) and
> under msys shell (also mingw) I tried a straight cygwin build. It went a
> lot farther but eventually got this error:
I have never used mingw; I am glad you tried this under cygwin...
Tonight I updated to CVS HEAD and rebuilt the whole thing. It took
several hours (I only have a 500MHz Pentium III that runs Win2k -- I
*really* got to set up a virtualized host!), but my build succeeded.
I updated my cygwin installation immediately prior to configuring,
building, and installing:
$ CFLAGS="-g" ../src/configure
--prefix=/home/keiths/sources/insight/head/built
[snip]
$ make all-gdb install-gdb
[snip]
[I set the CFLAGS to "-g" so that I can debug the resultant executable,
if I need to. You need not specify it.]
There must be something magical about my machine that it works every
time... :-P
> make[3]: Entering directory
> `/cygdrive/c/insight_make/insight_build/tcl/cygwin'
> gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
> -DPACKAGE=\"libtcl_cygwin\" -DVERSION=\"8.4\" -DHAVE_GETCWD=1
> -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_TMPNAM=1
> -DHAVE_WAITPID=1 -DNO_VALUES_H=1 -DHAVE_UNISTD_H=1 -DUSE_TERMIOS=1
> -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_ST_BLKSIZE=1
> -DSTDC_HEADERS=1 -DNO_UNION_WAIT=1 -DNEED_MATHERR=1 -DRETSIGTYPE=void
> -DHAVE_SIGNED_CHAR=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_TM_ZONE=1 -I.
> -I../../../insight_sources/tcl/cygwin
> -I../../../insight_sources/tcl/cygwin/../generic
> -DTCL_LIBRARY='"/usr/local//lib"' -g -O2 -mno-win32 -c
> ../../../insight_sources/tcl/cygwin/../unix/tclUnixInit.c
> ../../../insight_sources/tcl/cygwin/../unix/tclUnixInit.c:66: error:
> missing terminating " character
> ../../../insight_sources/tcl/cygwin/../unix/tclUnixInit.c:66: error:
> parse error before ')' token
> ../../../insight_sources/tcl/cygwin/../unix/tclUnixInit.c:66: error:
> missing terminating " character
> ../../../insight_sources/tcl/cygwin/../unix/tclUnixInit.c:66: error:
> parse error before ';' token
Line 66 of tclUnixInit.c is (and the accompanying comment):
/*
* Directory in which to look for packages (each package is typically
* installed as a subdirectory of this directory). The symbol is
* defined by Makefile.
*/
static char pkgPath[sizeof(TCL_PACKAGE_PATH)+200] = TCL_PACKAGE_PATH;
What does your Makefile say the value of TCL_PACKAGE_PATH is? In my
build (cygwin/Makefile), this is defined:
TCL_PACKAGE_PATH = NONE/lib /home/keiths/insight/head/built/lib
I configured with --prefix=/home/keiths/insight/head/built, so this
looks okay. Right below this is the Makefile portion that uses this:
AM_CFLAGS = -DTCL_LIBRARY='"$(TCL_LIBRARY)"'
-DTCL_PACKAGE_PATH='"$(TCL_PACKAGE_PATH)"'
Does this look the same in your Makefile?
For this file on my cygwin box, the following build command was executed:
gcc -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
-DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE=\"libtcl_cygwin\" -DVERSION=\"8.4\" -DHAVE_GETCWD=1
-DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_TMPNAM=1
-DHAVE_WAITPID=1 -DNO_VALUES_H=1 -DHAVE_UNISTD_H=1 -DUSE_TERMIOS=1
-DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_ST_BLKSIZE=1
-DSTDC_HEADERS=1 -DNO_UNION_WAIT=1 -DNEED_MATHERR=1 -DRETSIGTYPE=void
-DHAVE_SIGNED_CHAR=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_TM_ZONE=1 -I.
-I../../../src/tcl/cygwin -I../../../src/tcl/cygwin/../generic
-DTCL_LIBRARY='"/home/keiths/sources/insight/head/built/share/tcl8.4"'
-DTCL_PACKAGE_PATH='"NONE/lib
/home/keiths/sources/insight/head/built/lib"' -g -mno-win32 -c
../../../src/tcl/cygwin/../unix/tclUnixInit.c
As you can see, both our builds have the define for TCL_LIBRARY (in your
build it is not set correctly for some reason -- this value is generated
by configure), yet only my build defines TCL_PACKAGE_PATH -- in yours it
is missing for some reason. Did you paste the entire command?
Keith
next prev parent reply other threads:[~2009-06-12 6:13 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 [this message]
2009-06-12 22:04 ` Gene Smith
2009-06-12 23:38 ` Gene Smith
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=4A31F1FF.6060707@redhat.com \
--to=keiths@redhat.com \
--cc=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).