Re: The man and Info pages say different things about make -p

On Tue, 2024-06-25 at 05:49 +0800, Dan Jacobson wrote: > The man and Info pages say different things: > To print the data base without trying to remake any files, use 'make > -qp'. > > To print the data base without trying to remake any files, use make - > p -f/dev/n

The man and Info pages say different things about make -p

The man and Info pages say different things: To print the data base without trying to remake any files, use 'make -qp'. To print the data base without trying to remake any files, use make -p -f/dev/null. Also they should mention how to print the database in non-jumbled order. GNU Make 4.3

[bug #65600] `--silent` option should also silence `$(info ...)`

Follow-up Comment #11, bug #65600 (group make): [comment #10 comment #10:] > You might consider checking this blog post; it describes a "common" way to utilize silent / verbose rules. I haven't checked the details of the Linux man pages build system to know how much overlap etc. there is (or isn

[bug #65273] Potential bug in the info function?

Update of bug #65273 (group make): Status:None => Wont Fix Open/Closed:Open => Closed ___ Follow-up Comment #10: I have decided, for now

[bug #65600] `--silent` option should also silence `$(info ...)`

Update of bug #65600 (group make): Status:None => Wont Fix Open/Closed:Open => Closed ___ Follow-up Comment #10: Thanks for the comment;

[bug #65600] `--silent` option should also silence `$(info ...)`

cary. :) > > > > <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/> > > > > The makefiles are the GNUmakefile, and files under share/mk/. > > Indeed the structure seems complicated to me. I browsed a bit and I like that you have an optional $(INFO_) that

[bug #65600] `--silent` option should also silence `$(info ...)`

pub/scm/docs/man-pages/man-pages.git/> > > The makefiles are the GNUmakefile, and files under share/mk/. Indeed the structure seems complicated to me. I browsed a bit and I like that you have an optional $(INFO_) that can prepend strings to the info lines which helps (I believe) with the hi

[bug #65600] `--silent` option should also silence `$(info ...)`

Follow-up Comment #7, bug #65600 (group make): [comment #5 comment #5:] > > [comment #4 comment #4:] > > > Hmmm, I still disagree, because $(info) is a replacement for echo(1). In fact, I use .SILENCE to not show any commands, and then $(info) shows pretty versions of them (

[bug #65600] `--silent` option should also silence `$(info ...)`

Follow-up Comment #6, bug #65600 (group make): I could not find a button to close this enhancement request. I assume I don't have any privileges. Feel free to close this item. ___ Reply to this item at:

[bug #65600] `--silent` option should also silence `$(info ...)`

Follow-up Comment #5, bug #65600 (group make): [comment #4 comment #4:] > Hmmm, I still disagree, because $(info) is a replacement for echo(1). In fact, I use .SILENCE to not show any commands, and then $(info) shows pretty versions of them (e.g., CC file.o, instead of cc -Wall -Wextra ...

[bug #65600] `--silent` option should also silence `$(info ...)`

but cannot redirect the output of `make`. Just one case does not justify my proposal — however the concept of *silencing* is about *severity* of messages and I like that `--silent` can suppress the commands being executed. I just propose that `$(info)` could be included too, because `$(info)` is p

[bug #65600] `--silent` option should also silence `$(info ...)`

s about *severity* of messages and I like that `--silent` can suppress the commands being executed. I just propose that `$(info)` could be included too, because `$(info)` is part of make and not a executed command. ___ Reply to this ite

[bug #65600] `--silent` option should also silence `$(info ...)`

e use `echo` or `$(info ..)` to summarize what is being done in a recipe and use `@` to silence the executed commands. No. `@` is to not print the command before executing it. For silencing the command, you'd need to >/dev/null > However it is not possible to silence `echo` or `$(

[bug #65600] `--silent` option should also silence `$(info ...)`

Follow-up Comment #1, bug #65600 (group make): [comment #0 original submission:] > I propose that `--silence`... I actually meant `--silent`. ___ Reply to this item at: _

[bug #65600] `--silent` option should also silence `$(info ...)`

URL: <https://savannah.gnu.org/bugs/?65600> Summary: `--silent` option should also silence `$(info ...)` Group: make Submitter: goekce Submitted: Tue 16 Apr 2024 10:14:04 AM UTC Severity: 3 -

[bug #65273] Potential bug in the info function?

Follow-up Comment #9, bug #65273 (group make): Note that the trick in John's book no longer works without warnings in the current Git-based code: $ ./make Makefile:3: warning: invalid variable name ' ' Makefile:4: warning: invalid variable reference ' ' Makefile:4: [ ] make: *** No targets. Sto

[bug #65273] Potential bug in the info function?

Follow-up Comment #8, bug#65273 (group make): [comment #3 comment #3:] > The problem is that (a) there is no way to create a variable name containing, or consisting of, whitespace Sure there is: Makefile: ``` SPACE := SPACE := $(SPACE) $(SPACE) $(SPACE) := $(SPACE) $(warning [$( )]) ``` Output:

[bug #65273] Potential bug in the info function?

Follow-up Comment #7, bug#65273 (group make): [comment #6 comment #6:] > Leaving these checks disabled by default is not a good solution since the very people who need this help most, will not benefit from them. I agree. It took me a while to understand some of the GNU Make extensions a few years

[bug #65273] Potential bug in the info function?

Follow-up Comment #6, bug#65273 (group make): I mean, there IS a reasonable way to get the same effect; I showed one possibility in my response. Yes, it looks slightly different but the result is the same and there are no warnings. Alternatively the Emacs makefiles could disable these new warnin

[bug #65273] Potential bug in the info function?

Follow-up Comment #5, bug#65273 (group make): FWIW, I think it is very unfortunate that GNU Make started warning about this trick, especially if there is no reasonable way of getting the same effect by other means. ___ Reply to this item

[bug #65273] Potential bug in the info function?

Follow-up Comment #4, bug#65273 (group make): [comment #3 comment #3:] > It's usually a good idea to check the NEWS file for things that might cause differences in behavior Thanks. I'll do that next time first. :) I grep'd for the error message and found it through git blame so it didn't take too

[bug #65273] Potential bug in the info function?

behavior; in this case see: https://git.savannah.gnu.org/cgit/make.git/tree/NEWS#n68 I understand what the Emacs makefile is trying to do: by adding this invalid variable reference, which used to be silently ignored, they are adding indentation. For example this: $(info foo) shows th

[bug #65273] Potential bug in the info function?

Follow-up Comment #2, bug#65273 (group make): Finally got around to looking into this. From what I can tell it was an intentional change from commit 03ecd94488b85adc38746ec3e7c2a297a522598e. The previous commit doesn't warn and one referenced onward can be controlled with --warn=(ignore|warn|error

[bug #65273] Potential bug in the info function?

Follow-up Comment #1, bug#65273 (group make): I was able to reproduce this on a FreeBSD VM. The GNU Make in ports is version 4.3 and does not output the warnings. When using gmake from master they are outputted. On a separate note, FreeBSD fails when building in maintainer mode due to a #warning p

[bug #65273] Potential bug in the info function?

URL: <https://savannah.gnu.org/bugs/?65273> Summary: Potential bug in the info function? Group: make Submitter: collinfunk Submitted: Thu 08 Feb 2024 02:01:44 AM UTC Severity: 3 - Normal Item

Re: Bug with $(info xxx) in 4.2.1

t; This can be seen by the example given, where the variable assignment > line did not generate an error. You can do this simpler experiment > without the ifeq, which is irrelevant for this issue: > > FOO = bar > $(info baz) > all:; > > (where the f

Re: Bug with $(info xxx) in 4.2.1

On Thu, 2023-12-07 at 11:38 -0500, Dmitry Goncharov wrote: > On Tue, Dec 5, 2023 at 12:01 AM Aaron Williams > wrote: > > > What is happening is I will get the error: > > *** recipe commences before first target.  Stop. > > At the line with $(info xxx) unless I d

Re: Bug with $(info xxx) in 4.2.1

On Tue, Dec 5, 2023 at 12:01 AM Aaron Williams wrote: > What is happening is I will get the error: > *** recipe commences before first target. Stop. > At the line with $(info xxx) unless I do not precede it with a tab. This error is expected. A tab precedes a recipe. It does not ma

Bug with $(info xxx) in 4.2.1

If I have something like the following in my Makefile it is interpreting $(info blah) as a recipe before a target. ifneq ($(SOME_VAR),1) [tab] SOME_OTHER_VAR=SOME_VALUE [tab] $(info"Set SOME_OTHER_VAR=$(SOME_OTHER_VAR)) endif recipes follow What is happening is I will get the

Broken internal links on the make Info Concept Index

In (info "(make) Concept Index"), these three items, * :: rules (double-colon): Double-Colon.(line 6) * ::=: Flavors. (line 56) * ::= <1>: Setting. (line 6) just j

Re: $(info xxx) output interleaved with other $(info) output

urce: https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=fac8d0ac2f4cbdbd5828a57ddc90adf6601d956b This patch causes the Emacs build procedure to use $(info) with bleeding-edge GNU Make where the $(info) bug is fixed, and to resort to sh+echo with GNU Make 4.3-and-older which have the bug.

Re: $(info xxx) output interleaved with other $(info) output

On Thu, Jan 20, 2022 at 5:41 PM Paul Eggert wrote: > I suggested working around the problem in the GNU Emacs Makefiles by > installing the attached patch. It's a bit of a hack but I couldn't think > of anything better, other than outputting the information with the shell > r

Re: $(info xxx) output interleaved with other $(info) output

nk of anything better, other than outputting the information with the shell rather than with $(info). I'm mentioning this here in case anyone else needs a workaround for current and older GNU Make.From 153f3d9af2b3d021d9ba8eb17d979c772a7c09cd Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Th

Re: $(info xxx) output interleaved with other $(info) output

hanged. I examined this method and in fact, it's not possible for it to be called with anything other than exactly one argument so all the mess around recombining multiple arguments is useless. I rewrote this function and applied this change: Author: Paul Smith Date: 2022-01-19 15:49:19

Re: $(info xxx) output interleaved with other $(info) output

aul Eggert Date: Wed, 19 Jan 2022 15:20:40 -0800 Subject: [PATCH] Fix interleaved $(info) output MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * src/function.c (func_error): On POSIX-compatible platforms, cause $(info xxx) output to a pipe to be atomic w

$(info xxx) output interleaved with other $(info) output

I recently modified the Emacs build procedure to use '$(info xxx)' instead of 'echo xxx' to avoid some fork+execs and simplify strace-oriented debugging. Unfortunately, Lars Ingebrigtsen reports that this results in confused output with 'make -j' because $(

(info "(make) Chained Rules") lacks examples

(info "(make) Chained Rules") is great, but it lacks code snippet examples. It mentions several features, but all with English prose. It needs some hard code examples. And those examples should be independent of those built in for C compilers, etc. rm bla.bla # See, b

Re: How to avoid the double execution of a make info call?

> If the makefile, or any of the files it includes, is updated by make > then make will re-execute itself and re-read all the makefiles from > scratch so it can see the updated content. When that happens, > obviously all the $(info ...) functions etc. will be re-expanded. Tha

Re: How to avoid the double execution of a make info call?

the files it includes, is updated by make then make will re-execute itself and re-read all the makefiles from scratch so it can see the updated content.  When that happens, obviously all the $(info ...) functions etc. will be re-expanded. > I imagine that my extra information display might be us

Re: How to avoid the double execution of a make info call?

> Your Makefile looks likely to rebuild .depend, a file that it includes. > So, like Paul said: >>> or else make has re-executed itself >>> because this makefile or one of its >>> included files was rebuilt; Yes. - This can happen at the moment. > I wonder about the information “Re-executing[1]

Re: How to avoid the double execution of a make info call?

Your Makefile looks likely to rebuild .depend, a file that it includes. So, like Paul said: >> or else make has re-executed itself >> because this makefile or one of its >> included files was rebuilt; see https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gnu.org%2Fsoftware%2Fm

Re: How to avoid the double execution of a make info call?

> If you are seeing these values printed multiple times it means that the > makefile is being parsed multiple times. How can such additional parsing be clarified further? Will it help to display extra data from special make variables? > Why that might be, we can't determine from the information

Re: How to avoid the double execution of a make info call?

On Thu, 2017-06-22 at 09:36 +0200, SF Markus Elfring wrote: > > modules_without_mli::=$(filter-out $(basename $(mli_sources)),$(basename > > $(ml_sources))) > > $(info modules_without_mli) > > $(info $(sort $(modules_without_mli))) > > Now I observe that the test

Re: How to avoid the double execution of a make info call?

> modules_without_mli::=$(filter-out $(basename $(mli_sources)),$(basename > $(ml_sources))) > $(info modules_without_mli) > $(info $(sort $(modules_without_mli))) It seems that I got this design approach working to some degree by the addition of a few calls of make functio

[bug #40801] $(info), $(warning), $(error) are evaluated in a comment in a define

Update of bug #40801 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: This isn't a bug, IMO.

[bug #40801] $(info), $(warning), $(error) are evaluated in a comment in a define

URL: <http://savannah.gnu.org/bugs/?40801> Summary: $(info), $(warning), $(error) are evaluated in a comment in a define Project: make Submitted by: None Submitted on: Wed 04 Dec 2013 10:26:31 AM UTC Severity: 3 -

[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 __

[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: insufficient debug info from gnu-make

All, I am a compiler expert, busy doing compiler optimization invention, design, and implementation, and perhaps someday some of the fruits of my inventions can, with my employer's permission, be folded into gcc. in that light, it would be far better to the community overall if I ca

[bug #111] '@' hides useful info sometimes, needs --print_all_cmds

Update of bug #111 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

Re: insufficient debug info from gnu-make

Peter Lawrence wrote: great if you want to see what was actually executed, not so great if you want to figure out where in the make sources you need to start looking, both are realistic wants. when things get as messy as gcc's makefiles, I'ld like to be able to see both the before and after

Re: insufficient debug info from gnu-make

However, I do see some value in an extension to support command-line options that would, whenever executing a recipe, output the make-file name and line number, along with $@ and maybe $? (or at least its first few entries) - for example --debug=r (recipe) might enable this; this would fit with

Re: insufficient debug info from gnu-make

> the output I see from make is after all macro substitutions have been > made, which can make it virtually impossible > to recognize as far as where it came from in the original source This, however, is an issue with how the make file is written. It sounds like its recipes for commands are of f

Re: insufficient debug info from gnu-make

... make[.]: ... GNU Make displays the equivalent "Entering directory foo..." and "Leaving directory foo..." messages. Isn't that the same info? the words "Entering" and "Leaving" never appear in the output I captured So are you going to read the

Re: insufficient debug info from gnu-make

[.]: ... >> >> GNU Make displays the equivalent "Entering directory foo..." and >> "Leaving directory foo..." messages.  Isn't that the same info? > > the words "Entering" and "Leaving" never appear in the output I captured

Re: insufficient debug info from gnu-make

t the directory that the commands had cd'ed to before recursing (and maybe the file name, can't be sure any more) make[foo/bar]: ... make[foo]: ... make[.]: ... GNU Make displays the equivalent "Entering directory foo..." and "Leaving directory foo..." messages. Isn

Re: insufficient debug info from gnu-make

wrote out the directory that the commands had cd'ed to before > recursing (and maybe the file name, can't be sure any more) > > make[foo/bar]: ... > make[foo]: ... > make[.]: ... GNU Make displays the equivalent "Entering directory foo

Re: insufficient debug info from gnu-make

Paul, one thing I remember in detail about Sun's make, is that instead of writing a level number make[3]: ... make[2]: ... make[1]: ... it wrote out the directory that the commands had cd'ed to before recursing (and maybe the file name, can't be sure any more) make[foo/bar]: ...

Re: insufficient debug info from gnu-make

On Thu, 2010-07-29 at 21:09 -0700, Peter Lawrence wrote: > make[3]: *** No rule to make target `real-install-headers-tar'. Stop. This is printed when you've invoked make and the target you asked for on the command line cannot be created (for example you ran "make foo" but the makefile has no targ

insufficient debug info from gnu-make

Sirs, in trying to debug a failing gcc build, it seems that the real trouble is that there doesn't seem to be any easy way to figure out what directory/file[line number] a make command comes from, for example I see as output: make[3]: *** No rule to make target `real-install-heade

Re: Section 3.8 of the info manual not respected

On Wed, May 27, 2009 at 10:03 AM, Anthony Shipman wrote: > On Wed, 27 May 2009 11:26:14 am Philip Guenther wrote: ... >> The paragraph just above the example says this: >> >>    For example, if you have a makefile called `Makefile' that says how >> to make the target `foo' (and other targets)

Re: Section 3.8 of the info manual not respected

On Thu, 2009-05-28 at 03:03 +1000, Anthony Shipman wrote: > On Wed, 27 May 2009 11:26:14 am Philip Guenther wrote: > > On Tue, May 26, 2009 at 9:45 AM, Anthony Shipman wrote: > > > I've tried the example in section 3.8 Overriding Part of Another > > > Makefile. i.e. > > > > > > foo: > > >f

Re: Section 3.8 of the info manual not respected

On Wed, 27 May 2009 11:26:14 am Philip Guenther wrote: > On Tue, May 26, 2009 at 9:45 AM, Anthony Shipman wrote: > > I've tried the example in section 3.8 Overriding Part of Another > > Makefile. i.e. > > > > foo: > >        frobnicate > foo > > > > %: force > >       �...@$(MAKE) -f Makefile $@ >

Re: Section 3.8 of the info manual not respected

On Tue, May 26, 2009 at 9:45 AM, Anthony Shipman wrote: > I've tried the example in section 3.8 Overriding Part of Another Makefile. > i.e. > > foo: >        frobnicate > foo > > %: force >       �...@$(MAKE) -f Makefile $@ > > force: ; > > The command 'make foo' results in > > make[1]: Makefile:

Section 3.8 of the info manual not respected

I've tried the example in section 3.8 Overriding Part of Another Makefile. i.e. foo: frobnicate > foo %: force @$(MAKE) -f Makefile $@ force: ; The command 'make foo' results in make[1]: Makefile: No such file or directory make[1]: *** No rule to make target `Makefile'.

Re: [bug #25751] Add option to output dependency info as xml

ually edit makefiles. This is a kind of step on the way in that it puts the dependencies into a format that a gui could parse fairly easily. Regards, Tim 2009/3/2 anonymous : > > URL: >  <http://savannah.gnu.org/bugs/?25751> > >                 Summary: Ad

[bug #25751] Add option to output dependency info as xml

URL: <http://savannah.gnu.org/bugs/?25751> Summary: Add option to output dependency info as xml Project: make Submitted by: None Submitted on: Mon 02 Mar 2009 07:15:19 PM UTC Severity: 3 - Normal Item

[bug #24522] $(info) does not nothing

Update of bug #24522 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: The $(info) fu

[bug #24522] $(info) does not nothing

URL: <http://savannah.gnu.org/bugs/?24522> Summary: $(info) does not nothing Project: make Submitted by: None Submitted on: Fri 10 Oct 2008 05:50:12 PM UTC Severity: 3 - Normal Item Grou

link to New-Fashioned Suffix Rules in Info

Info says 10.7 Old-Fashioned Suffix Rules === "Suffix rules" are the old-fashioned way of defining implicit rules for `make'. Suffix rules are obsolete because pattern rules are more general and clearer. OK, at this point give a linking fo

[bug #20069] Request for unexport/export info in makefile database outputs

URL: <http://savannah.gnu.org/bugs/?20069> Summary: Request for unexport/export info in makefile database outputs Project: make Submitted by: agent Submitted on: Monday 06/04/2007 at 13:11 Severity: 3 -

Re: broken reference in info documentation

OK, fixed for the next release. Thanks. -- --- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may b

broken reference in info documentation

tting., for a full explanation of `:=')" makes info complain about not finding the node "Setting.", with a period. It seems punctuation is not allowed after the @pxref command in texinfo. One solution is the attached patch, which removes the offending comma. Although, it m

Wasteful trailing blanks spotted on one Info page

Wasteful trailing blanks spotted on one Info page, with cat -e|colrm 21 name1 := $(word $ include inc.mk$ $ name2 := $(word $ all:$ ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug

info tree jump

In the info menu, reading the page at LINE A, it seems to lead into the tree at LINE B or something. Maybe move LINE A into the LINE B set or something. Writing the Commands in Rules * Echoing:: How to control when commands are echoed. * Execution:: How

Re: Phony Targets Info node's parallelism

%% Dan Jacobson <[EMAIL PROTECTED]> writes: dj> The Phony Targets Info node mentions parallel builds, but I don't dj> see any "&" symbol meaning parallel jobs, nor a make -j. So the dj> node should clarify it is talking about a different type of dj>

Phony Targets Info node's parallelism

The Phony Targets Info node mentions parallel builds, but I don't see any "&" symbol meaning parallel jobs, nor a make -j. So the node should clarify it is talking about a different type of parallelism. P.S., in emacs use show-trailing-whitespace to see trailing blanks near

Re: Double-Colon Rules Info page needs an example

Paul> I don't see how this is a good example of how to use double-colon rules. Well, with no examples to build from, of course all users can do is wildly guess. ___ Bug-make mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-make

Re: Double-Colon Rules Info page needs an example

%% Dan Jacobson <[EMAIL PROTECTED]> writes: dj> The Double-Colon Rules Info page needs an example snippet. dj> I think I figured out a use just from reading the documentation however: dj> bus8.htm:: #always check for a fresher version dj> wget -N http://www.fybus.co

can't jump to : stuff in Info index

In the info index, these cannot be jumped to with m etc. * :: rules (double-colon): Double-Colon. * := <1>:Setting. * :=:Flavors. probably because they use Info's colon without quoting o

Double-Colon Rules Info page needs an example

The Double-Colon Rules Info page needs an example snippet. I think I figured out a use just from reading the documentation however: bus8.htm:: #always check for a fresher version wget -N http://www.fybus.com.tw/bus8.htm fybus.w3m:bus8.htm w3m -cols 99 -dump $? > $@ Or an e

Re: make 3.80: -B option is not documented in man and info pages

%% Petr Slansky <[EMAIL PROTECTED]> writes: ps> There is an alterntaive --always-make for -B option, from my point ps> of view, --rebuild-all will be better but I am happy with ps> --alwayes-make too. I considered and rejected "rebuild-all" because I was concerned people might think that it

Re: make 3.80: -B option is not documented in man and info pages

%% Henning Makholm <[EMAIL PROTECTED]> writes: hm> No, it's not in the man page, but the man page explicitly states hm> that it isn't being kept up-to-date. (If somebody cares enough hm> about manpages to do the work, they'll probably contribute a patch hm> for make.1). Someone sent me a

Re: make 3.80: -B option is not documented in man and info pages

Scripsit Petr Slansky <[EMAIL PROTECTED]> > Thanks for -B option very much, it seems to work well. > -B option is not documented in man and info pages. I see it loud and clear in node "Options Summary" of the texinfo manual. Sure you're looking in the right manual?

make 3.80: -B option is not documented in man and info pages

make 3.80: Thanks for -B option very much, it seems to work well. -B option is not documented in man and info pages. There is an alterntaive --always-make for -B option, from my point of view, --rebuild-all will be better but I am happy with --alwayes-make too. With regards, Petr

Re: Line up info topdir entry

%% Julio Merino <[EMAIL PROTECTED]> writes: jm> I've noticed that the Info directory entry of gnu make is not jm> lined up properly with other entries in the same section. This jm> makes it ugly. This patch should fix it: I'm not aware of any standards or documen

Line up info topdir entry

Hello I've noticed that the Info directory entry of gnu make is not lined up properly with other entries in the same section. This makes it ugly. This patch should fix it: --- make.info.orig Fri Aug 30 22:55:14 2002 +++ make.info Fri Aug 30 22:55:21 2002 @@ -2,7 +2,7 @@ INF

Re: Make info bug: typo

Thanks. -- --- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.org/gmake/ "Please remain calm...I may be mad, but I am a professi

Make info bug: typo

Hi, In Make's info page, node 'Include': This is acts like `include' in every way except that there is no The 'is' should not be there. Also, in node 'Simple Makefile', a simple example makefile is introduced. It is then used as an example to introduc

RE: info

Title: RE: info     Gmake has the option "-d" that will output a large amount of very detailed information about what it's doing and why. I suggest you re-direct this to a file. Also, the "-p" option will print out the definitions of all internal macros and targ

info

Hello, I'm sorry to bother you on this e-mail address, but I am working with quiet complex makefiles and would like to know if it exist a debugger or 'tracer' for make. Can you help me ? Regards Bruno ___ Bug-make mailing list [EMAIL PROTECTED] http

Re: Value of $? not set in archive rules (more info)

%% "Robert E. Menteer II" <[EMAIL PROTECTED]> writes: rem> Here is some additional information on the problem. The version rem> used was: GNU Make version 3.79.1, by Richard Stallman and Roland rem> McGrath. Built for hppa1.1-hp-hpux11.00 rem> The problem with $? does not appear when us

Value of $? not set in archive rules (more info)

Here is some additional information on the problem. The version used was: GNU Make version 3.79.1, by Richard Stallman and Roland McGrath. Built for hppa1.1-hp-hpux11.00 The problem with $? does not appear when using the -n option to view which commands will execute. This may be related to a pro

Re: Bug#104130: info typo

Yes, this has been fixed in CVS for a while now. Thanks for the report... -- --- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://www.paulandlesley.

Re: Bug#104130: info typo

Hi, In the info page, on the Phony Targets rule, the very nice example of using phony subdirs for recursive make has: == $(MAKE) -C

FREE Biotech Stock Info! 644

Title: Do you want to capitalize on the Biotech Revolution Do you want to capitalize on the Biotech Revolution? Would you like to add groundbreaking biotech, pharmaceutical and medical device companies to your portfolio mix? Does hearing about exciting IPO and private placement offerings fr

FWD: MORE INFO ON THE PHONE SERVICE

You Are Receiveing This Again, Due To Another Typo In The Last Web Address. $99 Flatrate Longdistance STATE TO STATE / UNLIMITED CALLS GET RID OF THOSE HUGE LONG DISTANCE BILLS. DOESN'T TAKE AWAY FOCUS FROM YOUR PRIMARY PROGRAM!! SO... GET YOUR WHOLE DOWNLINE ON IT FOR RAPID GROWTH IN YOUR CURR