Re: 4.4: embeds volatile information in MAKEFLAGS

Paul Smith wrote in <05f924d1e2c372b7321b6c3b1863ff864cc433df.ca...@gnu.org>: |On Mon, 2022-11-07 at 21:55 +0100, Steffen Nurpmeso wrote: |>  |However, I don't think that any changes being made for GNU Make 4.4 |>  |compatibility, would render the makefile unusable with GNU Make 4.3 |>  |(unle

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 14:59 -0500, Paul Smith wrote: > I agree that we should drop down to "jobserver unavailable" here > rather than having a fatal error. I have a change that implements this now.

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 21:55 +0100, Steffen Nurpmeso wrote: >  |However, I don't think that any changes being made for GNU Make 4.4 >  |compatibility, would render the makefile unusable with GNU Make 4.3 >  |(unless they start actually using the new features like the new >  |functions, but I don't k

Re: 4.4: embeds volatile information in MAKEFLAGS

Paul Smith wrote in : |On Mon, 2022-11-07 at 21:24 +0100, Steffen Nurpmeso wrote: |> What would interest me now.  Will there be GNU make 4.4.1? |> (On the left and right i see quite some changes of projects to |> become compatible with GNU make 4.4 though, CRUX Linux imported |> a pretty leng

Re: 4.4: embeds volatile information in MAKEFLAGS

On Mon, 2022-11-07 at 21:24 +0100, Steffen Nurpmeso wrote: > What would interest me now.  Will there be GNU make 4.4.1? > (On the left and right i see quite some changes of projects to > become compatible with GNU make 4.4 though, CRUX Linux imported > a pretty lengthy glibc patch, and on the ports

Re: 4.4: embeds volatile information in MAKEFLAGS

ake. | |I'm not sure I understand what you are saying. These values ARE passed |to the child clients through the environment. That's what MAKEFLAGS |_is_, it's the environment variable that's used to allow a parent make |to provide information on options etc. to its sub-makes

Re: 4.4: embeds volatile information in MAKEFLAGS

cessible for root aka SUID i think (E?UID > mismatches, issetuid or what-do-i-know, but this hardly is > a problem for GNU make. I'm not sure I understand what you are saying. These values ARE passed to the child clients through the environment. That's what MAKEFLAGS _is_, it'

Re: 4.4: embeds volatile information in MAKEFLAGS

Hello. Steffen Nurpmeso wrote in <20221105231048.8w3mb%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20221105230326.qijdr%stef...@sdaoden.eu>: ||Dmitry Goncharov wrote in || : |||On Sat, Nov 5, 2022 at 6:24 PM Steffen Nurpmeso \ |||wrote: |||> make[1]: *** Cannot open jobserver /tm

Re: 4.4: embeds volatile information in MAKEFLAGS

Steffen Nurpmeso wrote in <20221105230326.qijdr%stef...@sdaoden.eu>: |Dmitry Goncharov wrote in | : ||On Sat, Nov 5, 2022 at 6:24 PM Steffen Nurpmeso \ ||wrote: ||> make[1]: *** Cannot open jobserver /tmp/GMfifo31074: No such file \ ||> or directory. Stop. || ||Can you please tell us

Re: 4.4: embeds volatile information in MAKEFLAGS

Dmitry Goncharov wrote in : |On Sat, Nov 5, 2022 at 6:24 PM Steffen Nurpmeso wrote: |> make[1]: *** Cannot open jobserver /tmp/GMfifo31074: No such file \ |> or directory. Stop. | |Can you please tell us how to reproduce? Well it is a bit hard in a short time. But like i wrote in my se

Re: 4.4: embeds volatile information in MAKEFLAGS

On Sat, Nov 5, 2022 at 6:24 PM Steffen Nurpmeso wrote: > make[1]: *** Cannot open jobserver /tmp/GMfifo31074: No such file or > directory. Stop. Can you please tell us how to reproduce? regards, Dmitry

Re: 4.4: embeds volatile information in MAKEFLAGS

*** Cannot open jobserver /tmp/GMfifo31074: No such file \ | or directory. Stop. | make[1]: Leaving directory '/tmp/x/s-nail-14.9.24/.obj' | make: *** [makefile:40: distclean] Error 2 | |It seems GNU make now embeds volatile information into $MAKEFLAGS, |but refrains from working if that

4.4: embeds volatile information in MAKEFLAGS

* [makefile:40: distclean] Error 2 It seems GNU make now embeds volatile information into $MAKEFLAGS, but refrains from working if that is invalid. I see NEWS is saying You can force GNU Make to use the simple pipe-based jobserver (perhaps if you are integrating with other tools or older versi

Re: [bug #40639] GNU Make with profiling information

2014/1/14 Tim Murphy > > To some, using a spreadsheet might not seem like the most worthwhile > way to visualise timing information. That's why I thought it can be useful to provide the information in various formats. I found useful the graphs provided via a graph from data in sp

Re: [bug #40639] GNU Make with profiling information

hy wrote: > To some, using a spreadsheet might not seem like the most worthwhile > way to visualise timing information. > > If it was me, I'd be far more concerned about whether I could write a > script that could easily cope with all this information. Builds with > hundre

Re: [bug #40639] GNU Make with profiling information

To some, using a spreadsheet might not seem like the most worthwhile way to visualise timing information. If it was me, I'd be far more concerned about whether I could write a script that could easily cope with all this information. Builds with hundreds of thousands of targets were common f

Re: [bug #40639] GNU Make with profiling information

output format, and I'd prefer that format to be in a > more-or-less readable form, more like the "long" form than the others. If that will be the only format, then it would mean always imposing a lot more more work on the information processing stage due to necessary filtering

Re: [bug #40639] GNU Make with profiling information

e start time of a job, then > > when it's complete show the elapsed time for that job? Or recipe? > Or > > both? > > The resulted information when using absolute time stamps is almost > meaningless until they are further processed in an external tool > because is hard t

Re: [bug #40639] GNU Make with profiling information

mount of time a given job takes to > run, but I guess I don't understand the need for a "start time offset" > at all. Isn't it sufficient to record the start time of a job, then > when it's complete show the elapsed time for that job? Or recipe? Or > both? T

Re: [bug #40639] GNU Make with profiling information

fset is not necessary IMO. I'm unsure about the PID. This is the pid of the make process so I'm not sure what the goal is. Is it to be able to collect all the times together maybe? Is it necessary to dump all the output times at the end? Doing so requires that we increase the size of t

Re: [bug #40639] GNU Make with profiling information

It's nice to know when in the build a job was scheduled. e.g I have a huge job that gets scheduled at the end of the build - wouldn't it be nicer if it was scheduled at the beginning? Perhaps I can redesign my makefile to achieve that if I know. On 11 January 2014 18:58, Paul Smith wrote: > Sorr

Re: [bug #40639] GNU Make with profiling information

Sorry, I've been mostly away from my systems recently. On Wed, 2013-12-18 at 13:28 +0200, Eddy Petrișor wrote: > Thanks for clarifying this. Could you please confirm if the general > direction of the the is OK in the latest patch I sent? I will take a look. > What it is in scope and what I wou

Re: [bug #40639] GNU Make with profiling information

Paul, I would really appreciate feedback on this. If the problem is the licensing, don't worry about my rights, I will gladly give them to the FSF. Pe 18.12.2013 13:28, "Eddy Petrișor" a scris: > > > Pe 15.12.2013 18:07, "Paul Smith" a scris: > > > > > On Sun, 2013-12-15 at 13:38 +, Tim Mur

Re: [bug #40639] GNU Make with profiling information

Pe 15.12.2013 18:07, "Paul Smith" a scris: > > On Sun, 2013-12-15 at 13:38 +, Tim Murphy wrote: > > I suppose I'm skirting around saying that I think gnu make needs an > > output format in the same way that valgrind has "--xml=yes". I'm not > > an XML fan really - JSON might be an alternative

Re: [bug #40639] GNU Make with profiling information

rious reasons the filters we used had to parse the "structured output" into readable form but if you were designing such a thing into make then you could do it without a print-then-parse. It's fairly key for recipes to be able to inject information into this output e.g. attribute=valu

Re: [bug #40639] GNU Make with profiling information

On Sun, 2013-12-15 at 13:38 +, Tim Murphy wrote: > I suppose I'm skirting around saying that I think gnu make needs an > output format in the same way that valgrind has "--xml=yes". I'm not > an XML fan really - JSON might be an alternative. > It isn't your problem to provide such a mechanism

Re: [bug #40639] GNU Make with profiling information

bout it. This feature > is just a small example of how gnu make will evolve an irregular > output format that's not easy to change once its "finalised" because > it's not designed to be extendable. > > Extra information like timing could be a new tag and any parser th

Re: [bug #40639] GNU Make with profiling information

Sorry for the side-track but for future reference when discussing the hypothetical rigorous output format: On Sun, Dec 15, 2013 at 5:38 AM, Tim Murphy wrote: > I'm not an XML fan really Agree. > JSON might be an alternative. IMHO, YAML is to JSON what JSON is to XML (oh, and vim > emacs!). Da

Re: [bug #40639] GNU Make with profiling information

of me to give you any sort of hard time about it. This feature is just a small example of how gnu make will evolve an irregular output format that's not easy to change once its "finalised" because it's not designed to be extendable. Extra information like timing could be a new

Re: [bug #40639] GNU Make with profiling information

es it make sense to separate the profiling info into one file per process and then try to merge the information back? The second proposal I sent prints the pid for the 'short' and 'long' formats, so if one wants to focus on a specific submake, one can grep for the pid in the whol

[bug #40639] GNU Make with profiling information

Follow-up Comment #7, bug #40639 (project make): Please check https://savannah.gnu.org/bugs/download.php?file_id=29801 instead of file #29800 ___ Reply to this item at: _

[bug #40639] GNU Make with profiling information

Additional Item Attachment, bug #40639 (project make): File name: profile-predefs-ga4937bc8.patch Size:9 KB ___ Reply to this item at: ___ Message sent

[bug #40639] GNU Make with profiling information

arbitary string. Formats are: simple, startend, short and long. -P can have an argument respecting the following form: [[prefix]:[separator]] The default argument is equivalent to: PROFILE::short Signed-off-by: Eddy Petrișor The information

Re: [bug #40639] GNU Make with profiling information

g written a few external tools, I always appreciate it when the creator of some information source makes it easy for me to recover data and the relationships between each item. I also like it when there's not really any way for my parser to potentially make some mistake just because a tool

Re: [bug #40639] GNU Make with profiling information

roduces. The profiling info is printed on stderr, not on stdout. I also initially thought I should isolate the information in a different file, but the problem is that for recursive make that file descriptor must be passed on every fork, which is a very intrusive change to make and very wasteful (p

Re: [bug #40639] GNU Make with profiling information

et invokes in a $SHELL? >> >> Yes; something line /usr/bin/time. > > Not on Windows. > >> > If that's the case, you don't get the actual/real-time measurement, and >> > that might skew your profiling information. >> >> True. Hnow how much o

Re: [bug #40639] GNU Make with profiling information

GNU make. > > > If that's the case, you don't get the actual/real-time measurement, and > that might skew your profiling information. > > > > True. Hnow how much of a difference does it make? > > Depends on how badly the build system is written. And tha

Re: [bug #40639] GNU Make with profiling information

at you mean. Do you mean wrapping all target invokes in a $SHELL? > > Yes; something line /usr/bin/time. Not on Windows. > > If that's the case, you don't get the actual/real-time measurement, and that might skew your profiling information. > > True. Hnow how much of a

[bug #40639] GNU Make with profiling information

format > the output of recipes for proper XML encoding as well. > > But I don't want to add multiple different formatting options, for different > types of output. I'd prefer to have one comprehensive formatting capability. AFAICT, we are talking about two types of formatting: - what

Re: [bug #40639] GNU Make with profiling information

you mean. Do you mean wrapping all target > invokes in a $SHELL? Yes; something line /usr/bin/time. > If that's the case, you don't get the actual/real-time measurement, and that > might skew your profiling information. True. Hnow how much of a difference does it make? &

[bug #40639] GNU Make with profiling information

sive formatting capability. So what I'd prefer is to split it so that this change deals solely with the profile information, and (if requested) will print it out in a standard (predefined) format. Then at some future time someone can look into providing an output formatting definition capabi

[bug #40639] GNU Make with profiling information

Follow-up Comment #3, bug #40639 (project make): I rebased the patch on top of f5f5adb6, updated to use O and OS macros, and strlist type for the -P/--profile/--profile-format option parameter. The patch is attached. (file #29698) ___ Addi

[bug #40639] GNU Make with profiling information

Follow-up Comment #2, bug #40639 (project make): I have cleaned up the code to remove the warnings that were generated by the newly introduced code. I also reworked the rebase on the profile-rebase branch to contain cleaner patches and to separate the non-essential changes (e.g.: some whitespace

Re: [bug #40639] GNU Make with profiling information

n extra exec(), > but it will keep the make code base simpler. I'm not sure if I understand what you mean. Do you mean wrapping all target invokes in a $SHELL? If that's the case, you don't get the actual/real-time measurement, and that might skew your profiling information.

Re: [bug #40639] GNU Make with profiling information

On Tue Nov 19 22:29:22 2013, invalid.nore...@gnu.org (Eddy Petrișor) wrote: > Follow-up Comment #1, bug #40639 (project make): > > I have created a cleaned up rebased branch that contains only changes for the > profiling feature so it can be easier to review. > > https://github.com/eddyp/make-pro

[bug #40639] GNU Make with profiling information

Follow-up Comment #1, bug #40639 (project make): I have created a cleaned up rebased branch that contains only changes for the profiling feature so it can be easier to review. https://github.com/eddyp/make-profiler/tree/profile-rebase Please note this branch will be rebased. Use 'git pull --reb

[bug #40639] GNU Make with profiling information

URL: <http://savannah.gnu.org/bugs/?40639> Summary: GNU Make with profiling information Project: make Submitted by: eddyp Submitted on: Tue 19 Nov 2013 21:31:16 GMT Severity: 3 - Normal Item

[bug #32493] new function to output information to file. kind of extension of $(info) function, but outputs to file

Update of bug #32493 (project make): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #1: See bug #35147 __

Using GNU make manual for blog entries: Copyright information

Hi, Now a days, I am learning the GNU make manual. I am also preparing the summary of each chapter for my future reference. Can I post my summaries as my blog post given that, I will clearly mention the reference. Is there any copyright issue? Regards -- Tahir Rauf _

[bug #32493] new function to output information to file. kind of extension of $(info) function, but outputs to file

URL: <http://savannah.gnu.org/bugs/?32493> Summary: new function to output information to file. kind of extension of $(info) function, but outputs to file Project: make Submitted by: olexiyb Submitted on: Tue 15 Feb 2011 01:15:01

Re: Using $(eval) to get information at the time a target is invoked

On Tue, 2011-01-11 at 21:05 +0200, Eli Zaretskii wrote: > Okay. Any hints for where to put breakpoints to see when the Make > reads the directory for the offending file (the one that gets deleted > by the rule)? I'd like to compare the behavior on GNU/Linux and on > Windows, so that I could decid

Re: Using $(eval) to get information at the time a target is invoked

will renew the cache (IIRC), except that the cache > has a limited size and so eventually information is removed from it that > way. > > I would suspect something different: the cache is not loaded all at > once; that is, make starts looking for files and as it does so it loads &g

Re: Using $(eval) to get information at the time a target is invoked

ache used by $(wildcard) on GNU/Linux? I could then try to see > why it does not happen on Windows in this case. There's nothing that will renew the cache (IIRC), except that the cache has a limited size and so eventually information is removed from it that way. I would suspect something differe

Re: Using $(eval) to get information at the time a target is invoked

> Date: Mon, 10 Jan 2011 08:03:31 -0500 > From: "Hsu, ShihchiehIAS" > Cc: > > My friend tried the makefile file on Linux (make 3.81) with me watching, and > it works. Thanks. I tried on GNU/Linux as well, when I first saw your report, and it worked for me, too. I'm waiting for Pa

RE: Using $(eval) to get information at the time a target is invoked

information at the time a target is invoked > From: Paul Smith > Date: Fri, 07 Jan 2011 21:58:53 -0500 > Cc: bug-make@gnu.org > > I realize that maybe this doesn't matter on Windows where the filesystem > is not case-sensitive, but of course on Linux if you delete "he

RE: Using $(eval) to get information at the time a target is invoked

I am new to $(eval) and can only present my wishful thinking: When "all" is invoked, it will go through $(eval) , $(wildcard), etc and save the information, but apparently, the information is also saved when makefile was scanned (???) Any suggestion to dump cache information on

Re: Using $(eval) to get information at the time a target is invoked

> Date: Sat, 8 Jan 2011 11:40:23 -0500 > From: "Hsu, ShihchiehIAS" > Cc: > > Identical results are obtained as before. So the issue is probably not when > GNU/Linux renews the cache $(eval), but when Windows/Make refresh/update the > cache. Maybe I don't understand something, but

RE: Using $(eval) to get information at the time a target is invoked

My earlier example makefile did not emphasize the fact that information should be obtained when target is invoked. Here is as better example: SRC_DIR = ./ PROG_NAME = test define PROGRAM_template $(1)_SRC_DIR = $$(SRC_DIR) $(1)_SRC_FILES = $$(wildcard $$($(1)_SRC_DIR)*.c

RE: Using $(eval) to get information at the time a target is invoked

t work on Linux, then they may be a different problem. -Original Message- From: Eli Zaretskii [mailto:e...@gnu.org] Sent: Saturday, January 08, 2011 4:35 AM To: psm...@gnu.org Cc: Hsu, Shihchieh IAS; bug-make@gnu.org Subject: Re: Using $(eval) to get information at the time a target

Re: Using $(eval) to get information at the time a target is invoked

> From: Paul Smith > Date: Fri, 07 Jan 2011 21:58:53 -0500 > Cc: bug-make@gnu.org > > I realize that maybe this doesn't matter on Windows where the filesystem > is not case-sensitive, but of course on Linux if you delete "hello.c" > that won't have any impact on "Hello.c" which is why "Hello.c" s

Re: Using $(eval) to get information at the time a target is invoked

On Fri, 2011-01-07 at 20:46 -0500, Hsu, Shihchieh IAS wrote: > Summary: Using $(eval) to get information at the time a target is > invoked, but instead information gotten is when “make” is invoked. > > Problem occurs for make3.81 and make 3.82 on Windows XP It works fine for me on

Using $(eval) to get information at the time a target is invoked

Summary: Using $(eval) to get information at the time a target is invoked, but instead information gotten is when "make" is invoked. Problem occurs for make3.81 and make 3.82 on Windows XP However if makefile is modified to look for inform

information

Dear, i'm blocked by some difficulties. I can't install any tool. I'm a new user of Linux ubuntu. i can't run the command ./configure. ibra...@ibrahim-laptop:~$ ./configure --help bash: ./configure: no file or directory find ibra...@ibrahim-laptop:~$ best regards ___

Re: Information regarding gcc

On Thu, 2008-07-03 at 17:26 +0530, A, Sravanthi wrote: > Could you please confirm below? Sorry, none of these questions has any relationship to GNU make; this list is for bugs and issues in GNU make. Please try one of the GCC mailing lists for help with GCC and porting. Good luck! -- -

Information regarding gcc

Paul/Team, We have our API programs defined in C++. Now we are porting from Solaris 5.8 version to LINUX. Currently I am using gcc 3.2.3 on Red hat 3 server. But iam getting some many errors like " ISO C++ says that `TYPE&" , " conversion from `int' to `std::_Ios_Openmode'". From below link under

Re: Question about RAM/ROM information in TinyOS

%% Kamini Prajapati <[EMAIL PROTECTED]> writes: kp> I am working on TinyOS project. kp> Recently I upgraded my system with the following Patches. kp> Previously when I compile any Application, it used to show me the kp> RAM and ROM information. But after the upgrad

Question about RAM/ROM information in TinyOS

Hi, I am working on TinyOS project. Recently I upgraded my system with the following Patches.   nesc-1.1.2b-1.cygwin.i386.rpmtinyos-1.1.14Jul2005cvs-1.cygwin.noarch.rpm   Previously when I compile any Application, it used to show me the RAM and ROM information. But after the upgrade, it doesn&#

sorry for wrong information

Hi, As per my previous email, i have written OS is Solaris 7 but it was wrong. The operating System is solaris2.7 . please take care about it.   Thanks and Regards Alpesh Thakar---Hardware EngineereInfochips Ltd.[EMAIL PROTECTED][EMAIL PROT