Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199907040433.XAA23684@mercury.xraylith.wisc.edu>
To: Geoff Appleby <geoff AT topic DOT com DOT au>
cc: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: A few different questions. Long. 
In-Reply-To: Your message of "Sun, 04 Jul 1999 14:10:38 +1000."
             <377EDEBE DOT FFDAAA4A AT topic DOT com DOT au> 
Date: Sat, 03 Jul 1999 23:33:06 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Geoff Appleby <geoff AT topic DOT com DOT au> writes:
> Hello :)
> 
> I've been playing with Cygwin on NT Server 4.0 for the last couple of
> weeks, and a few questions have popped up
> that I haven't been able to get answers for - I'm expecting some of
> these to be unanswered since
> some have to do with programs downloaded from other peoples sites - but
> anyway....
> 
> Many programs that I try to install fail doing ./configure when looking
> for gcc's ld.  The only way i've got around
> this is to manually edit the script and specifiy my ld program.
> Any ideas?

This is a problem with older versions of gcc that changed the pathnames
to DOS style. My binaries do not have this particular problem. A work
around is the following:
  
  $ LD=/full/path/to/ld.exe <srcdir>/configure [...args...]

> I downloaded the latest release of ecgs from the egcs.cygwin site, and
> added the patch that
> was on...Mumit Kahn's???....pages.
> Make boostrap failed, but a simple make worked.  Is it possible to get
> the bootstrap to work?
> It failed doing a comparison of stage2 to stage3 I think.

You're right. I typically get compare errors on all c++ and f77 files,
but not on the C files. Don't know why. It's not a timestamp issue
since the differences are much further away than where the timestamps
are (the comparison does skip 16 bytes to avoid the issue).

I don't know the answer, sorry. However, GCC does seem to work. This
is the way a few folks do it: 

  $ [configure]
  $ make 
  $ make install
  $ make clean
  [ repeat `make; make install; make clean' a few times ]

> Both with the gcc that comes with the cygwin download, and the latest
> egcs i compiled the other
> day, when configure scripts check for whether shared objects can be
> created, it says no.
> Is this where I start learning how to make dll's and stuff?

http://www.xraylith.wisc.edu/~khan/software/gnu-win32/dllhelpers.html

> If a program I compile breaks, and writes a core file (eg,
> MyProg.exe.core), is just the
> gdb that came with the cygwin download unable to read core files, or is
> it just not possible
> on cygwin?

The core files are misnamed. They're not what you'd expect on a Unix
system. These are text files, so you can just take a look and see
what's in it.

[ more good questions that I can't answer ... ]

> Just what is Mingw32? Where can i read up on it?
> 

Start at http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ and
follow along. 

> Sorry for all the questions :)

That's how we learn. Since you're just starting out, you may want also
want to start by searching the mail archives (it's been sick due to
DJ Delorie's ISP problem, but hopefully up by now).

All the questions you've asked are answered there, albeit it takes 
while to go through the archives.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com