kann mir da bitte jemand weiter helfen
Leide nicht. Ihre Problem ist irgendwo anders - es gibt keine Bug mit make(1)
hier. Vielleicht koennen sie Hilfe finden auf einen Mailing Liste oder Website
fuer dahdi.
(Wenn sie meinen schrecklichen Denglish verstehen koennen.)
All you have to do is use recursive assignment (=) and NOT simple
assignment (:=).
The attachment did use =, making the coworker's assertion odder. The
lack of need for target-specific variables can be illustrated with a
simple example:
mart...@whitewater:~/playpen/make-splitting$ cat
From make's NEWS file for the 3.81 release:
* WARNING: Backward-incompatibility!
In order to comply with POSIX, the way in which GNU make processes
backslash-newline sequences in recipes has changed. If your makefiles
use backslash-newline sequences inside of single-quoted strings
Follow-up Comment #1, bug #27374 (project make):
I see the error message:
mart...@whitewater:~/playpen/make-27374$ make -f make.bug /dev/null echo
success
make.bug:1: make.bug: Too many open files
success
mart...@whitewater:~/playpen/make-27374$
The failure happens (for me) here in the
You misunderstand something.
it outputs:
VAR=foo VAR2=bar VAR3=foo
That's only a small fraction of what I see, with make-3.81. This is what I see:
mart...@whitewater:~/tmp/bug-make-2009-05-07$ make
make var1
make[1]: Entering directory `/home/martind/tmp/bug-make-2009-05-07'
VAR=foo
Dorey
Cc: bug-make@gnu.org
Subject: Re: conditionals not working for conditional variables in sub-make?
Hi,
2009/5/7 Martin Dorey mdo...@bluearc.com:
That's only a small fraction of what I see, with make-3.81. This is what I
see:
[...]
VAR=foo VAR2=bar VAR3=foo
But here VAR2 should be foo
to see the light. Imagine in the all
rule, that instead of running make var1, you ran
a-script-which-happens-to-invoke-make-var1.
-Original Message-
From: Szekeres István [mailto:szeke...@iii.hu]
Sent: Thursday, May 07, 2009 14:40
To: Martin Dorey
Cc: bug-make@gnu.org
Subject: Re
, hence empty.
-Original Message-
From: Szekeres István [mailto:szeke...@iii.hu]
Sent: Thursday, May 07, 2009 14:50
To: Martin Dorey
Subject: Re: conditionals not working for conditional variables in sub-make?
2009/5/7 Martin Dorey mdo...@bluearc.com:
VAR become foo when the var1 rule
This is not a bug in make. It may be a problem with the makefile in question.
Google has a number of matches for 'mpfr no such file or directory' although
none of them grabbed my attention as relevant. I see there's an MPFR mailing
list. That would be the best place to ask, if you've
Follow-up Comment #1, bug #25697 (project make):
Can reproduce with latest make from CVS. ns is null at the penultimate
line:
2175/* In case user set .DEFAULT_GOAL to a non-existent
target
2176 name let's just enter this name into the table and
let
The link to the Errors in Commands section,
http://www.gnu.org/software/make/manual/make.html#Errors, explains what
the - is for.
From: bug-make-bounces+mdorey=bluearc@gnu.org
[mailto:bug-make-bounces+mdorey=bluearc@gnu.org] On Behalf Of Yakup
Akbay
to the current
source and generate a patch to attach to the bug. Someone might then
commit the changes.
-Original Message-
From: jida...@jidanni.org [mailto:jida...@jidanni.org]
Sent: Friday, January 23, 2009 12:16
To: Martin Dorey
Cc: m...@packages.debian.org; bug-make@gnu.org
Subject: Re: make
it looks like this bug is still there
And it looks like there are several other instances of it too.
What I am looking for is some help writing a makefile that
is simple enough to post in a bug report.
I had a few goes but it looks like the variable_buffer is always already
big enough by the
, 2009 13:44
To: bug-make@gnu.org
Subject: Re: Bug in make-3.81: variable_buffer moves out from under
buffer
Martin Dorey mdorey at bluearc.com writes:
And it looks like there are several other instances of it too.
That's what I was afraid of. I looked at the other places where
xrealloc
could
=bluearc@gnu.org] On Behalf Of David
Wuertele
Sent: Tuesday, January 20, 2009 15:07
To: bug-make@gnu.org
Subject: Re: Bug in make-3.81: variable_buffer moves out from under
buffer
Martin Dorey mdorey at bluearc.com writes:
In the original makefile, does
the long rule really not contain any
It's not clear whether you're complaining about rules whose commands are
run even with -n or -t, or whether you're complaining about commands run
by eg $(shell).
Assuming the former, the documentation already explains:
The `-n', `-t', and `-q' options do not affect command lines that begin
make --help in CVS has been updated with the recipe clarification but
still says:
-n, --just-print, --dry-run, --recon\n\
Don't actually run any recipe; just print
them.\n
I agree that make --help is on particularly dubious ground when saying
any recipe. Saying
To install this software correctly make must run as follows
That sounds like a bug in the documentation you're reading rather than a
bug in make.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Siraj
Rathore
Sent: Friday, November 21, 2008
last updated 04 April 2000, of `The GNU Make
Manual', for `make', Version 3.79. I use: GNU Make
version 3.79.1
(Wow, that's pretty old skool.)
It seems as if it is not possible to change the value
of a variable inside an ?ifeq? conditional that test
against that very variable
That
URL:
http://savannah.gnu.org/bugs/?24509
Summary: doc for wildcard expansion in commands could be
clearer
Project: make
Submitted by: mdorey
Submitted on: Thu 09 Oct 2008 06:20:47 PM GMT
Severity: 3 - Normal
Follow-up Comment #3, bug #24251 (project make):
I reproduced the behavior you saw without svn by replacing the end of the
makefile with:
$(ECOS_MAKE) : $(ECOS_DIR)
$(ECOS_DIR) :
mkdir -p $(ECOS_DIR)/include/pkgconf/
{
echo 'ECOS_GLOBAL_CFLAGS = -mcpu=arm7tdmi -Wall
Follow-up Comment #1, bug #24251 (project make):
Looks like https://savannah.gnu.org/bugs/?102 to me.
___
Reply to this item at:
http://savannah.gnu.org/bugs/?24251
___
Message sent via/by
It's not dry when the command in question is a recursive call to make either.
That's because, in both cases, it's more useful to more people to behave this
way by default. If you want a different behavior, you can have your including
makefile decide not to include if the included file doesn't
The order of generation of any targets that don't have dependencies is not
documented. This is deliberate because there is no defined ordering. The
targets may even be generated in parallel.
- Original Message -
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: bug-make@gnu.org
MAKEFILE_STACK.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 28, 2008 03:01
To: bug-make@gnu.org
Cc: [EMAIL PROTECTED]; Martin Dorey; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [bug #23928] Add MAKEFILE variable
Philip Guenther wrote:
BTW, $(lastword
Try make -f and.mk A=22 B=44.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim
Murphy
Sent: Tuesday, June 17, 2008 09:31
To: bug-make@gnu.org
Subject: Re: Help : how to use $(or condition ) $(and condition )
inmakefile
Hi,
I have amended an
This example is certainly simple, thanks.
The Makefile isn't telling make that the rule for making c from d will
also update b. Make caches modification times and doesn't know to
invalidate its cache of b's time.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Didn't happen for me with the same makefile and similar make, kernel and
architecture. In any case it sounds more like bad ram. Suggest burning
a CD of http://www.memtest.org/ and leaving it running overnight.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
When a make command MAKE
Any bug report should contain:
What exactly did you type?
What did the computer say? Paste all of the output into the bug report.
Why do think that is a bug?
That last point is the most interesting. You don't say what you expect
make to do. You don't say which
I need the latest and greatest for Red Hat 9
Try http://rpmfind.net/linux/rpm2html/search.php?query=make. Please
though, if you need more help, bear in mind that this mailing list is
for bugs with make itself.
From: [EMAIL PROTECTED]
[mailto:[EMAIL
You haven't installed docbook2man but libieee1284-0.1.6 seems to require
it. Google's first match for your error message looks to have some
advice for exactly this error:
http://canon-fb330p.sourceforge.net/howto-fb630p-english
This mailing list is for bugs with make. That isn't a make bug.
http://www.gnu.org/software/make/manual/make.html#Makefile-Basics
suggests you follow your final suggestion, as you (seem to) have a
$(srcdir) variable. It suggests ./ otherwise, although I've tripped
over doing that and generally use $(CURDIR)/ myself.
It's helpful elsewhere that ./file and
Follow-up Comment #1, bug #21198 (project make):
In which order do you think the prerequisites should be built? And why?
If C should be built before D, for example, then we have to tell make that D
depends on C. Mentioning D after C in a list of prerequisites is not
sufficient. Mentioning D
Follow-up Comment #2, bug #21198 (project make):
Robin Williams points out there is a different issue here which can be seen
by adding $ to the echo command, so the test reads:
all : A B C
all : ; @echo $@ -- $^, $
all : D E F
A B C D E F : ; @echo $@
With that change, make-3.80 says:
A
B
C
.SUFFIXES = .in
Your makefile works for me (with make foo, given a foo.in) if I change that
line to read:
.SUFFIXES: .in
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ludovic Courtès
Sent: Sunday, August 12, 2007 00:30
To: bug-make@gnu.org
That sounds unlikely to be a bug with make, so the help-make list would
be more appropriate. The make maintainer has a paper on dependencies
which you can find here:
http://web.archive.org/web/20061205233409/http://make.paulandlesley.org/
autodep.html
That focuses on automatic generation of
Follow-up Comment #2, bug #20033 (project make):
(I can reproduce a crash with that example.)
___
Reply to this item at:
http://savannah.gnu.org/bugs/?20033
___
Message sent via/by
Follow-up Comment #1, bug #19900 (project make):
See the note about double expansion here:
http://www.gnu.org/software/make/manual/make.html#Eval-Function
You want the rule to read:
echo $$(var)
That then works for me.
___
Reply to
Follow-up Comment #2, bug #19035 (project make):
Also, if your source was last written on machine A and you're now trying to
compile those files on machine B and machine B's clock is so far behind
machine A's that the source files' timestamps still appear to be the future,
then you'd see this
Yes, that is a bug *while running* make. Perhaps we should rename the mailing
list to [EMAIL PROTECTED] or otherwise try to indicate in the error message
that this isn't likely to be a bug in make. Perhaps we're doomed though. For
one thing, this bug looks unlikely to be a bug in lprng,
2007-02-07-15:28:15.682 sbkdgdbdev1 Init_tempfile: bad tempdir
'/var/spool/lpd/%P'
...
*** glibc detected *** double free or corruption (fasttop): 0x080a0bc8
***
Now those are definite lprng issues. Suggest googling or taking that to
an lprng list. This list is only for bugs in make. We try
help-make might be an appropriate mailing list to send this request to.
Googling for a make tutorial might turn up something useful. There's always
the make manual, which contains a fairly simple example:
http://www.gnu.org/software/make/manual/make.html#Simple-Makefile
You might, however,
Follow-up Comment #1, bug #18963 (project make):
-include never issues warnings or errors. I'd previously suggested a change
to that section of the manual in
http://lists.gnu.org/archive/html/bug-make/2007-01/msg2.html. Perhaps
you'd like to suggest a further or alternative change to make
03, 2007 19:57
To: Martin Dorey; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
bug-make@gnu.org
Subject: Re: RE: [bug #18641] GNUmake 3.81,$(error ) sometimes unable to stop
make process
Hello, Martin Dorey,
Thank you very much for your investigation, now I've realized that the source
To get the behavior you want, you need the rule for $(_p_SubprjsMade) to fail
when its invocation of ${MAKE} -f $(_p_mk_MakeSubPrjs) fails. Suggest
rewriting the last two lines as:
@${MAKE} -f $(_p_mk_MakeSubPrjs) \
touch $@
(echo -n $@ is fine - touch $@ is just more usual
.
-
Martin's Outlook, BlueArc Engineering
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin
Dorey
Sent: Saturday, December 30, 2006 7:05
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
bug-make
it fails with a message saying that target cannot
be built.
That's close to what it says but the OP's right that, strictly speaking, the
message make produces isn't actually true. If it said no rule whose
prerequisites can be built to make target then it would be true but verbose.
I can
p[-1] = '\0';
What makes you think this is a compilation error? Do you have a
compiler error message for us? I suspect that you're just worried about
indexing an array with -1. p isn't an array. It's previously been
assigned by:
p = name + strlen (name);
So -1 is only an invalid
Did you miss the fact that p is const?
Doh, yes, sorry.
-
Martin's Outlook, BlueArc Engineering
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
Isn't this more relevant? (Quoting from here on.)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul D. Smith
Sent: Saturday, November 25, 2006 14:09
To: Paul D. Smith; [EMAIL PROTECTED]; bug-make@gnu.org
Subject: [bug #18369] pattern rules don't work with spaces in filenames
However, your point about programs invoked by make inheriting the
setrlimit() is definitely something that seems problematic. Perhaps
GNU
make could change the stack limit back to what it was after it forks
but
before it execs its child. I wonder what happens if you change a
limit to
.
The non-ASCII characters seem to work fine.
-
Martin's Outlook, BlueArc Engineering
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 16:22
To: Jon Grant
Cc: Martin Dorey; bug-make@gnu.org; Dan Jacobson
Subject
an error from make.
-
Martin's Outlook, BlueArc Engineering
-Original Message-
From: Paul Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 18:27
To: Martin Dorey
Cc: Jon Grant; bug-make@gnu.org; Dan Jacobson
Subject: RE: can't get far
Using heap, which requires a system call to get more memory
(It doesn't affect the main point of Paul's reply but just for academic
interest) no it doesn't:
[EMAIL PROTECTED]:~/playpen$ cat ten-thousand-mallocs.c
#include stdlib.h
int main() {
for (int ii = 0; ii != 10 * 1000; ++ ii) {
http://www.gnu.org/software/make/manual/html_node/Flavors.html
How about expanding:
The two flavors are distinguished in how they are defined and in what
they do when expanded.
To say:
The two flavors are distinguished in how they are defined, in what they
do when expanded and in which phase
base = xxx-$(shell date '+%Y%m%d-%H%M%S')
Perhaps you wanted := instead of =. The difference is explained in (for
example):
http://www.gnu.org/software/make/manual/html_node/Reading-Makefiles.html
#Reading-Makefiles
-
Martin's Outlook, BlueArc Engineering
all variables are expanded exactly once - whether they are immediate
or
deferred
No. It might sound like that but that's definitely, definitely,
definitely not what happens. Deferred variables are expanded again
every time they're used. I thought perhaps I'd quoted the wrong part of
the
I don't know why.
Sounds like
a bug I hit too - https://savannah.gnu.org/bugs/?func=detailitemitem_id=1516
- which is fixed in make-3.81.
2. some compare funcitons like
compare of numbers maybe usefull
Yeah, using
the Peano numbers gets tedious after the initial
thrill at using
Thanks for your polite report. I think you've been bitten by one of
make's design quirks, documented by this section in the manual ($ is an
automatic variable):
Conditional Statements
--
All instances of conditional syntax are parsed immediately, in their
entirety;
A quick google for the error message turned up a fourth line, saying:
!!! If you need support, post the topmost build error, NOT this status message.
However, this list is for bugs in gnu make and your problem is far more likely
to be with something gentoo-specific. We don't know anything
Any intelligent operating system will store timestamps in a
canonical format that does not jump around wildly when changing
timezones or entering/exiting daylight savings.
Yes, and Windows does this.
I don't use Windows so I don't know how it works: maybe it does the
intelligent thing, too,
Follow-up Comment #7, bug #9062 (project make):
From the make ChangeLog:
2002-10-03 Paul D. Smith [EMAIL PROTECTED]
Version 3.80 released.
2002-06-06 Paul D. Smith [EMAIL PROTECTED]
...
* read.c (read_all_makefiles): Create a new built-in variable,
MAKEFILE_LIST.
make could not figure out full graph of implicit rules
From the info pages:
4.12.2 Static Pattern Rules versus Implicit Rules
...
An implicit rule _can_ apply to any target that matches its
pattern,
but it _does_ apply ... only when the prerequisites can be found.
...
By
Follow-up Comment #15, bug #16132 (project make):
I've been using make 3.80 with cygwin sh.exe quite comfortably
for the past 2 years.
But which make 3.80? The Cygwin one or the Windows native one? They're
quite different configurations. If you're trying to replace a Cygwin make
with a
I'm between a rock and a hard place.
I know - I'm in a similar position. Having code which reliably
generates rules (with $eval) is a powerful feature and, once you've
tasted it, it's hard to give it up. However, I've been using the 3.81
beta builds very successfully on a number of platforms
Title: help
This mailing list is for reporting
and discussing bugs in make rather than for help with installation
difficulties.
You would probably be better off
downloading an executable from, perhaps, http://www.mingw.org/download.shtml
or using Cygwin's setup tool. You'd be even
Follow-up Comment #10, bug #15757 (project make):
It's a long shot and Paul's method looks like a more constructive way of
progressing but I just thought I'd mention bug #15534. There, make got
confused by an apparent inode number collision, caused by only considering
the bottom 32 bits of the
(
As documented in info make, 10.5.1:
`%' in a prerequisite of a pattern rule stands for the same stem
that was matched by the `%' in the target. In order for the pattern
rule to apply, its target pattern must match the file name under
consideration, and its prerequisite patterns must name
I didn't succeed to find ( ) the way to make the MAKE to stop after the
predefined number of errors has occurred. ( or after the some file has
failed to compile )
make does, by default, stop at the first error it encounters. (Perhaps that
isn't sufficiently clear in the manual - you could
NFS filesystems (at least not NFSv2 or NFSv3) don't support sub-second
timestamps
That's definitely not true. NFSv3 supports nanosecond timestamp
resolution. This isn't just a theoretical capability. I'm looking at a
file on a Solaris box exported with NFSv3 to a Linux client, showing a
, 2005 11:08
To: Martin Dorey
Cc: [EMAIL PROTECTED]; bug-make@gnu.org
Subject: RE: GNU Make 3.80 problem on Solaris 8
%% Martin Dorey [EMAIL PROTECTED] writes:
NFS filesystems (at least not NFSv2 or NFSv3) don't support
sub-second
timestamps
md That's definitely not true. NFSv3 supports
Can you explain me why the del command can not be found?
del is part of cmd.exe, not a separate program. cmd /c del *.h will work. rm
*.h will probably work (if you have enough of cygwin installed to run make,
then you probably have rm).
I have a problem with gmake.
This list is really
Google suggests that your error message comes from the cygwin dll. I
notice that you're using a version of make that's more than 3 years old.
Perhaps you might like to see if the problem's reproducible with the
latest released version of cygwin and its build of make? All of the
google matches I
Regardless of which gcc you're using, you appear to be using the cygwin
version of make - and it's the cygwin dll in that make process that's
hit an error. So you need to report a cygwin problem but, I'd suggest
(again), first try a newer version of cygwin.
-
201 - 274 of 274 matches
Mail list logo
