[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #9, bug #64806 (project make): > Is the brechtsanders build a 32-bit executable or a 64-bit executable? 64-bit as I read it. bin/make.exe:PE32 executable (console) Intel 80386 (stripped to external PDB), for MS Windows, 10 sections perl/c/bin/mingw32-make.exe:

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #7, bug #64806 (project make): > This bug report lacks a reproduction recipe ... The closest which I think I can come to providing such a recipe is in WINE where "-Otarget -j" works with the ezwinports build, but not with the brechtsanders/winlibs_mingw build. detailed outputs

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #6, bug #64806 (project make): > This bug report lacks a reproduction recipe ... Yes, I know. Unfortunately (well, in this instance ;) ) I run Linux exclusively on my personal systems and only interact with windows via continuous integration builds. Troubleshooting with CI is

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #5, bug #64806 (project make): Quoting @shawnlaffan from https://github.com/StrawberryPerl/Perl-Dist-Strawberry/issues/148#issuecomment-1783929512 > The root cause of the issue seems to be that the make executables do not support recursive calls when they have been renamed. Call

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #3, bug #64806 (project make): "choco install make" is stated to be a build from https://sourceforge.net/projects/ezwinports https://bitbucket.org/xoviat/chocolatey-packages/src/master/make/4.4.1/tools/VERIFICATION.txt At this point I have am not sure I can provide any additi

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #2, bug #64806 (project make): Following the trail from the strawberry perl installer leads to: https://github.com/brechtsanders/winlibs_mingw/issues/174 ___ Reply to this item at:

[bug #64806] "invalid output sync mutex" on windows

Follow-up Comment #1, bug #64806 (project make): Correction. We intended to use make 4.4.1 via chocolatey. It appears that the latest strawberry perl release 5.38.0.1 now installs "make.exe". Previous releases only install "gmake.exe". This executable also identifies as make 4.4.1, but I am un

[bug #64806] "invalid output sync mutex" on windows

age Status: None ___ Follow-up Comments: --- Date: Sun 22 Oct 2023 09:38:22 PM UTC By: Michael Davidsaver I have recently found that recursive invocations of make 4.4.1 (from chocolatey) in th

[bug #63552] includes specified with -I ignored when -C is also used, since 4.4

Additional Item Attachment, bug #63552 (project make): File name: make_include_bug.tar.gzSize:0 KB ___ Reply to this item at:

Amiga support

Please sir - may I have some more?

please keep up supporting AmigaOS

founder of probablly the biggest Amiga developer group on facebook, I noticed lots of people beeing unhappy with your decission. Please overthink! Kind regards, Mit freundlichen Grüßen, Michael Bergmann Betreuer Kaufmann im Gesundheitswesen (IHK) Gesundheits- und Krankenpfleger Mühlstraße 29

Archive Members as Targets

foo.o ranlib libfoo rm foo.o acker$ make gcc-c -o foo.o foo.c ar cr libfoo foo.o ranlib libfoo rm foo.o ``` Can anyone confirm that? (or tell me what obvious stupid mistake I have done …?) Best regards, Michael

[bug #53152] Intermittent timeout running regression test features/output_sync

Follow-up Comment #3, bug #53152 (project make): I think the problem is the outer loop in update_goal_chain(): - All goals are handle once per loop iteration. - At the beginning of each iteration at least on child is reaped (if any exist) What happens is this: First iteration: - job for 'bar' is

Re: Idea: Standard way to negate special targets

On Wed, Jun 12, 2019 at 7:25 PM David A. Wheeler wrote: > > I would strongly prefer "!" just binding to the next target & documenting > that. > The first time someone sees they may wonder how far it binds, > but it's pretty obvious that there are multiple possibilities, > so they can look it up o

Re: Idea: Standard way to negate special targets

Or! How about a general syntax for canceling prerequisites (not just for special targets)? Say, "!:" (inspired by "&:")? Then you'd just say ".ONESHELL!: my-tricky-target". More verbose than "my-tricky-target: ! .ONESHELL" or whatever, but seems more robust to me (and more general, although I co

[bug #54116] Extend documentation for space-free line continuation techniques

Follow-up Comment #2, bug #54116 (project make): Thanks; I feel better using this technique knowing that it's officially supported :-) ___ Reply to this item at: ___

[bug #55944] make-4.2 arm64 w10 test

URL: Summary: make-4.2 arm64 w10 test Project: make Submitted by: necrose99 Submitted on: Mon 18 Mar 2019 08:17:13 AM UTC Severity: 3 - Normal Item Group: Bug

[bug #55316] Stack (or rather "scope"?) backtracing facility

Additional Item Attachment, bug #55316 (project make): File name: 0001-Print-backtrace-on-fatal-error.patch Size:13 KB ___ Reply to this item at: ___

[bug #55316] Stack (or rather "scope"?) backtracing facility

URL: Summary: Stack (or rather "scope"?) backtracing facility Project: make Submitted by: cmm2 Submitted on: Fri 28 Dec 2018 08:25:05 PM UTC Severity: 3 - Normal Item Gr

[bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

Follow-up Comment #4, bug #54727 (project make): The first version of the patch is not good, make hangs on this test: $ echo '$(eval all: M:=$$(eval all: Q:=(eval all: T:=M)))' | ./make -f - The second version of the patch takes into account that the target-specific context may already b

Re: [bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

. It seems that it's not hard to fix this bug and the fix does not break existing scripts, I will send a patch when I have time. -michael On Fri, Oct 5, 2018 at 2:50 AM Brian Vandenberg wrote: > On Thu, Oct 4, 2018 at 7:53 AM Michael Builov > wrote: > > > > Foll

[bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

Additional Item Attachment, bug #54727 (project make): File name: make_bug_54727.patch Size:0 KB ___ Reply to this item at: ___ Message sent

[bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

Follow-up Comment #3, bug #54727 (project make): It also possible to step on this "foreach + eval" bug not in a recipe. Please consider the next example: # define global variable f := g # function for defining target-specific variables # $1 - target # $2 - variable def_target_speci

[bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

Follow-up Comment #2, bug #54727 (project make): > By the time we expand the recipe all target-specific variables for that recipe have already been assigned: it's not possible for the recipe to add more target-specific variables to it's target and have those take effect. But this is works: $ ec

[bug #54727] foreach variable is not visible for a target specific variable definition in a recipe

URL: Summary: foreach variable is not visible for a target specific variable definition in a recipe Project: make Submitted by: mbuilov Submitted on: Tue 25 Sep 2018 02:48:25 PM UTC S

[bug #54703] Incorrection expansion of := accumulator under $(eval …)

Follow-up Comment #1, bug #54703 (project make): Hello. This is not a bug. Argument of eval is always expanded prior evalation. Let's see how this works. - ITERATIONS:=1 2 3 ACCUMULATOR:=Macron go home : WORD_1:=Macron WORD_2:=go WORD_3:=home define ACCUMULATE WORD:=$(WORD_$(1)) ACC

[bug #54116] Extend documentation for space-free line continuation techniques

d break the dollar sign/backslash/newline technique. Thanks for your consideration. Michael Henry ___ File Attachments: --- Date: Thu 14 Jun 2018 04:44:07 PM UTC Name: make.

[bug #49841] flavor() function incorrectly shows function parameters as defined.

Follow-up Comment #1, bug #49841 (project make): > It appears that the scope of the parameters in the outer function intrudes into the inner function for the flavor() function but not for the value of the parameter. The origin() function is also affected. When inner function takes less argumen

[bug #49844] 'make -j' without explicit process count sometimes doesn't parallelize

Follow-up Comment #1, bug #49844 (project make): Hello. There is a bug in your trivial example: 1) 'seq 1000 | xargs -n1000 make -j5' expands to 'make -j5 1 2 3 4 5 6 7 ...' and 2) 'seq 1000 | xargs -n1000 make -j' expands to 'make -j 1 2 3 4 5 6 7 ...' As we can see, in second example '1

[bug #51237] Deadlock in Ctrl-C handler on Windows

Follow-up Comment #3, bug #51237 (project make): I have created test application, which detaches console and sleeps for 1000 seconds: #include int main(int argc, char *argv[]) { FreeConsole(); Sleep(100); return 0; } And tested it with this makefile: # run make -j -O, then pres

[bug #51237] Deadlock in Ctrl-C handler on Windows

Follow-up Comment #2, bug #51237 (project make): >> ...Would you be willing to assign copyright for your changes to the FSF... Yes, I will, no problem. >> ...signaling the event you added will not interrupt that wait... New event is not supposed to interrupt Main thread waiting for sub-processe

[bug #51237] Deadlock in Ctrl-C handler on Windows

URL: Summary: Deadlock in Ctrl-C handler on Windows Project: make Submitted by: mbuilov Submitted on: Wed 14 Jun 2017 12:43:28 PM UTC Severity: 3 - Normal Item Group: Bug

[bug #50648] GMake 4.2.1 --with-guile fails silently if installed Guile version is higher than 2.0

Additional Item Attachment, bug #50648 (project make): File name: 0001-Allow-building-with-Guile-2.2.patch Size:0 KB ___ Reply to this item at: ___ Mes

Re: Optimization for reading *.d files

On 19.03.2017 09:54, Norbert Thiebaud wrote: > On Sat, Mar 18, 2017 at 9:25 PM, brenorg wrote: >> >> Anyway, I want to continue to use GNU Make, and not fallback to CMake/Ninja. >> After some profiling, what's killing me is parsing the "*.d" files generated >> by the compiler. >> >> The time to in

[PATCH] Improve “missing separator” error when reading spaces

With this change, users who have their editor misconfigured when writing Makefiles without using 8 spaces for one TAB character will also get a friendly error message. I used the following 3 test cases: echo -e "foo:\n echo bar" > broken.make echo -e "foo:\necho bar" > broken.8.make

[PATCH] Improve “missing separator” error when reading spaces

With this change, users who have their editor misconfigured when writing Makefiles without using 8 spaces for one TAB character will also get a friendly error message. I used the following 3 test cases: echo -e "foo:\n echo bar" > broken.make echo -e "foo:\necho bar" > broken.8.make

[bug #44660] possible buffer overflow?

URL: Summary: possible buffer overflow? Project: make Submitted by: mdupont Submitted on: Sun 29 Mar 2015 11:48:55 AM CEST Severity: 3 - Normal Item Group: Bug

Makefiles named makefile not found anymore on Windows

0 }; + { "GNUmakefile", "makefile", "Makefile", "makefile.mak", 0 }; #else /* !Amiga && !VMS && !WINDOWS32 */ { "GNUmakefile", "makefile", "Makefile", 0 }; #endif /* !Amiga && !VMS && !WINDOWS32 */ --- Best regards, Michael ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Document typo

The last line of "Section 6.5 Setting Variables" of http://www.gnu.org/software/make/manual/make.html#Recipes is: var := $(shell find . -name "*.c") and believe should be: var := $(shell find . -name '*.c') Michael Procca Software Developer Iders Incorpora

Re: Help:Stop compile due to Segmentation Fault Error

On 21/06/13 16:09, 최철우 wrote: > Dear GNU.org > > I have a problem with make file. > > Segmentation Fault error occurred while compile below part of Makefile. > > we used the make 3.81 on ubentu 10.10. ok... >$(eval APKCERTS_TMP_FILE := $(shell mktemp)) using eval... > Here is t

RE: Implicit rule with multiple targets "forgets" to build a target

only about giving a recipe and prerequisites to the file presently in question. However, when this file's recipe is run, the other targets are marked as having been updated themselves." Sorry. Greetings Michael Bos From: Michael Bos Sent: Dienstag, 18. Juni 2013 01:24 To: 'bug-make@g

Implicit rule with multiple targets "forgets" to build a target

ng to the documentation there should be no difference: "4.10 Multiple Targets in a Rule: A rule with multiple targets is equivalent to writing many rules, each with one target, and all identical aside from that." What's wrong with my argumentation? I am using GNU Make 3.81

[bug #15719] Test suite not reliable for parallel build support

Follow-up Comment #9, bug #15719 (project make): With cvs HEAD (as of 2012-12-09), I've seen TEST #11 ("thing1,thing2 start,end") sometimes failing, even without so much load on the Linux build machine, where the diff output shows /missing/ lines. Extracting this test and running in a loop with s

[bug #35147] Implement a make function to write to a file

Follow-up Comment #2, bug #35147 (project make): Yay, thanks! Wish it was present back in 3.81... just in case, fiddling with debug logging. ___ Reply to this item at: _

[bug #19298] simplify automatic generation of prerequisites example

Follow-up Comment #3, bug #19298 (project make): I would not discuss too much on this issue (4 years already!). The first example works indep. of compiler used, second works for gcc. The request is then to remove the given example in the manual and replace it with: --

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Fri, Sep 2, 2011 at 05:38, Paul Smith wrote: > I do prefer bugs files in Savannah to things sent on the mailing list, > just because they're easier to keep track of. Ah. Sorry about that. ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Tue, Aug 2, 2011 at 16:59, Michael Witten wrote: > On Tue, Apr 12, 2011 at 17:14, Paul Smith wrote: >> On Mon, 2011-04-11 at 18:49 -0500, Michael Witten wrote: >>> On Fri, Mar 25, 2011 at 00:00, Paul Smith wrote: >>> > On Thu, 2011-03-24 at 03:52 -0500, Micha

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Tue, Apr 12, 2011 at 17:14, Paul Smith wrote: > On Mon, 2011-04-11 at 18:49 -0500, Michael Witten wrote: >> On Fri, Mar 25, 2011 at 00:00, Paul Smith wrote: >> > On Thu, 2011-03-24 at 03:52 -0500, Michael Witten wrote: >> >> > Thus, it makes most sense for `-

Re: substantial 'glob' speedup ...

Hi Paul, On Sun, 2011-04-17 at 22:00 -0400, Paul Smith wrote: > On Wed, 2011-04-06 at 12:35 +0100, Michael Meeks wrote: > > Anyhow - one problem we are seeing is that as we load and parse the > > ~50Mb of dependencies that we need (for part of writer) we are statting > > th

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Fri, Mar 25, 2011 at 00:00, Paul Smith wrote: > On Thu, 2011-03-24 at 03:52 -0500, Michael Witten wrote: >> > Thus, it makes most sense for `--dry-run' (`-n') to mask `--touch' (`-t') >> > rather than the other way around (which is the current, buggy, u

Re: substantial 'glob' speedup ...

atch is slightly simpler (though hardly if you use strpbrk). So - I'd rather prefer my original; with the glob scope indented to avoid the glob_free having an ugly condition, and using strpbrk; but that's just me. HTH ! Michael. diff --git a/read.c b/

substantial 'glob' speedup ...

inue to work nicely when I test with manual touching, and 'make check' passes ... Thoughts much appreciated, Thanks, Michael. diff --git a/read.c b/read.c index a3ad88e..48de4fe 100644 --- a/read.c +++ b/read.c @@ -2824,6 +2824,20 @@ tilde_expand

substantial 'glob' speedup ...

inue to work nicely when I test with manual touching, and 'make check' passes ... Thoughts much appreciated, Thanks, Michael. diff --git a/read.c b/read.c index a3ad88e..48de4fe 100644 --- a/read.c +++ b/read.c @@ -2824,6 +2824,20 @@ tilde_expand

[PATCH 5/7] Docs: Move `within a variable name'

Signed-off-by: Michael Witten --- doc/make.texi |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index 091e098..9ab0ae2 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5219,7 +5219,7 @@ Here, the innermost @samp{$(x)} expands to @samp{y

[PATCH 3/7] Docs: Add `the following' to improve flow after the example.

Signed-off-by: Michael Witten --- doc/make.texi |9 + 1 files changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index a3eb642..7460963 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5189,7 +5189,7 @@ in its name might have strange results

[PATCH 1/7] Docs: Offset modifiers with commas

Signed-off-by: Michael Witten --- doc/make.texi |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index 13cecbd..efc28f7 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5183,7 +5183,7 @@ sets @samp{bar} to @samp{a.c b.c c.c}. @cindex

[PATCH 7/7] Docs: Remove comma

Signed-off-by: Michael Witten --- doc/make.texi |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index 6feae91..069941d 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5344,7 +5344,7 @@ This restriction could be removed in the future if

[PATCH 6/7] Docs: Improve wording

In particular, the `will' is not the correct tense for the expressions of some sort of universal fact; therefore, the language has been changed to mirror that of previous examples. Signed-off-by: Michael Witten --- doc/make.texi |6 +++--- 1 files changed, 3 insertions(+), 3 dele

[PATCH 2/7] Docs: Remove unnecessary rambling

Signed-off-by: Michael Witten --- doc/make.texi |4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index efc28f7..a3eb642 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5185,9 +5185,7 @@ sets @samp{bar} to @samp{a.c b.c c.c}. Computed

[PATCH 4/7] Docs: add comma before `which'

Signed-off-by: Michael Witten --- doc/make.texi |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index 7460963..091e098 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -5199,7 +5199,7 @@ a := $($(x)) @noindent defines @code{a} as

[PATCH 0/7] Docs: Computed Variable Names

I recently read through that section, and here are a few modifications that I made along the way. Michael Witten (7): Docs: Offset modifiers with commas Docs: Remove unnecessary rambling Docs: Add `the following' to improve flow after the example Docs: add comma before `which&#x

[PATCH] Docs: `and' -> `but'; add missing `the'

Signed-off-by: Michael Witten --- doc/make.texi |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/doc/make.texi b/doc/make.texi index 298d0ce..13cecbd 100644 --- a/doc/make.texi +++ b/doc/make.texi @@ -7554,7 +7554,7 @@ Here the redefinition takes place if @samp{$(origin

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Tue, Mar 8, 2011 at 18:12, Michael Witten wrote: > On Tue, Mar 8, 2011 at 16:11, Philip Guenther wrote: >> On Tue, Mar 8, 2011 at 1:37 PM, Michael Witten wrote: >>> The `--dry-run' flag is supposed to be safe in that nothing >>> in the file system is act

Re: [PATCH] Options: `--dry-run' should prevent `--touch' from touching

On Tue, Mar 8, 2011 at 16:11, Philip Guenther wrote: > On Tue, Mar 8, 2011 at 1:37 PM, Michael Witten wrote: >> The `--dry-run' flag is supposed to be safe in that nothing >> in the file system is actually modified. > > That's not actually true. To quote the

[PATCH] Options: `--dry-run' should prevent `--touch' from touching

res future compliance by introducing a test. Signed-off-by: Michael Witten --- remake.c |3 +++ tests/scripts/options/dash-n | 15 +++ 2 files changed, 18 insertions(+), 0 deletions(-) diff --git a/remake.c b/remake.c index 97e3854..91a70cc 100644 --- a/remake.c +++

[PATCH] Docs: make.texi: static -> simple

Variables are largely described as being one of the following flavors: * Recursively expanded * Simply expanded The two occurrences of the word `static' in regard to the variable flavor have been replaced with the word `simple' in order to maintain consistency. Signed-off-by: Mich

[PATCH] Docs: make.texi: ; -> ,

The punctuation in a few spots has been change from a semicolon to a comma; this is not only grammatically correct, but also consistent with previous usage when presenting the exact same information. Signed-off-by: Michael Witten --- doc/make.texi |6 +++--- 1 files changed, 3 insertions

Re: Problem with parallel build

On 21.10.2010 21:04, Mike Shal wrote: On Thu, Oct 21, 2010 at 1:33 PM, Vardhan, Sundara (GE Energy) wrote: Hi Michael During parallel makes if the time of the object files created and the time archive command is run is within a second then it will fail to include these object files. The

Problem with parallel build

pp1" repeatedly. On my machine (Intel core i5 551, openSuSE 11.3, make 3.81) make fails after a few retries, because the link command is invoked before app1.o is compiled. --Michael ### --- Makefile start --- AR := ar CC := gcc all: app1 # Link apps app%: app%.o lib.a ${CC} ${@:a

[bug #27374] fatal error reading included makefile silently ignored

Follow-up Comment #2, bug #27374 (project make): Oops. I get the same message; I hadn't noticed that it scrolled off the top of my terminal. Nonetheless, I still think make should drop dead immediately in this case and also return an error status. My understanding is that 'include' may sometim

[bug #27374] fatal error reading included makefile silently ignored

URL: Summary: fatal error reading included makefile silently ignored Project: make Submitted by: mkc Submitted on: Wed 02 Sep 2009 02:26:22 PM CDT Severity: 3 - Normal I

[bug #17614] Clock Slew < 1 sec.

Follow-up Comment #3, bug #17614 (project make): I posted the previous comment before I created my account. ___ Reply to this item at: ___ Message sent

Re: 3.81 and windows paths

or the second choice. It seems to me that it should be possible to have the DOS path within quotes, so that it doesn't trigger make's pattern matching syntax. That would be a more acceptable solution than the other two. -- Michael Eager[EMAIL PROTECTED] 1960 Park Blvd.

PATCH: make-3.81 - read.c bug?

Hi, In file read.c, the function multi_glob() has #ifndef NO_ARCHIVES code which I believe has a bug. Once you enter the large encompassing for loop memname get sets to either NULL or non-NULL (due to a malloc). Then, entering case 0, i gets set to gl.gl_patchc, and a while loop churns over

PATCH: make-3.81

Hi, In file implicit.c, there seems to be a variable 'remove_explicit_deps' which, as far as I can tell, serves as a flag to "remove all the dependencies that didn't come from this implicit rule", as per the comment in the code. However, this variable is initialized to 0, then set to 0, then

Re: [patch] parallel make bug with failing commands

able one should simply make the sleep and the "echo" be one command, then it's guaranteed to be form disturbing output in the prompt :) Ala: ok: @sleep 4; echo ok done Ciao, Michael. ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make

[patch] parallel make bug with failing commands

7; is reset after the first iteration. But that leads to a recursive invocation of die() which just exits the whole make, and misses to complete the iteration of the waiting loop in the upper die() activation. I used the below patch to fix this problem. It produces no regressions in the testsu

building make on solaris 2.8

in build.sh, the symbol @REMOTE@ is not resolved. The build process crumps when it trys to compile [EMAIL PROTECTED] ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

Re: Variable is assigned wrong value

om comment on the end of the line". Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

Re: gmake and embedded PL/SQL block

have a problem." Kudos for posting the version of GNU make that you're running though. Most people forget to do that. Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] On Wed, 23 Jul 2003, Pankratz, Theresa wrote: > I am trying to compile a Pro*C project using gmake. One of the pc fil

make 3.80, build.sh, remote-@REMOTE@.c: No such file or directory

: sh ./build.sh The build dies with: compiling remote-@REMOTE@.c... gcc: /berman/migchain/source/make-3.80/remote-@REMOTE@.c: No such file or directory gcc: no input files It looks like a missing @...@ substitution in configure.in. Michael C

errors when installed gnumake v3.80 on Win2000

d"   Used files as it is suggested in README for W32 doc: VCVARS32.bat build_w32.bat   Please advise.   Thank you in advance, Michael

(no subject)

Hi I am learning linux and after installing j2sdk1.4.1 I think it added new fonts or changed the system and now (screen,X,GDM) whatever does not work I get the error message: According to/var/run/gdm.pid, gdm was already running (XXX) but seems to have been murdered mysteriously. . the screen t

Too speedy problem

Hi all, I'm a numerical analysis who has been running a script that solves a standard test set of optimization problems by repeatedly linking them with an optimization code and then running the resulting executable. Some of these problems are old and solve very quickly on modern computers. This

Re: GNU make 3.80rc2 released

Is it just me or is "make check" completely hosed? I'm not at all confident in my environment here so this isn't rhetorical. Can someone please confirm a working "make check" please? Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] On Tue, 10 Sep 2002 [EMAIL P

GNU Make version 3.79.1 bug

Hello! The following test demonstates a problem in Gnu make 3.79.1 It is a combination of recursive make, overriding variables for targets and += operator. does someone have fix/work-around for this? thanks, MST /tmp>cat make.bug var = 1 export var %: $(MAKE) -f test.bug x: var += a /tm

Re: GNU make 3.80 rc1

e the patches themselves) to 3.80? Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] diff -ur make-3.80rc1.orig/commands.c make-3.80rc1/commands.c --- make-3.80rc1.orig/commands.cTue Jul 9 00:54:08 2002 +++ make-3.80rc1/commands.c Mon Jul 15 15:34:30 2002 @@ -512,7 +

Re: GNU make 3.80 rc1

len = 1 cp isn't NULL qp is NULL bp isn't NULL qp is null because we try to alloca(0) which returns NULL (despite what the comment at the top of the file says about alloca(0) re-claiming memory). I'm hoping rc2 is more fun. ;-) Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED

Re: GNU make 3.80 rc1

those are the two that make GNU make not as fun to use here. I'll send out my two patches here in a bit. Ya changed the code just enough so my patches for previous version of make don't apply cleanly to this one so I have to redo them. ;-) Michael Sterrett -Mr. Bones.- [EMAIL PROTEC

I made $230,000 in two months

OT accepted. Make sure the cash is concealed by wrapping it in at least 2 sheets of paper. On one of those sheets of paper write the NUMBER & the NAME of the Report you are ordering, YOUR E-MAIL ADDRESS and your name and postal address. PLACE YOUR ORDER FOR THESE REPORTS NOW- REPORT #1: "

Make 3.79.1 can't build from CD

\"/usr/share/locale\" - gcc -O3 -m486 -pipe -fomit-frame-pointer -fstrict-aliasing -s -o make ar. /bin/sh: /vol/cdrom/make-3.79.1/stamp-pot: Read-only file system make[2]: *** [/vol/cdrom/make-3.79.1/stamp-pot] Error 1 make[2]: Leaving directory `/var/.home/michael/build/make-build' mak

Re: Oracle Pro-C pre-compiler error PCC-F-02104 & Pro Cobol errorPCC-S-0037

eading its configuration from. Looking at /oracle/.db_user_passwd might be good too since it looks like that's where the userid is supposed to be coming from in your environment. Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] On Mon, 15 Apr 2002, Thatcher Deane wrote: > We use gnumake

Re: Dependency issue in GNU Make?

Hello Henning, Thanks a lot for your quick answer! I double checked that your patch works on my computer too. Cheers, Michael. > Scripsit Michael Opdenacker <[EMAIL PROTECTED]> > > > I found the below problem using GNU Make 3.79.1. > > What do you think? > >

MzScheme on Darwin

mpile Gnu CC and Gnu Pascal. Thank you. Michael terminal_interaction.txt Description: Binary data

MzScheme on Darwin

Hi, I wanted to compile MzScheme for Darwin on Powerpc. This is what happened: = [localhost:~/desktop/plt.1/src] michael% sudo ./configure loading cache ./config.cache checking for gcc... (cached) cc checking whether the C compiler (cc

Dependency issue in GNU Make?

Hello, I found the below problem using GNU Make 3.79.1. What do you think? Don't hesitate to get back to me for more details or to ask me to run more experiments. You can download the testcase files from http://michaelo.free.fr/gnu/make/make_feb21_2002.tar.gz Cheers, Mi

Re: unexpected rm

e out the first time. ;-) Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] On Sat, 16 Feb 2002, andre maute wrote: > hello make team > > i use linux 2.4.16, gcc 2.95.2 > > make -v > GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. > Built for i686-pc-linu

handling of errors during recursion

I've been switching our build over to gnumake to all the migration to other platforms. The system has a top level makefile that sets up a few things, then recursively calls the make files located in each of the service areas that are subdirectories. The issue I am dealing with is an error in a s

Re: non-restartable system calls

en a problem for us in the past and we're currently running a patched version of gmake to get it to work properly with regard to non-restartable system calls. The EINTR checks are definitely painful. ;-) Thanks, Michael Sterrett -Mr. Bones.- [EMAIL PROTECTED] __

Error in VMS port of GNU make

In file variable.c, the procedure lookup_variable has an error in the following code: sptr = value; scnt = 0; if (listp) *listp = current_variable_set_list; while ((sptr = strchr (sptr, '$'))) { The variable listp is not defined, n

  1   2   >