From: Frank McIngvale <frankm@HiWAAY.net>
To: cygwin <cygwin@sourceware.cygnus.com>
Subject: windres.exe error?
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <Pine.OSF.4.02.9903031044040.18891-100000@fly.HiWAAY.net> (raw)
Message-ID: <19990331194500.N6Op64KM03MBNZhCNxHaMrPGegkHgAP_irFu9ZOSS18@z> (raw)
In-Reply-To: <001101be6595$72ce0770$29acdfd0@InspirePharm.Com>
I'm getting what seems to be an out of memory error
when running an .rc through windres, but I'm suspicious
because of the huge allocation:
--------------------------------------------------------------------
windres.exe -i minimal.rc -o minimal_resources.o --include-dir \
/usr/local/wx/include --define __WIN32__ --define __WIN95__ --define \
__GNUWIN32__
[main] c:\cygnus\CYGWIN~1\H-I586~1\bin\windres.exe 1777 (0)
commit_and_inc: VirtualAlloc failed
windres.exe: Can not allocate 369098853 bytes after allocating 201318400
bytes
make: *** [minimal_resources.o] Error 1
---------------------------------------------------------------------
An allocation of 370 Mb to compile an .rc file seems a bit
excessive, doesn't it? I'll be glad to send the .rc file
to whomever, I just didn't want to spam the list.
This is under B20.1 with egcs 1.1.1. Did I miss an update
to windres.exe somewhere?
thanks!
frank
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-31 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-03 8:31 GCC Internal Compiler Error When Compiling with -pipe Suhaib M. Siddiqi
[not found] ` < 001101be6595$72ce0770$29acdfd0@InspirePharm.Com >
1999-03-03 8:48 ` Frank McIngvale [this message]
1999-03-31 19:45 ` windres.exe error? Frank McIngvale
1999-03-03 15:58 ` GCC Internal Compiler Error When Compiling with -pipe Chris Faylor
1999-03-31 19:45 ` Chris Faylor
1999-03-31 19:45 ` Suhaib M. Siddiqi
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=Pine.OSF.4.02.9903031044040.18891-100000@fly.HiWAAY.net \
--to=frankm@hiwaay.net \
--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).