[bug #64112] ...\$(...) or ...\\$(...) give unexpected result

: None ___ Follow-up Comments: --- Date: Wed 26 Apr 2023 08:10:40 AM UTC By: Pascal J. Bourguignon 1- the comments in the source code would seem to indicate that the intended effect of

[bug #51974] multiline (define/endef) containing target-specific assignments causes errors in /bin/sh

Follow-up Comment #3, bug #51974 (project make): As the other poster points out here, $(eval) was required to parse the result of the $(call) reference. This resolves this issue. Many thanks for your patience and advice.

[bug #51972] target-specific assignments and target definitions in multi-line variable definitions not handled correctly

Follow-up Comment #2, bug #51972 (project make): As a posted pointed out in #51972, $(eval) was required to parse the result of the $(call) reference. This resolves this issue. ___ Reply to this item at:

[bug #51974] multiline (define/endef) containing target-specific assignments causes errors in /bin/sh

Follow-up Comment #2, bug #51974 (project make): case 4: Makefile: define EXELNK1 $(1): OBJ1=xOBJ1 endef define EXELNK2 $(1): OBJ2=xOBJ2 endef $(call EXELNK1, utl1) $(call EXELNK2, utl1) utl1:;@echo "jfh1:pt1:$(OBJ1):$(OBJ2):" result of invoking make : works as expected ___

[bug #51973] variable value set by target-specific assignment not available to reference in multi-line variable definition

Follow-up Comment #2, bug #51973 (project make): Anonymous: You are indeed correct. I did not take that first expansion into account. I think your explanation resolves this issue. Many Thanks for this. ___ Reply to this item at:

[bug #51972] target-specific assignments and target definitions in multi-line variable definitions not handled correctly

Follow-up Comment #1, bug #51972 (project make): as mentioned in but 51972 by another poster, I had neglected to account for the initial expansion of $(OBJ1) in the definition of EXELNK here is a corrected version with that (hopefully) taken into account: case 1 : Makefile: define EXELNK #$(1):

[bug #51974] multiline (define/endef) containing target-specific assignments causes errors in /bin/sh

URL: Summary: multiline (define/endef) containing target-specific assignments causes errors in /bin/sh Project: make Submitted by: oss542 Submitted on: Sat 09 Sep 2017 08:45:50 PM UTC

[bug #51973] variable value set by target-specific assignment not available to reference in multi-line variable definition

URL: Summary: variable value set by target-specific assignment not available to reference in multi-line variable definition Project: make Submitted by: oss542 Submitted on: Sat 09 Sep 2017 08:30:55 PM

[bug #51972] target-specific assignments and target definitions in multi-line variable definitions not handled correctly

URL: Summary: target-specific assignments and target definitions in multi-line variable definitions not handled correctly Project: make Submitted by: oss542 Submitted on: Sat 09 Sep 2017 07:09:29 PM U

[bug #46443] $(warning message) line number incorrect if after TAB

Follow-up Comment #7, bug #46443 (project make): Great work! ___ Reply to this item at: ___ Message sent via/by Savannah http://savannah.gnu.org/ __

[bug #46443] $(warning message) line number incorrect if after TAB

Follow-up Comment #5, bug #46443 (project make): Many thanks for making the patch. ___ Reply to this item at: ___ Message sent via/by Savannah http://

[bug #46443] $(warning message) line number incorrect if after TAB

URL: Summary: $(warning message) line number incorrect if after TAB Project: make Submitted by: now3d Submitted on: Sat 14 Nov 2015 10:07:10 GMT Severity: 3 - Normal Item

prerequisites alter choice of pattern match rules?

Hi, I have run into something I find strange with GNU Make 3.81 (yes, I know 3.82 is latest but since it's not in EL6, my target platform, I cannot depend on it's features). I would think that given the following set of rules: /tmp/%.foo: %.foo echo "foo rule 1" touch $@ %.foo:

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #10, bug #31361 (project make): Thanks Martin. Fair enough, I just thought a more appropriate name might help others in my position (even if it's marked "not a make bug" or whatever). Apparently my searching has led me to the wrong place, so could you point me towards the right

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #9, bug #31361 (project make): Drilling deeper into this, I see cc1plus.exe is silently giving me errors even though I specified "-v". " cc1plus.exe: error: argument to "-gdwarf-" should be a non-negative integer " Hmm. Must be referring to "-gdwarf-2", which is a perfectly va

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #7, bug #31361 (project make): Thanks Paul. I thought make might be managing intermediate files but you say no. Ok, that's progress. I'm downloading make-3.82-3-mingw32-bin.tar.lzma now, though I believe it will be fruitless. I'll try something else in the meantime. Seems to m

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #5, bug #31361 (project make): Is it possible to change the name of the bug to "MinGW make deletes intermediate file prematurely" or something similar, please? The inaccurate bug name might be putting people off. ___ Rep

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #4, bug #31361 (project make): I think this is a make timing issue. It looks like the file is created and then deleted before as is invoked. Why would this happen? It seems cc1plus doesn't have any more verbosity options than "-v". That might be a moot point though, since here

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #3, bug #31361 (project make): Thanks Eli. From my make output, make is already passing -v to cc1plus. It doesn't mention anything about not writing the file (or writing it and then deleting it). I see from this: COLLECT_GCC_OPTIONS='-v' '-DSmallTestLib_EXPORTS' '-Wwrite-strin

[bug #31361] MinGW make inexplicably invokes as.exe

Follow-up Comment #1, bug #31361 (project make): I found the random filename elsewhere in the results file. Looks like cc1plus produces Assembler output in a temp location and then as compiles it into machine code. Ok, so that's how the build system works. Fine. Invoking cc1plus by hand, I find

[bug #31361] MinGW make inexplicably invokes as.exe

URL: Summary: MinGW make inexplicably invokes as.exe Project: make Submitted by: fatman_uk Submitted on: Mon Oct 18 11:58:08 2010 Severity: 3 - Normal Item Group: Bug

RE: [RFC]serialize the output of parallel make?

I've not been following this thread too closely, but this may be relevant: http://www.cmcrossroads.com/ask-mr-make/12909-descrambling-parallel-buil d-logs One aspect to this issue is that the compiler error messages appear 'mis-aligned' against the sources. I've worked around this for one build sy

[bug #27545] Patch to add Makefile.mak to default file names searched

Follow-up Comment #2, bug #27545 (project make): Boris. You make a good point about not processing NMAKE files. However lots of "make" tools like Borland I believe also check for "Makefile.mak". The main point of this bug ticket is to have an extension (filetype) on the filename, so editors can

[bug #27545] Patch to add Makefile.mak to default file names searched

URL: Summary: Patch to add Makefile.mak to default file names searched Project: make Submitted by: now3d Submitted on: Sun 27 Sep 2009 22:36:55 GMT Severity: 3 - Normal

make 3.81 crash: make: double free or corruption (!prev)

$ uname -a Linux localhost.localdomain 2.6.23.14-107.fc8 #1 SMP Mon Jan 14 21:37:30 EST 2008 i686 i686 i386 GNU/Linux $ make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for ME

Auto deps problem with newest make

x27;. Finished prerequisites of target file `a.out'. Giving up on target file `a.out'. Actual working makefile attached regards -- ## # # ## ### ### Tadeusz J. Liszka, Ph.D. # # # # # # # # # Altair Engineering Inc. # # # ### http

[bug #712] GNU make can't handle spaces in pathnames

Follow-up Comment #8, bug #712 (project make): How to other make's handle quoted strings? like NMAKE for example? do any POSIX make's handle quoted strings internally themselves at present? ___ Reply to this item at:

[bug #17277] Pathes longer than 128 Chars fail with make under windows

Follow-up Comment #1, bug #17277 (project make): In light of Microsoft declaring the old Win9x/ME OSs "end of life". Can we just switch to the new API and drop compatiblity with these old OSs for future releases of Make? Cheers Jon ___ Rep

[bug #17926] gnustep-base build fails on HP-UX 11.23 (both ia64 and pa)

Follow-up Comment #1, bug #17926 (project make): Hello Rashmi, This build problem is in GNUstep, not GNU Make. Their site is gnustep.org. My view is this bug should be marked invalid. I don't have an HP machine to review the headers on, perhaps HP is not a supported build platform.

Re: required changes in make file

Hello On 05/07/06 00:26, Kshitij Yadav wrote: Hello, We had purchased the crossbow's MICAz, MIB520, audio sensor and mote-view. After installation, when we run "make micaz" command, in the cygwin window, it shows the error "*** no rule to make target MICAz. stop". Looking into the info for the

Re: makefile issue

Hi! On 19/05/06 10:02, Parikshat Dubey wrote: Hi! I want to integrate my c source files with gtk source files(supplied by thirdparty) and want to make a make file for that purpose.I know how to devlop make file but donot know how i integrate gtk files into it .I donot know how i shall start.

[bug #16476] Inconsistent function macros - again

Follow-up Comment #1, bug #16476 (project make): Hi! > I assume that WINDOWS32 is for MS compiler support - not for WIN32 specific > code. I also see that changes have been made in the CVS source, at least in > make.h - so take this for what it is. WINDOWS32 is for win32 builds, be they compil

[bug #15942] test_driver.pl - run_each_test() fails to set $status when test dies, prints value of $status from prior test

Follow-up Comment #4, bug #15942 (project make): Hi, Has this just changed recently? I've seen the symlink tests fail every time I have ran the tests on MinGW/MSVC builds within MSYS. Admittedly I have not tried rc1, I only tried the betas. Could the symlink tests be explicitly disabled if W32?

[bug #15942] test_driver.pl - run_each_test() fails to set $status when test dies, prints value of $status from prior test

Follow-up Comment #2, bug #15942 (project make): Can symlink checks be disabled on MinGW/MSVC builds when testing through MSYS (or Perl installed in a different environment on windows) please? Kind regards JG ___ Reply to this item at:

Re: Make-3.81 rc1 hangs with -j 2 (multiplatform)

On 27 Feb 2006 at 13:09, Paul D. Smith wrote: > %% Boris Kolpackov <[EMAIL PROTECTED]> writes: > > bk> 3. If I replace the "%.3 : | %.2" rule with the equivalent normal > bk> rule, make does not hang. What would the "equivalent normal rule" be? Perhaps I can use that as a workaround in my

Re: Make-3.81 rc1 hangs with -j 2 (multiplatform)

Boris, On 27 Feb 2006 at 21:13, Boris Kolpackov wrote: > That would be > > test.3: | test.2 Ah yes, thanks. > I think a better workaround would be to remove test.2 from .SECONDARY. Actually, that case still hangs for me, under both Unix and Windows. Could you please test that again, being

Re: Make-3.81 rc1 hangs with -j 2 (multiplatform)

On 27 Feb 2006 at 13:09, Paul D. Smith wrote: > Dave, can you please file a bug for this on the Savannah site so we > don't misplace it? Please add the makefile to reproduce it as an > attachment so we don't lose the formatting. Done; bug #15919. -- Dave

Make-3.81 rc1 hangs with -j 2 (multiplatform)

I originally reported a make-3.81rc1 hang against the Windows port here: http://lists.gnu.org/archive/html/make-w32/2006-02/msg00058.html ...but I've now tried the test makefile on a different system, and the same hang occurs, so I believe it's a general make issue. I built and tested rc1 on

Re: help

On 20/02/06 17:31, Robert Tellamalla wrote: Hi, While I am trying to install the Gnu make in to my system it is showing that make is failed and goto dosbuild.bat Hi, There is a win32 binary in the download section of http://mingw.org/ Kind regards JG

Make CVS 7X slower on Win32 NTFS than beta 4

Running under Windows (MSYS), I observe that make built from current CVS takes about seven times longer to check a large number of dependent files on an NTFS partition than did beta 4. Sample timing from a 3 GHz machine using a makefile that assembles a large number of TIFF images into a PDF:

Re: Installation problem with make 3.80

Hi, On 11/01/06 00:30, Steve Buberl wrote: Hello, I just installed ubuntu to discover that there was no make program. I am running latest ubuntu which includes the "make" package (version 3.80-9). You can install it with: $ sudo apt-get install make Kind regards JG

Re: Make - problem - MacOS X

I have a problem when I try to compile any c program. I work with Mac OS X. This is what the system displays when I use "make" ### /Users/Radhouani/IOTA/IOTA/default.mk:248: warning: overriding commands for target `/Users/Radhouani/IOTA/IOTA/lib/lib.a' /Users/Radhouani/IOTA/IOTA/de

Re: broken make file for w32

Hi, On 09/12/05 20:53, Frank P Esposito wrote: Greetings -- The supplied make file for win32 (nmakefile) is broken for ver 3.80 -- There are references to functions in hash.c, but hash.obj is not included in the makefile Thanks, this is fixed in the latest beta of 3.81 and CVS. Kind rega

RFC: Make is a HUGE memory hog

On Sun, Dec 04, 2005 at 10:33:31PM +1030, Alan Modra wrote: > On Sun, Dec 04, 2005 at 11:45:21AM +, Andrew Haley wrote: > > Alan Modra writes: > > > On Sun, Dec 04, 2005 at 12:35:31AM +0100, Gerald Pfeifer wrote: > > > > spawns a recursive make (GNU make 3.80) that consumes some 450MB of > >

test suite "Comparing Output ...." display filenames when -debug flag is set?

Hello, Could the test suite display the filenames it is diffing when it displays "Comparing Output " and -debug is passed please? I am trying to work out which log files correspond with a particular .mk file and am not completely sure. Could the .base files also be kept when -debug is passe

Re: Latest CVS make compile warnings fix

On 24/07/05 18:04, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Perhaps there could be a way to force setting of config.h macro's jg> for those circumstances. I was thinking of something like that too. I have to go back and examine that

Re: Latest CVS make compile warnings fix

Hi Paul, [...] jg> main.c:420: warning: missing initializer jg> main.c:420: warning: (near initialization for `switches[30].type') This one, IMO, could be a bug in GCC. As far as I can tell the initializer is correct. The only way to avoid the warning seems to be to put a full suite of 0

Re: Latest CVS make compile warnings fix

Hi Paul, [...] jg> I expect those macros were intended to be used with signed values, jg> and now they are being used with unsigned values as well, which is jg> bad. No, I don't think so. I don't remember the details but my recollection is that they were specifically designed to work wit

Re: Is this a bug?

Hi David, This is still in make3.81beta3: make.h /usr/include/stdlib.h on my debian GNU/Linux box contains: #define EXIT_FAILURE1 /* Failing exit status. */ So you could be right. Anyone know if this is 0 for a reason..? Kind regards JG __

Re: Latest CVS make compile warnings fix

[...] Well we can't use inline functions per se. GNU make still attempts to be compilable by old K&R C compilers: it doesn't even rely on features available in the first (1989) ANSI C standard, much less features not found until the second (1999) ISO C standard (which is where inline was introdu

Re: Latest CVS make compile warnings fix

Hi Paul, [...] jg> If I submit fixes for these would they be reviewed for inclusion ? I'm happy to look at them, but they will not be easy to fix. I'm happy to assist if needed. I hope the 3.81 release can have as few warnings as possible. jg> main.c:420: warning: missing initializer

job.c:2155: warning: unused parameter `batch_filename_ptr'

Could (void)batch_filename_ptr; be added in this job.c to stop this compile warning please? (or a different solution to stop the warning) batch_filename_ptr job.c: In function `construct_command_argv_internal': job.c:2155: warning: unused parameter `batch_filename_ptr' I just rebuilt with late

Latest CVS make compile warnings fix

Hello, I just built on GNU/Linux (gcc (GCC) 3.3.5 (Debian 1:3.3.5-8)) If I submit fixes for these would they be reviewed for inclusion ? main.c:420: warning: missing initializer main.c:420: warning: (near initialization for `switches[30].type') main.c: In function `main': main.c:1790: warning: c

Re: help-me please

Hello Marcos, On 22/03/05 12:22, Marcos Lima Rodrigues wrote: make: /home/marcos/usr/src/AOMD/Util/buildUtil/getarch: Command not found (@(@re/locale/en_US/LC_MESSAGES/make.moMakefile:175: /home/marcos/usr/src/AOMD/Util/buildUtil/make.common: No such file or directory make: *** No rule to make targ

Re: bug?

[EMAIL PROTECTED] wrote: make:invalid option -- a There is not such an option to my knowledge. Please check the man page (man make) to find the option you are looking for. Please post make --version output if you have a bug report. Kind regards JG ___

Re: Problem with current cvs make

Hi Art, This morning I did a 'cvs update', rebuild, and installation of make, and am seeing a problem when trying to build the current GCC snapshot. The 'make' command bombs out at the point where the GCC build process prints out 'Bootstrapping the compiler'. Unfortunately I've deleted my build log

Re: Schedule for GNU make 3.81

I noticed several files were not writable in the tar.gz package. Could the files also be -wr- when it is the final release please? Kind regards JG -r--r--r-- config.ami -r--r--r-- configh.dos -r--r--r-- config.h-vms -r--r--r-- config.h.W32 -r--r--r-- Makefile.DOS -r--r--r-- README -r--r--r--

Re: Interupting make, causing my machine to lock up?

You might like to try with -d option to see if that reveals which process is causing the problem. it sounds as though a process is not handling SIGTERM (Ctrl+C) correctly. (that means "die now"). You could try sending SIGINT ("please die") which requests your process to exit as fast as it can. I t

Invalid VPATH directories query

Hello, I have noticed some accidental mistakes with invalid VPATH directories. I wonder if there is any way Make could first check the directories are valid and list the ones which are invalid? Would such a feature be supported if not already present? (I could not find it) Kind regards JG __

goto and macro usage

Hello I noticed use of goto's in the latest cvs make source code. Are there any plans to restructure so that goto/branches are not needed? goto's make the algorithms a little unclear IMO. There are several common macro's in use. i.e. "record_waiting_files()", "return_STRING_N_HASH_2". Could the

Re: Problem with make -j option

I am learning about the make code. But i have problem of make -j code. Can u give details about it. Plz give details as early as possible. ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

return codes

Greetings Could someone direct me to documentation on the various return codes make returns please? I could not spot any so far in the man/info pages or source code. Best regards JG ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/m

Re: Hi

This is not a problem with make. You need Qt, I suggest you contact your supplier of Qt. You could check that your shared libraries are on the correct path kdevelop searches too. Perhaps you need to run ldconfig? (or equivalent) JG on the 02/03/04 08:58, Do Manh Hung wrote: I'm installed Qt

Re: make/tests issues

Hi, on the 29/02/04 14:33, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Are the make/tests working ok at present? I am testing with the jg> latest CVS code. Using MSYS/rxvt as my shell environment, perl jg> v5.6.1 compiled for msys. They wo

Re: Autoconf/Automake versions needed to build make from CVS

You definitely need at least 0.12 and I think you'll really need 0.13.1. Ok, thank you. jg> They talk about having a preparation/boostrap script. I could not jg> spot one in the CVS. Check out the README.cvs file; there's a quick set of commands there that will get you from a vanilla CVS ch

make/tests issues

Hello, Are the make/tests working ok at present? I am testing with the latest CVS code. Using MSYS/rxvt as my shell environment, perl v5.6.1 compiled for msys. There are several problems, the output seems to be unable to be determined as identical or different. I checked the output for the firs

Re: Autoconf/Automake versions needed to build make from CVS

on the 28/02/04 22:31, Paul D. Smith wrote: Actually locally I'm building now with autoconf 2.59, automake 1.8.2, and gettext 0.14.1. There was a big hurdle to get over to get to automake 2.5x but since then the releases have been easy. I do this because there are fixes to autoconf and automake a

Autoconf/Automake versions needed to build make from CVS

Hello I was about to test some changes on my GNU/Linux computer. I found that the latest CVS source requires "Autoconf version 2.58 or higher". I manually upgraded my distro version to 2.57 last year with great pains. I was wondering why make needs to use the latest Autoconf version? Would it be

Re: make dumps core on empty filename

Hi Paul This bug has been fixed in the source for GNU make. The fix will be available in the next release. I wonder when the final testing phase before release of the next release will be? If this testing phase or final release candidate is announced I would be interested in giving it a try. I t

Re: Any help needed?

How about figuring out a backwards compatible way to deal with paths containing spaces? Regards JG on the 30/01/04 07:26, Kamil Burzynski wrote: Hello. Recently I've decided to spend some time on open-source project - and after short search I've found (on savannah site) list of projects that

Re: 3.81 ... any dates for release

jg> Will this release be ISO C90 GNU Make? With other packages such jg> as binutils standardising on C90 I am interested to know if jg> anything is in the pipeline plan for Make. "C90" GNU make? Is "C90" some shorthand for some version of the POSIX standard I'm unaware of? I thought "C90"

Re: 3.81 ... any dates for release

Hello, Will this release be ISO C90 GNU Make? With other packages such as binutils standardising on C90 I am interested to know if anything is in the pipeline plan for Make. Best regards JG on the 18/01/04 21:46, Noel Yap wrote: Will this release include the distributed make feature? If not, w

Re: help compile

Hi, Looks like a mame problem; rather than GNU Make being at fault. I suggest you contact the website you received the source code from. Please be sure to give them complete error logs. Not just the two lines here. Regards JG on the 20/01/04 18:49, Digerati . wrote: dear sir i found this er

Re: [patch] README.W32.template

Hello Paul, on the 22/11/03 20:10, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Is there a reason why "template" was appended to this files name jg> in CVS? Because during the creation of the tarball releases the file is processed t

[patch] README.W32.template

Hello, I have not heard anything about the patch I emailed on 2003-10-08: http://www.mail-archive.com/[EMAIL PROTECTED]/msg02796.html Could someone consider it for addition please? Kind regards JG ___ Bug-make mailing list [EMAIL PROTECTED] http://m

Lucent nmake feature support

Hello, I have been reading about Lucent nmake (http://www.bell-labs.com/project/nmake/). It looks interesting, they use a different rule format, and include a preprocessor. There is a comparison to GNU make (http://www.bell-labs.com/project/nmake/faq/gmake.html). I was wondering if GNU mak

Re: make signal text descriptions

Hi, #define SIGINT 2 /* Interactive attention */ #define SIGILL 4 /* Illegal instruction */ #define SIGFPE 8 /* Floating point error */ #define SIGSEGV 11 /* Segmentation violation */ #define SIGTERM 15 /* Termination request *

Re: make signal text descriptions

Hi Earnie, ok, I wonder if win32 has extra signals, this code 127, could these be supported for win32 ports? #define SIGINT 2 /* Interactive attention */ #define SIGILL 4 /* Illegal instruction */ #define SIGFPE 8 /* Floating point error */ #define SI

Re: make signal text descriptions

Hello, What port of Make, specifically, do you use? Hello, I am using a native win32 build I created of 3.80. Kind regards JG ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

Re: make signal text descriptions

Hello, We use the system service to translate the code if the system provides it (many UNIX systems provide strsignal() for example). If not we have a predefined set of signals we translate, but if the signal is not a member of that predefined list it's not translated. ok, I wonder if win32 has e

Re: make signal text descriptions

Hello, Thank you for your email. on the 29/10/03 00:03, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Could the signals and errors that Make displays include the text jg> description of them? The same way that other programs do not jg> retu

make signal text descriptions

Hello, Could the signals and errors that Make displays include the text description of them? The same way that other programs do not return the errno.h value, but the text that it corresponds too. Let me know if you would like to implement this for make. Kind regards JG e.g.: Signal 127 z:\b

chmod 755 build.sh

Hello, As build.sh is generated from build.sh.in I believe it should be set to executable, currently I have to "chmod 755 build.sh" it. Is there a reason build.sh is not included in the make-3.80 distribution? Should @REMOTE@ not default to cstms ? Currently I get the following error until I hav

[patch] README.W32.template

Hello, I have attached patch a made to improve the description of the BATCH_MODE_ONLY_SHELL mode when using --jobs. Please review it for addition. Is there a reason why "template" was appended to this files name in CVS? Best regards JG 2003-10-08 Jonathan R. Grant <[EMAIL PROTECTED]> *

Re: --no-silent --no-quiet style option

Hello, > > As I mentioned before, I'm not interested in adding lots of new > > options. Instead I want to implement one comprehensive option where you > > can specify exactly what types of output you want generated and which > > you don't. > > I'm only suggesting o

Re: --no-silent --no-quiet style option

Hello, on the 24/09/03 05:38, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> I think expanding the output would be helpful. I would like to jg> create a patch to add --no-silent, basically turns off the jg> features of .SILENT, @, --silent. A

Re: --no-silent --no-quiet style option

GNU make if I create the patch and submit to this list? Regards J. Grant ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

Re: Path to binary in --help or --version

ext Paul D. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2003 4:21 AM To: J. Grant Cc: [EMAIL PROTECTED] Subject: Re: Path to binary in --help or --version [SNIP] I'm still not very clear on why you want the path to make. It seems to me that checking the version value should be able to

Re: Path to binary in --help or --version

t;[EMAIL PROTECTED]>. __ It would also be useful to others wishing to determine where the make they are running is actually on the filesystem. JG on the 08/07/03 03:21, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: >> I'm not sure how you imagine

Re: Path to binary in --help or --version

Hi, I'm not sure how you imagine this would work, or what use it would be. If you run --version don't you already know that you have different versions? For instance, cygwin make ver 3.80 and msys/mingw make ver 3.80, both installed, and used by different build processes. However, there are pro

Path to binary in --help or --version

Hi, One problem I have frequently come across is having multiple incompatible versions of make installed. This would be solved if the path was visible. Could the path to the binary being run be added to the --help or --version output please? Alternatively if I submit a patch to add this will it b

make is deleting the c files created during compilation

Hello, I'm experiencing an odd effect using GNU Make version 3.79.1. When the file created during the execution of the makefile is deleted based on this line "$(BMP2C) $< $(*F) > $@" in the Makefile below. Does make have a rule that "deletes all files cat into automated filenames" on exit or s

RE: Eriksson

iqiGMySN > YNc+Cu5pRFG550HtXIc/yF3kuQubiZOgk/ajI1EP0gdlV4rJMvJ2Y59KKBpjTwWhjaGtDRoK > LLTPL3ueTXcapDHugEjDPsmz0J7Bkqv8k9c0eSMB1TYN36Ip0/ihCWSeAKRx7Ixw+CEiKYOi > hCGev+aC4JP44oQhu/kmRlmkw80Z1KVCEN38k3OVOyXZCEGn8Eg5eieJRl3CEiWaGKlXDF8v > zSp/jokSrEGwNFL0jDy6rGzU81Id6Epq7EKQ6ZZ+IUncqMS1OqkS5wd

$(dir $@) does not work correctly with directory names that have spaces. (Cygwin build 3.79.1)

Hi there, Just wanted to drop you a quick note about a "problem" I have encountered while replacing a commercial build system during a cost-reduction excercise. The problem occurs when using directory names with spaces in them - for example: /source/Some Library/Test Harness I neede

Re: make-3.79.1 bug breaks linux-2.5.24/drivers/net/hamradio/soundmodem

enning Makholm wrote: >Scripsit "Adam J. Richter" <[EMAIL PROTECTED]> >> Until the make bug is fixed, I have worked around the problem >> by replacing the rule with: >> $(obj)/sm_tbl_%: $(obj)/gentbl >> PATH=$(obj):$$PATH $< >That

make-3.79.1 bug breaks linux-2.5.24/drivers/net/hamradio/soundmodem

ed around the problem by replacing the rule with: $(obj)/sm_tbl_%: $(obj)/gentbl PATH=$(obj):$$PATH $< Adam J. Richter __ __ 575 Oroville Road [EMAIL PROTECTED] \ / Milpitas, California 95035 +1 408 309-6081

missing config.h

i'm porting the compiler to hux 11i on a hp9000 series D370. i have been using the hpux 11 suggestions and got the gmake and binutils working with ease. now i'm trying to get the compiler as well. i have come across the fillowing errors: ***first error: has been fixed*** **from log** make[3]: L

European Water Management News

king forward to your answer. Best regards, Jan van de Kraats Institute for Inland Water Treatment and Waste Water Treatment (RIZA) European Water Management Official Journal of the European Water Association (EWA) Editor-in-Chief Drs J A van de Kraats Institute for Inland Water Management and W

Re: pipe read hang on Win 2000 with make 3.79.1

> PKGDIR = $(shell echo this.is.a.test | sed 's:\.:/:g') >Your best bet is to ask on [EMAIL PROTECTED], but, did >you try running this directoy >at the command line, >without using make's shell function? >If that doesn't work, then it's not a make issue at >all and you should ask the >Cygwin

pipe read hang on Win 2000 with make 3.79.1

Here's a problem I've encountered recently ... Using the Win32 port of GNU make 3.79.1 on Windows 2000 with either the Cygwin shell, or the MKS sh.exe, or even the Windows cmd.exe I get a hang when running the following makefile: CWD:=$(shell pwd) PKGDIR = $(shell echo this.is.a.test | sed 's:

  1   2   >