[bug #41730] Make doesn't show text for error messages when using the Microsoft C runtime

2014-02-28 Thread anonymous
URL:
  http://savannah.gnu.org/bugs/?41730

 Summary: Make doesn't show text for error messages when using
the Microsoft C runtime
 Project: make
Submitted by: None
Submitted on: Fr 28 Feb 2014 09:34:05 UTC
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: 4.0
Operating System: MS Windows
   Fixed Release: None
   Triage Status: None

___

Details:

Make doesn't show the text for error messages when compiled with the Microsoft
C++ compiler (Visual Studio 2010 in my case). This is because the
msc_vsnprintf function defined just for this case isn't actually used. The
following patch fixes the issue:

--- output.c.orig   2014-02-28 10:33:00.909575093 +0100
+++ output.c2014-02-28 10:32:21.383192857 +0100
@@ -61,7 +61,7 @@
 #endif
 #ifdef _MSC_VER
 # define va_copy(_d, _s) ((_d) = (_s))
-# define snprintf msc_vsnprintf
+# define vsnprintf msc_vsnprintf
 static int
 msc_vsnprintf (char *str, size_t size, const char *format, va_list ap)
 {




___

Reply to this item at:

  http://savannah.gnu.org/bugs/?41730

___
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make


[bug #41730] Make doesn't show text for error messages when using the Microsoft C runtime

2014-02-28 Thread Christian Boos
Follow-up Comment #1, bug #41730 (project make):

Duplicate of bug #40227 which is already fixed in git.

You'll soon realize that there are some other issues with stock 4.0 when it's
built with msvc, so better go with the latest in git ;-)

___

Reply to this item at:

  http://savannah.gnu.org/bugs/?41730

___
  Message sent via/by Savannah
  http://savannah.gnu.org/


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make


Test harness on VMS working, 58 tests currently failing.

2014-02-28 Thread John E. Malmberg
I have the test harness apparently working on VMS.  I need to fix up the 
DCL command procedure that is needed set up a number of foreign

commands needed by it before submitting a patch.

If no one else is interested in immediately running the test harness on 
VMS, I can wait on submitting a patch until I determine what is causing 
all the test failures.


So far it will require:
   Perl 5.18.1 or later.
   GNV 2.1.3 or later.
   Bash 4.2.45 or later.
   Coreutils 8.21 or later.

This limits running the test harness on Alpha/VMS 8.3 and 8.4 and IA64 
VMS 8.4.


58 Tests in 103 Categories Failed (See .diff* files in work dir for 
details) :-(


As there appears to be 111 log files, this is just less than half the 
tests passing.


I still need to investigate all of these failures.

The features/archives test fails because the GNV AR utility requires 
real VMS object files at this time, and the test just creates some 
files.  I will need to adjust the test setup section for VMS.


Some of the other tests are failing because the VMS sets argv[0] 
differently than what is expected.  I have a fix from the Bash 4.2.45 
port that will handle that.


3 tests timed out after 5 seconds.


Here is an example of a passing test.
EAGLE perl run_make_tests.pl features/comments
--
  Running tests for GNU make on VMS
   GNU Make 4.0.90
--

Clearing /lcl_root/make/tests/work...
Making work dirs...

features/comments ... ok (1 passed)

1 Test in 1 Category Complete ... No Failures :-)

Regards,
-John


___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make