public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Godfrey <godfrey@io.nosc.mil>
To: gnu-win32@cygnus.com
Cc: godfrey@io.nosc.mil (Michael Godfrey)
Subject: Problems with make
Date: Fri, 30 May 1997 00:12:00 -0000	[thread overview]
Message-ID: <199705300129.SAA05781@io.nosc.mil> (raw)

I have encountered two problems with 'make'.  I'm running NT
v4.0, Cygnus B18.  All mounts are binary, /tmp is in place, I'm
the only user on the system, etc.

The first problem is that the make binary that came with the
B18 distribution outputs the following, no matter what I'm
trying to make:


$ make
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) In
     cygwin_except_handler
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) Exception trapped!
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) exception C0000005
     at 10029ACE
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) exception: ax 241F457
     bx 241E812 cx 45535500 dx 241F457
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) exception: si 241E838
     di 241F0EB bp 241E800 sp 241E7FC
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) exception is:
     STATUS_ACCESS_VIOLATION
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) Stack trace:
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 0: sp =
     0x241E630, pc = 0x1000CEC2
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 1: sp =
     0x241E64C, pc = 0x77F94072
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 2: sp =
     0x241E670, pc = 0x77F88A53
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 3: sp =
     0x241E6FC, pc = 0x77F75E82
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 4: sp =
     0x241E800, pc = 0x40817F
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 5: sp =
     0x241E878, pc = 0x406CD9
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 6: sp =
     0x241F1D4, pc = 0x1000C102
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 7: sp =
     0x241FF94, pc = 0x1000C113
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 8: sp =
     0x241FFA0, pc = 0x416309
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 9: sp =
     0x241FFB0, pc = 0x40103B
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 10: sp =
     0x241FFC0, pc = 0x77F1AFC1
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) frame 11: sp =
     0x241FFF0, pc = 0x0
(c:\usr\gnuwin32\b18\H-i386-cygwin32\bin\make.exe 3684) End of stack trace


So, I got and built GNU make v3.75 (using MSVC++ and nmake).  This
version of make has successfully made a variety of good executables,
although sometimes I get the following error when compiling:

     g++: Internal compiler error: program cc1plus got fatal signal 33

After which make stops.  However, the code compiles fine if I issue
the same g++ command interactively (e.g., from the bash command line
instead of from within a Makefile).

Has anyone else encountered these errors?  If so, have you found a
solution or a workaround?  Any help will be greatly appreciated.

Thanks.

-Mike Godfrey
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-05-30  0:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-30  0:12 Michael Godfrey [this message]
1997-06-04 12:20 Michael Godfrey
1997-06-17  1:32 Riccardo Daltoe
     [not found] <199706172355.QAA23579@io.nosc.mil>
1997-07-03  8:43 ` Riccardo D'Altoe'
1997-07-03 16:52   ` Jing-Hsien Chiang
1999-01-31 23:52 Gulyas Laszlo
2001-07-22  6:17 problems " Dave BT
2001-08-20 16:15 LPServ
2001-08-20 17:11 Schaible, Jörg
2001-08-20 17:45 netmgmt
2001-08-21  2:05 Schaible, Jörg

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=199705300129.SAA05781@io.nosc.mil \
    --to=godfrey@io.nosc.mil \
    --cc=gnu-win32@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).