From: N8TM@aol.com
To: azure@iki.fi
Cc: egcs@cygnus.com
Subject: Re: 19980707 built on win95/i686-pc-cygwin32
Date: Fri, 10 Jul 1998 20:04:00 -0000 [thread overview]
Message-ID: <90d75435.35a6b5e8@aol.com> (raw)
In a message dated 7/10/98 7:01:40 AM Pacific Daylight Time, azure@iki.fi
writes:
> If the build process required something out of the ordinary,
> what about making patches of the required changes and post them
> here so that future snapshots could be compiled out of the box
On win95/cygwin32, the search path through gcc/config was not always followed
from "auto-config.h", so the .h files in config/i386 were not being picked up.
That problem does not occur on NT, but misconfiguration re <inttypes.h> does.
Also, there are minor unnecessary annoyances due to failure to #undef macros
before changing them or unnecessary redefining of POSIX. Those and the
including of <wctype.h> instead of <wchar.h>
No, 64MB is not enough for satisfactory build performance on NT on a Novell
network with a virus checker active.
next reply other threads:[~1998-07-10 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-10 20:04 N8TM [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-07-12 9:18 N8TM
1998-07-12 8:15 N8TM
1998-07-12 0:41 N8TM
1998-07-12 0:41 ` Jeffrey A Law
1998-07-10 23:05 N8TM
1998-07-11 22:54 ` Jeffrey A Law
1998-07-10 0:33 N8TM
1998-07-10 7:01 ` Hannu Koivisto
1998-07-10 15:56 ` Joern Rennecke
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=90d75435.35a6b5e8@aol.com \
--to=n8tm@aol.com \
--cc=azure@iki.fi \
--cc=egcs@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).