From: Syd Polk <spolk@redhat.com>
To: Mike D <mike@clockwork.freeserve.co.uk>
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Problem building Sourcenav under Cygwin (latest)
Date: Wed, 19 Jul 2000 09:42:00 -0000 [thread overview]
Message-ID: <3975DAFC.300F5154@redhat.com> (raw)
In-Reply-To: <006c01bff14e$5a3ca450$3f61883e@Workgroup>
We could host them until we get ours built. Can you point us to your ftp site?
Mike D wrote:
>
> >From: Ian Roxborough <irox@redhat.com>
> >
> > The key to getting the Windows version to build with Visual C++
> > is CC = cl. This is because they are a bunch of comparision
> > in the configure file that will not work if CC = cl.exe.
>
> >From : Syd Polk spolk@redhat.com
> >
> > You need to set CFLAGS to "-Z7 -Od" also. What kind of errors are you
> getting.
> >
> > >Actually, I wouldn't mind following the othe advice in the
> > >/snavigator/install/README.TXT file :
> > >
> > >"use the binary distributions" ;-)
> > >
> > >The README.TXT file mentions a binary called SNWindows20000421.exe, is
> this
> > >available anywhere ?
> >
> > No, it isn't. Unfortunately, it is unlikely to be done soon. Sorry!
>
> Thanks a lot, those changes made it work.
>
> I have zipped up a copy of my executables, would it make sense for them to
> be hosted on the Sourcenav ftp site ? (I would host them myself, but the
> GPL means I'd have to put up SN451.tag.gz as well, and my service provider
> only gives me 15 Mb :-/ )
>
> Thanks again,
>
> Mike
next prev parent reply other threads:[~2000-07-19 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4.2.0.58.20000717121622.00ca2c10@pop.cygnus.com>
2000-07-18 13:32 ` Mike D
2000-07-18 13:35 ` Syd Polk
2000-07-18 13:53 ` Ian Roxborough
2000-07-18 23:56 ` Mike D
2000-07-19 9:42 ` Syd Polk [this message]
2000-07-16 5:52 Mike Davies
2000-07-16 9:11 ` Mo DeJong
2000-07-16 12:33 ` Mike D
2000-07-16 13:14 ` 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=3975DAFC.300F5154@redhat.com \
--to=spolk@redhat.com \
--cc=mike@clockwork.freeserve.co.uk \
--cc=sourcenav@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).