Re: enhancement: better clarification of search side effects

2023-06-01 Thread Alejandro Colomar
Hi Peter, On 6/1/23 21:42, Peter Radisson wrote: > > > Am 01.06.23 um 03:39 schrieb Dmitry Goncharov: >> On Wed, May 31, 2023 at 12:40 PM wrote: >>> today i had a strange problem with a long used makefile (GNU Make 4.3). >>> It found a file called "all.sh" and did a "cat all". >> >> That's not

Re: enhancement: better clarification of search side effects

2023-06-01 Thread Peter Radisson
Am 01.06.23 um 03:39 schrieb Dmitry Goncharov: On Wed, May 31, 2023 at 12:40 PM wrote: today i had a strange problem with a long used makefile (GNU Make 4.3). It found a file called "all.sh" and did a "cat all". That's not a strange problem. That's the default make behavior. In the mome

Re: enhancement: better clarification of search side effects

2023-05-31 Thread Dmitry Goncharov
On Wed, May 31, 2023 at 12:40 PM wrote: > today i had a strange problem with a long used makefile (GNU Make 4.3). > It found a file called "all.sh" and did a "cat all". That's not a strange problem. That's the default make behavior. > I use makefile for a long time but that effect happend the f

enhancement: better clarification of search side effects

2023-05-31 Thread Radisson97
Hello List, today i had a strange problem with a long used makefile (GNU Make 4.3). It found a file called "all.sh" and did a "cat all". It took me a while to figure out was was going on. I use makefile for a long time but that effect happend the first time to me. It would be helpful to improve th

Re: clarification the export VAR := VALUE

2010-06-17 Thread Paul Smith
On Thu, 2010-06-17 at 15:16 -0700, Warren Dodge wrote: > I would have expected the shell xterm to also have the exported > variable. Not sure if this is intentional or just never discovered. This is a known issue with a known, but not solved so far, cause. https://savannah.gnu.org/bugs/?10593 --

clarification the export VAR := VALUE

2010-06-17 Thread Warren Dodge
I am not sure if this is a bug report or an enhancement request. If I do the following Makefile # export TESTVAR := TEST $(shell xterm ) xterm: xterm ##

RE: Desire clarification of 'override' behavior

2007-09-11 Thread Krejsa, Dan
Hi Paul, Thanks for the clarification! It isn't clear from the documentation that 'override' changes the 'power' needed to subsequently set a variable (although one eventually finds out ;-). - Dan -Original Message- From: Paul Smith [mailto:[EMAIL PROTECTED]

Re: Desire clarification of 'override' behavior

2007-09-11 Thread Paul Smith
"Krejsa, Dan" <[EMAIL PROTECTED]> writes: > However, using 'override' also seems to prevent subsequent assignments > to the variable, done within the Makefile without 'override', from > taking effect, as if using 'override' made the variable look as if it > had been defined on the command line. Th

Desire clarification of 'override' behavior

2007-09-11 Thread Krejsa, Dan
Hi, Like the poster of http://lists.gnu.org/archive/html/bug-make/2000-10/msg00011.html I've noticed that gnu make (I'm currently using 3.80) has a little undocumented behavior regarding the use of 'override'. Without 'override', an assignment in a Makefile to a make variable will not take e

Re: clarification

2001-02-28 Thread Paul D. Smith
You need to read the whitepaper on my site below about using VPATH; even if you don't use VPATH, it will explain why your makefile is not working as you expect. -- --- Paul D. Smith <[EMAIL PROTECTED]> Find som

clarification

2001-02-26 Thread tanand
i have a specific problem in makefile. I have sub-makefiles in each of my subdirectories. I have also written a main makefile which calls the sub-makefiles. The sample format which we followed is given below. edit : main.o kbd.o command.o display.o \ insert.o search.o files.o utils.o