> ===
> process_begin: CreateProcess(NULL, uname, ...) failed.
> make:
> process_begin: CreateProcess(NULL, uname -a, ...) failed.
> make:
> process_begin: CreateProcess(NULL, cygpath C:\zzz_13.12.1_gener
> make:
> process_begin: CreateProcess(NULL, p
Paul Smith wrote:
> I fixed this one locally a couple of days ago; sorry for not pushing.
> I'll do that shortly.
>
> I don't think this change is sufficient because if output_sync !=
> &make_sync then make_sync is never dumped with the change below.
I had assumed it wasn't a problem because mak
Hello!
This is part of my spawn-patch for Make. The purpose of this piece is to
add missing support for output-sync option to spawn()-based flavors
(currently only EMX).
Tested together with the rest of spawn-patch under Cygwin, works fine.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Elec
Hello!
I am trying to rebuild GIT version of Make, however .po files are missing
in the repository. Is this intentional ? I have copied them over from my
4.0-2 archive. But where are they originally stored ?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
I showed some of the output when this new windows/dos make is run
from the command prompt, in the original message.
Why not just post a step by step description of how to compile
make in Windows 7 64, post some output of its operation,
and clear everything up ?
Also, can you describe what the ser
On Mon, Jan 13, 2014 at 9:56 PM, Christian Eggers wrote:
> Is there a workaround for this? Using explicit rules seems to be difficult in
> my case because some objects are built from .c sources, other from .cpp.
> Is there a better way instead of this:
>
> SOURCES_C := foo.c
> SOURCES_CPP := bar.c
Am Montag, 13. Januar 2014, 17:20:43 schrieb Paul Smith:
> On Mon, 2014-01-13 at 22:23 +0100, Christian Eggers wrote:
> > In Makefile 2 my intention was to state that foo.o depends on some
> > generated header which must be generated first (might be in another
> > rule). But I didn't want to change
I fixed this one locally a couple of days ago; sorry for not pushing.
I'll do that shortly.
I don't think this change is sufficient because if output_sync !=
&make_sync then make_sync is never dumped with the change below.
On Tue, 2014-01-14 at 06:21 +0100, Frank Heckenbach wrote:
> Oliver Kiddl
Oliver Kiddle wrote:
> Given the following Makefile, the output from the error function is
> being lost when the gmake 4 output-sync is enabled:
>
> [...]
With assertions active I even get this error:
% make -O
make: main.c:3409: die: Assertion `output_context == &make_sync'
failed.
Aborted
I
> From: "Mark Brown"
> Cc:
> Date: Mon, 13 Jan 2014 14:06:16 -0800
>
> As mentioned I used Visual C++ 2005,
> loading the project file and building it:
> make_msvc_net2003.vcproj .
>
> This results in a make_msvc.net2003.exe of length 892 KB
> being created in the debug directory.
Does thi
On Mon, 2014-01-13 at 22:23 +0100, Christian Eggers wrote:
> In Makefile 2 my intention was to state that foo.o depends on some
> generated header which must be generated first (might be in another
> rule). But I didn't want to change the be behaviour if foo.o cannot be
> built because e.g. there's
As mentioned I used Visual C++ 2005,
loading the project file and building it:
make_msvc_net2003.vcproj .
This results in a make_msvc.net2003.exe of length 892 KB
being created in the debug directory.
If this is not the intended compilation method,
do give step by step method to compile the
Hint: There's no file present from which foo.o can be built with implicit
rules.
Makefile 1:
--snip---
all: foo.o
--EOF---
# make foo.o
make: *** No rule to make target `foo.o'. Stop.
# echo $?
2
Makefile 2:
--snip---
all: foo.o
foo.o: generated.h
--EOF---
# touch generated.h
# make foo.o
make:
And for the record, the OP had no intention of building for Cygwin, at
least as described. The mention of Cygwin arises only because of the
error messages e.g.
process_begin: CreateProcess(NULL, cygpath
C:\zzz_13.12.1_general\tools, ...) failed.
David
On Mon, Jan 13, 2014 at 9:58 AM, Eli Zaretsk
Title: Re: win32 compilation of make 4.0 source code
Hello, Mark.
Monday, January 13, 2014, 17:57:20 you wrote:
Is the resulting file supposed to executed under Cygwin ?
No.
If you build Make natively for Windows, this results in native Windows version.
Cygwin is actually quite a dif
On Mon, 2014-01-13 at 19:37 +0200, Eli Zaretskii wrote:
> > On Windows, GNU make can be compiled in a quite a number of different
> > ways. It would be helpful if you gave us an idea of which method you
> > used.
>
> He said that: he used Microsoft Visual C++ version 2005.
But I meant, how? Thr
> From: Paul Smith
> Cc: bug-make@gnu.org
> Date: Mon, 13 Jan 2014 12:44:12 -0500
>
> On Mon, 2014-01-13 at 19:37 +0200, Eli Zaretskii wrote:
> > > On Windows, GNU make can be compiled in a quite a number of different
> > > ways. It would be helpful if you gave us an idea of which method you
> >
> From: Paul Smith
> Date: Mon, 13 Jan 2014 11:47:54 -0500
>
>
> On Mon, 2014-01-13 at 18:21 +0200, Eli Zaretskii wrote:
> > > From: "Mark Brown"
> > > Date: Mon, 13 Jan 2014 06:04:24 -0800
> > >
> > > I was able to compile the make 4.0 source code downloaded from the
> > > gnu make site using
On Mon, 2014-01-13 at 18:21 +0200, Eli Zaretskii wrote:
> > From: "Mark Brown"
> > Date: Mon, 13 Jan 2014 06:04:24 -0800
> >
> > I was able to compile the make 4.0 source code downloaded from the
> > gnu make site using Visual C++ 2005 under Windows 7 64 (generated 0 errors,
> > 259 warnings)
>
I was able to compile the make 4.0 source code downloaded from the
gnu make site using Visual C++ 2005 under Windows 7 64 (generated 0 errors, 259
warnings)
but executing the resulting make command file from the Windows 7 DOS Command
Prompt
yields a series of warnings/errors:
> From: "Mark Brown"
> Date: Mon, 13 Jan 2014 06:04:24 -0800
>
> I was able to compile the make 4.0 source code downloaded from the
> gnu make site using Visual C++ 2005 under Windows 7 64 (generated 0 errors,
> 259 warnings)
> but executing the resulting make command file from the Windows 7 DOS
I was able to compile the make 4.0 source code downloaded from the
gnu make site using Visual C++ 2005 under Windows 7 64 (generated 0 errors, 259
warnings)
but executing the resulting make command file from the Windows 7 DOS Command
Prompt
yields a series of warnings/errors:
===
22 matches
Mail list logo
