public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Tomas Dahle <zionic@omnidimension.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Can not view source under windows
Date: Fri, 28 Feb 2003 20:40:00 -0000	[thread overview]
Message-ID: <1046457152.1490.5.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <oprlawnrqgpmeskb@smtp.online.no>

On Fri, 2003-02-28 at 02:56, Tomas Dahle wrote:
> And just because I'm curious, does ./configure and make in cygwin using gcc 
> 3.2 work? After I got all the tools it missed, I ended up with a compile 
> error. I just want to know if its doing something wrong, or if ./configure 
> and make simply does not do the job on cygwin.

There is only one trick to compiling right now, largely because I keep
forgetting to "fix" it. If your source directory contains the "tix"
directory, REMOVE it before running configure.

Here's how I build insight, regardless of host platform:

$ cvs co insight+dejagnu
[time passes
$ ls
src/
$ mkdir cygwin  <-- or linux or hpux or whatever host I'm on; if I do a
                    cross, I use "cygwin-ppc" or "cygwin-mips-elf" etc
$ cd cygwin
$ CFLAGS="-g" ../src/configure --prefix=`pwd`/built \
    --exec-prefix=`pwd`/built/H-i686-pc-cygwin
$ make all-gdb
$ make install-gdb

That's it. There is no real magic (the tix thing excepted right now).

In fact, I'm attempting to configure and build it right now on cygwin
using this procedure.

Keith


  parent reply	other threads:[~2003-02-28 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28 17:24 Tomas Dahle
2003-02-28 18:26 ` Christopher Faylor
2003-03-02  0:27   ` Tomas Dahle
2003-03-02  2:08     ` Heiko Gerdau
2003-03-03  0:24     ` Keith Seitz
2003-02-28 20:40 ` Keith Seitz [this message]
2003-03-01 20:37   ` 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=1046457152.1490.5.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=zionic@omnidimension.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).