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: <377EE948.FB80B57A@topic.com.au>
Date: Sun, 04 Jul 1999 14:55:36 +1000
From: Geoff Appleby <geoff AT topic DOT com DOT au>
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
CC: cygwin <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: A few different questions. Long.
References: <199907040433 DOT XAA23684 AT mercury DOT xraylith DOT wisc DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Mumit Khan wrote:

> > 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...]

geoff AT sekhmet[~]> gcc -print-prog-name=ld
C:/usr/local/bin/../lib/gcc-lib/i686-pc-cygwin32/egcs-2.91.66/../../../../i686-pc-cygwin32/bin/ld.exe

This was the latest code but with your patch.  What else did you do?..hang
on....
....a light bulb just appeared above my head....let me guess.....see next
bit.

> 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 ]

So finally make a latest gcc from a latest gcc.....I get it...tricky :)
Thanks.

> > 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.

Ahh..can i get programs to dump core like i'm used to?
I had a look, and it's not understandable by me :)

Thanks or your help :)

--Geoff


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