From: Mumit Khan <khan@xraylith.wisc.EDU>
To: cygwin@sourceware.cygnus.com
Cc: Brendan Simon <brendan@dgs.monash.edu.au>,
"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: Canadian build of Insight
Date: Tue, 17 Aug 1999 20:39:00 -0000 [thread overview]
Message-ID: <199908180338.WAA11166@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <19990817230106.C2983@cygnus.com>
Chris Faylor <cygwin@sourceware.cygnus.com> writes:
>
> I'm not sure why you're not just downloading the prebuilt binaries
> from Mumit's site. It would save you a lot of time, it seems.
>
I believe Brendan is looking at supporting other targets, so needs to
build it locally.
Brendan, the easiest way to get the runtime support is find a machine
with Cygwin installed, and just grab the includes and libraries from
/Cygnus/cygwin-b20/H-i586-cygwin32/{include,lib} and you should be all
set.
If you want to build it locally without having to download the whole
bit, here's how (untested, but the basics are there ;-): download
the following "split" components from sourceware Cygwin site[1]:
toplevel.tar.bz2
config.tar.gz2
etc.tar.gz
include.tar.gz
libiberty.tar.gz
newlib.tar.gz
winsup.tar.gz
[1] ftp://sourceware.cygnus.com/pub/cygwin/cygwin-latest/src-by-top-dir/
Now unpack all of this in some directory, say cygwin-b20 and build/install
using your cross-compiler. Of course, unless you already have cross
compiler going, there may be a chicken and egg problem -- to build the
cross-compiler, you need the runtime; to build the runtime, you need to
the cross-compiler. If you already have a cross-compiler, you should
already have the runtime, right?
Since you may need termcap, also download the libtermcap.tar.bz2, which
has some modifications to support "cygwin" terminal type.
Regards,
Mumit
next prev parent reply other threads:[~1999-08-17 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 17:06 Brendan Simon
1999-08-17 19:59 ` Chris Faylor
1999-08-17 20:39 ` Mumit Khan [this message]
1999-08-17 21:36 ` Brendan Simon
1999-08-17 22:19 ` Andrew Cagney
1999-08-18 15:31 ` Chris Faylor
1999-08-18 15:49 ` Chris Faylor
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=199908180338.WAA11166@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=brendan@dgs.monash.edu.au \
--cc=cygwin@sourceware.cygnus.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).