Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/Command line tools/make    [ Add a report in this area ]  
Report #:  8209   Status: Reported
MAKE issues under windows XP
Project:  C++BuilderX/BC++ 2005 Build #:  unsure
Version:    1.0 Submitted By:   Hal Aljibury
Report Type:  Basic functionality failure Date Reported:  5/18/2004 10:10:09 AM
Severity:    Serious / Highly visible problem Last Updated: 9/3/2004 5:20:39 PM
Platform:    All versions Internal Tracking #:  
Resolution: None (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: 5
Description
Make will fail to operate on a makefile, crashing almost immediately with "Error 1"

One line of text (not two, for some reason) can be echoed before make terminates.

Problem is seen with make 3.7 as well as 5.2
Steps to Reproduce:
I am running windows XP, with windriver's DIAB compiler, and borland MAKE v. 3.7 (or 5.2, both have same issue)

I am unsure as to whether it is an issue with MAKE or the compiler I'm using, but
I'm leaning towards make, because the compiler never gets called once the problem is initiated.

steps: 1. Make is invoked, and things start happening.
2. The compilation filelist is echoed into a link.lst file.
3. Rules are invoked to call the compiler for each file in the link file.
4. Up until this point, everything runs perfectly.
5. An error (syntax, type mismatch, whatever) occurs, and compilation stops.
6. When compilation stops the error is "** Error 1 ** deleting BLAH"
7. At this point, things seem to have gone nuts.  
8. When make is again invoked, it immediately crashes with the same error,
   after one line of text is echoed (in my case, "@echo BUILDING BLAH"...)
9. Even if the syntax error is fixed, nothing happens because the compiler is never
   again invoked.
Workarounds
The workaround I've come up with is to open another command shell
and run make from that window.  If there are no bugs in the program,
everything gets compiled.

I'm guessing that when make terminates abruptly, some files that were automatically
closed under windows2000 are no longer treated the same way by XP (or substitute the word 'files' for windows objects, handles, etc.  I'm not entirely up on the inner workings of windows)
I'm leaning against the compiler being at fault because make never
reaches the point where it attempts to execute it again.
Attachment
None
Comments

Hal Aljibury at 5/18/2004 10:38:25 AM -
Problem also exists with the Sierra 68K compiler

Server Response from: ETNACODE01