public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cygwin@sourceware.cygnus.com>
To: Brendan Simon <brendan@dgs.monash.edu.au>
Cc: CygWin32 <cygwin@sourceware.cygnus.com>,
	"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: Canadian build of Insight
Date: Tue, 17 Aug 1999 19:59:00 -0000	[thread overview]
Message-ID: <19990817230106.C2983@cygnus.com> (raw)
In-Reply-To: <37B9F8F7.6188FBFC@dgs.monash.edu.au>

On Wed, Aug 18, 1999 at 10:06:16AM +1000, Brendan Simon wrote:
>>I downloaded insight-19990802.tar.gz last night and manged to compile a
>>native linux version and a native-powerpc-eabi version (ie.
>>cross-debugger running on linux but targeting powerpc-eabi).  Great.
>>
>>I tried doing a Canadian build (build=i586-linux, host=i586-cygwin32,
>>target=powerpc-eabi).  It eventually died complaining that it couldn't
>>find termcap.h or tcap.h (one of these anyway).  Now I'm not sure if I
>>configured it wrong or am missing a file.  I think I used the
>following configure options
>(--with-headers=<newlib-path>/newlib/libc/include
>>--with-newlib) which may have confused it.  Do I need to use these
>>options ?  Does the canadian build use the header files from the native
>>cross-tools directories (eg.  /usr/local/gcc/powerpc-eabi/include in my
>>case) ?
>
>James Ingham replied with:
>
>>Anyway, newer versions of readline use termcap, so you will have to
>>have the termcap libraries in the target support for your cross
>>compiler.  Newer versions of Cygwin do include it (like the snapshots
>>from sourceware) so you should be able to copy the libtermcap bits from
>>there.  There should be appropriate configury bits there as
>well...

Actually, the B20.1 sources should include the libtermcap directory.
Are you saying that it isn't there?

>I had a look on the sourceware for the new cygwin sources.  I found
>lots of snapshots around 4MB in size.  I built my cygwin cross compiler
>following Mumit Khan's howto.  It said to download the Cygwin dev
>sources which are around 27MB in size.  I thought I needed an update of
>this but there is only one on sourceware and it is quite old (the same
>one that I have already got).  What is the difference between the dev
>sources and the other snapshot soureces ?  Which ones do I need to
>build an up to date cygwin package on a Linux host ?  I want to be able
>to build the latest Insight code.  Are there any other pacages I need.
>I don't really want to build on a Win32 box, but would like to know if
>any extra packages are required to do this (just incase I get real
>desperate).

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.

-chris

  reply	other threads:[~1999-08-17 19:59 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 [this message]
1999-08-17 20:39   ` Mumit Khan
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=19990817230106.C2983@cygnus.com \
    --to=cygwin@sourceware.cygnus.com \
    --cc=brendan@dgs.monash.edu.au \
    --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).