public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Kai Ruottu <karuottu@freenet.hut.fi>
To: Cor van Loos <C_van_Loos@excite.com>
Cc: Insight@sourceware.cygnus.com
Subject: Re: Building Insight (2)
Date: Thu, 29 Jun 2000 15:47:00 -0000	[thread overview]
Message-ID: <395BD002.B85C6CD3@freenet.hut.fi> (raw)
In-Reply-To: <17962774.962279561504.JavaMail.imail@derby>

Cor van Loos wrote:
> 
> I downloaded the insight+dejagnu-2000-0612.tar.bz2 file and decompressed it.
> 
> After that I did the following:
> 
> bash-2.04$ mkdir win32
> bash-2.04$ cd win32
> bash-2.04$ ../insight/configure --target=h8300-hms

> $here/../../itcl/itcl/unix/itclsh.exe
> /win32/libgui/library/../../itcl/itcl/unix/itclsh.exe: not found
> 
> and that is where my make ends. I have tried this with several builds, older
> than 12-06-2000 and they all generate an error on a certain point.

 Recently I built both the 20000620 and 20000627 snapshots for Mingw host and
fr30-elf, h8300-hms (20000620) and mips64vr4100-elf (20000627) targets, just
to see that the Mingw-host support still works... The only problem seemed to
be that the icon resources are now somehow hided, my Win2k shows the executables
as 'console-only' apps and the 'Properties' says that there are no icons to
choose from. Perhaps there is some bug in my 'gdb/gdbtk/gdb.rc' after adding
more icons to it...

 I built them under Linux, so your problems seem to be related to the Cygwin
build environment, I'm quite sure there wouldn't be any problems with the
Cygwin host either, if building under Linux... Perhaps I'll try that soon, just
downloaded the 20000626 snapshots of Cygwin headers & libs, I have had the 1.1.2
ones for some time, but have tried them only for trying to build the Source
Navigator for Win32... This failed miserably, but after switching to Mingw as
the host, it shows some progress. The SN seems to be ported to Cygwin and MSVC
earlier, so I must try a compromise between them for Mingw...

> I don't know where to go next.

 I could email the 'insight-20000620' for H8/300 to you, but I'm not sure about
your motives... Do you want a working Insight for your H8/300 target or only to
build it? (no use for it afterwards...). If I should recommend a H8/300-target
Insight for Win32, I would choose the 4.18.x one (from 19991227) which I have put
for download... At least some people have said that it works... (I only try to
build these things sometimes...)

 Still there is the problem with the current HDI-systems... If you haven't the
older CMON monitor in your board, you have only a nice GDB with a GUI and with
a nice simulator. But how to communicate with the target board, that's the real
question...

Cheers, Kai


  parent reply	other threads:[~2000-06-29 15:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-29  4:52 Cor van Loos
2000-06-29  5:13 ` Mo DeJong
2000-06-29  5:45 ` Keith Seitz
2000-06-29 15:47 ` Kai Ruottu [this message]
2000-06-29 17:24 ` Jim Ingham
2000-06-29 17:34   ` Syd Polk
2000-06-29 17:37   ` Tom Tromey
2000-06-29 18:00     ` Jim Ingham
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28  0:21 Cor van Loos
2000-06-28  9:13 ` Syd Polk
2000-06-23  5:35 Cor van Loos
2000-06-23  5:57 ` Mo DeJong

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=395BD002.B85C6CD3@freenet.hut.fi \
    --to=karuottu@freenet.hut.fi \
    --cc=C_van_Loos@excite.com \
    --cc=Insight@sourceware.cygnus.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).