From: "Phil Edwards" <devphil@my-dejanews.com>
To: "Cygwin List" <cygwin@sourceware.cygnus.com>
Subject: Re: egcs-2.9.66 (B20.1) errors
Date: Wed, 07 Apr 1999 08:51:00 -0000 [thread overview]
Message-ID: <PFLKELENMGDHAAAA@my-dejanews.com> (raw)
On Tue, 6 Apr 1999 16:40:43 Mumit Khan wrote:
>
>The only time I've seen is when running GCC with -mno-cygwin mode or using
>include path that has mingw32 include files before g++ include files. The
>Mingw32 header directory contains alloc.h, which should be deleted (and
>the contents moved into malloc.h), which causes this.
That's exactly the situation here. I am now beating
my head into pulp for not mentioning this: the specs
file being used is the same one that I sent to the
list a few days earlier, asking for comments. The
default mode is now "no-cygwin", and the mingw32
include path comes before all the others. Again, I
apologize for not mentioning that. Gee, ya think it
could make a difference...?
The difference in 'spces' is the only change. Honest.
>Can you please send me more info?
>
> $ env > bug.txt
> $ cygcheck -s -r >> bug.txt 2>&1
> $ gcc -c -v -save-temps foo.cc >> bug.txt 2>&1
>
>and email me bug.txt and foo.ii file.
I'll send them separately in a moment. I should point
out that I'll generally be using gcc by itself from a
DOS box. The only times I venture into bash are when
I need to build a GNU package, where I have to run
things like 'configure' et al.
Phil
It's gonna be one of /those/ weeks...
-----== Sent via Deja News, The Discussion Network ==-----
http://www.dejanews.com/ Easy access to 50,000+ discussion forums
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: "Phil Edwards" <devphil@my-dejanews.com>
To: "Cygwin List" <cygwin@sourceware.cygnus.com>
Subject: Re: egcs-2.9.66 (B20.1) errors
Date: Fri, 30 Apr 1999 18:32:00 -0000 [thread overview]
Message-ID: <PFLKELENMGDHAAAA@my-dejanews.com> (raw)
Message-ID: <19990430183200.tnckWnSBcW2bsUI_oK-N9S8JjAAguTRZ350zKx_tarY@z> (raw)
On Tue, 6 Apr 1999 16:40:43 Mumit Khan wrote:
>
>The only time I've seen is when running GCC with -mno-cygwin mode or using
>include path that has mingw32 include files before g++ include files. The
>Mingw32 header directory contains alloc.h, which should be deleted (and
>the contents moved into malloc.h), which causes this.
That's exactly the situation here. I am now beating
my head into pulp for not mentioning this: the specs
file being used is the same one that I sent to the
list a few days earlier, asking for comments. The
default mode is now "no-cygwin", and the mingw32
include path comes before all the others. Again, I
apologize for not mentioning that. Gee, ya think it
could make a difference...?
The difference in 'spces' is the only change. Honest.
>Can you please send me more info?
>
> $ env > bug.txt
> $ cygcheck -s -r >> bug.txt 2>&1
> $ gcc -c -v -save-temps foo.cc >> bug.txt 2>&1
>
>and email me bug.txt and foo.ii file.
I'll send them separately in a moment. I should point
out that I'll generally be using gcc by itself from a
DOS box. The only times I venture into bash are when
I need to build a GNU package, where I have to run
things like 'configure' et al.
Phil
It's gonna be one of /those/ weeks...
-----== Sent via Deja News, The Discussion Network ==-----
http://www.dejanews.com/ Easy access to 50,000+ discussion forums
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-04-07 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-07 8:51 Phil Edwards [this message]
1999-04-30 18:32 ` Phil Edwards
-- strict thread matches above, loose matches on Subject: below --
1999-04-08 10:02 Phil Edwards
1999-04-30 18:32 ` Phil Edwards
1999-04-06 14:25 Phil Edwards
1999-04-06 14:41 ` Mumit Khan
1999-04-30 18:32 ` Mumit Khan
1999-04-30 18:32 ` Phil Edwards
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=PFLKELENMGDHAAAA@my-dejanews.com \
--to=devphil@my-dejanews.com \
--cc=cygwin@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).