From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Build for mingw32 and i686 on x86_64 observations
Date: Wed, 24 Mar 2010 20:21:00 -0000 [thread overview]
Message-ID: <ho9a3p$l8a$1@dough.gmane.org> (raw)
First off, I want to point out that I can build the very recent cvs head
for an embedded arm application but it doesn't run correctly in that the
insight gui does not reflect the actual location of the PC while
debugging/stepping (the green highlighted line never moves). This is
regarless of whether the tk/tcl is system supplied or insight's own.
Insight 6.8 does not have this problem. So I tried to build 6.8.1 to see
how it does. With 6.8 there were kludges I had to do to get it to build
and now those don't seem to be required when built on x86_64 (and
probably i686). I also did a cross build on x86_64 for i686/32-bit and
it worked with some effort:
additional configure options:
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu \
CFLAGS="-m32" LDFLAGS="-m32"
and in files tcl(and tk)/unix/configure had to add $CFLAGS like this:
CC="$CC -pipe $CFLAGS"
to fix a build error.
But when build with i686-pc-mingw32-gcc toolchain (fedora 12 yum), the
same (windows specific) kludges as before were required (syntax errors
in window specific tck/tk code regarding dde and registry that can be
commented out).
However, with mingw32 I had to build/install then build/install again to
get insight.exe to appear at install/bin. It seems that in the install
directory under lib there needs to exist *at compile time* tkConfig.sh
and tclConfig.sh. So you have to make clean all, make install, then make
clean all, make install again when you are starting with an empty
install directory. So if you keep install/lib/tclConfig.sh and
tkConfig.sh between compiles (don't completely clean the install dir)
you are ok the next time.
-gene
next reply other threads:[~2010-03-23 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 20:21 Gene Smith [this message]
2010-03-31 5:26 ` 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='ho9a3p$l8a$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).