From: Brendan Simon <brendan@dgs.monash.edu.au>
To: "Insight (GDB GUI)" <insight@sourceware.cygnus.com>,
Cross-GCC <crossgcc@cygnus.com>,
CygWin32 <cygwin@sourceware.cygnus.com>
Subject: Canadian build of Insight for Cygwin SUCCESS.
Date: Thu, 19 Aug 1999 18:04:00 -0000 [thread overview]
Message-ID: <37BCA9C4.574B8C95@dgs.monash.edu.au> (raw)
I have managed to build Insight targeted for powerpc-eabi and hosted on
cygwin. The build machine was a linux box of course :)
I had problems in the build with termcap.h not being found. I checked
the dev-cygwin source and found that there was a src/libtermcap
directory but nothing in the configure file. Also the full.exe does not
install any termcap files. Anyway, I did not know what to do with it so
I did the following.
* changed directory to src/libtermcap
* made a directory called BUILD and changed to it
* typed "../configure -- target=i586-cygwin32 --prefix=/usr/local/gcc
--program-prefix=i586-cygwin32- --with-gnu-as --with-gnu-ld -v
* typed "make all" and it compiled but it used the naitive compiler (ie.
linux) instead of i586-cygwin32-gcc. So I then typed "make
CC=i586-cygwin32-gcc all" and the correct compiler was used.
* ranlib was invoked on libtermcap.a but again the naitve version was
used so I had to run it manually with "i586-cygwin32-randlib
libtermcap.a"
* "make install" installed the files in /usr/local/gcc/lib and
/usr/local/gcc/include but this is also wrong. So I copied them to
/usr/local/gcc/i586-cygwin32/lib and /usr/local/cygwin32/include.
The canadian build of Insight now completes and a powerpc-eabi-gdb.exe
file is generated. I believe that this name is confusing. It should be
called powerpc-eabi-insight[.exe] as it is not the build of the official
gdb sources. I rename it on my system.
I haven't tried it to see if runs yet but I will do that today with the
wiggler BDM I have at work.
Cheers,
Brendan Simon.
reply other threads:[~1999-08-19 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=37BCA9C4.574B8C95@dgs.monash.edu.au \
--to=brendan@dgs.monash.edu.au \
--cc=crossgcc@cygnus.com \
--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).