On Sat, 2016-11-19 at 18:49 +0100, Michael Stapelberg wrote:
> With this change, users who have their editor misconfigured when writing
> Makefiles without using 8 spaces for one TAB character will also get a
> friendly error message.
I'm not a fan of this change.
Make's &qu
#x27; && strneq (line, "", 8))
O (fatal, fstart, _("missing separator (did you mean TAB instead
of 8 spaces?)"));
+else if (cmd_prefix == '\t' && strneq (line, " ", 1))
+ O (fatal, fstart,
r" > broken.8.make
echo -e "foo:\n--echo bar" > broken.else.make
Before this commit, running make on these files results in:
$ make -f broken.make
broken.make:2: *** missing separator. Stop.
$ make -f broken.8.make
broken.8.make:2: *** missing separator (did you
r" > broken.8.make
echo -e "foo:\n--echo bar" > broken.else.make
Before this commit, running make on these files results in:
$ make -f broken.make
broken.make:2: *** missing separator. Stop.
$ make -f broken.8.make
broken.8.make:2: *** missing separator (did you
Update of bug #46400 (project make):
Status:None => Duplicate
Assigned to:None => psmith
Open/Closed:Open => Closed
Fixed Release:
"missing separator" error
$(call make_target, my_thing)
___
Reply to this item at:
<http://savannah.gnu.org/bugs/?46400>
___
Message sent via/by Savannah
http://
URL:
<http://savannah.gnu.org/bugs/?46400>
Summary: *** missing separator, when expanding empty define'd
variable
Project: make
Submitted by: None
Submitted on: Sat 07 Nov 2015 08:24:43 PM UTC
Severity:
On Sat, 2015-01-17 at 13:41 -0800, Philip Guenther wrote:
> Paul, I still think $(eval) should have been named
> $(stick-arm-in-woodchipper), to make it less seductive to people
> trying to layer imperative programming on the declarative nature of
> make.
I do agree with you in general. I see alm
On Sat, Jan 17, 2015 at 12:52 PM, SF Markus Elfring
wrote:
>> Of course, if you had actually quoted the relevant lines from your
>> Makefile, we could be more precise.
>
> Thanks for your interest.
>
> Do you get further ideas from an excerpt of my build script
> "parallel-inc.make"?
>
> Lines 24
> Of course, if you had actually quoted the relevant lines from your
> Makefile, we could be more precise.
Thanks for your interest.
Do you get further ideas from an excerpt of my build script "parallel-inc.make"?
Lines 241 - 256:
$(EXIT_CODES_FUNCTIONS_THAT_CHECK_THEIR_SINGLE_PARAMETER_IN_HEADE
On Sat, Jan 17, 2015 at 11:06 AM, SF Markus Elfring
wrote:
> But the software tool "make 4.1-2.2" does not like
> a specific place in this file at the moment.
>
> …
> parallel-inc.make:247: *** missing separator. Stop.
>
>
> The mentioned line has got a leading
Hello,
I can use some phony targets from my build script
as expected.
But the software tool "make 4.1-2.2" does not like
a specific place in this file at the moment.
…
parallel-inc.make:247: *** missing separator. Stop.
The mentioned line has got a leading tab character
for the be
Update of bug #19015 (project make):
Status:None => Works for me
Open/Closed:Open => Closed
___
Follow-up Comment #1:
Sorry, but this is no
On 2/9/07, anonymous <[EMAIL PROTECTED]> wrote:
...
Any attempts to initialize the global variables
LS = ls
FIND = find
failed with error message "*** missing separator. stop". All other commands
like "grep", "rm", "mkdir" and others work.
I tri
URL:
<http://savannah.gnu.org/bugs/?19015>
Summary: Initialisation of variable to "ls" and "find" fails
with "**missing separator"
Project: make
Submitted by: None
Submitted on: Friday 02/09/2007 at 2
ile'...
> makefile:12: *** missing separator. Stop.
Depending on the settings of your system, you might be processing a
completely different makefile from the one you intend to process, since
the makefile in your directory is written with a capital 'M', whereas
both the commandli
%% maxx <[EMAIL PROTECTED]> writes:
m> Reading makefile `makefile'...
m> makefile:12: *** missing separator. Stop.
So, there is a bug in your makefile, at line 12. This isn't a bug in
make.
If you check the GNU make manual there's a chapter listing the error
me
.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Report bugs to <[EMAIL PROTECTED]>.
Reading makefiles...
Reading makefile `makefile'...
makefile:12: *** missing separ
%% "Michael Sterrett -Mr. Bones.-" <[EMAIL PROTECTED]> writes:
msb> Lines 345 and 346 start with spaces instead of tabs. Change that
msb> and it may work much better.
The last rule in the file also has this problem.
msb> That particular error message is not very helpful.
Get a newer ver
Shell command lines in make _MUST_ start with a TAB character. Your
makefile has 8 spaces instead of a TAB in the last two rules. A number
of Windows editors will "helpfully" convert TABs to spaces automatically
for you; find one that doesn't when you edit makefiles.
If you get a newer version
Lines 345 and 346 start with spaces instead of tabs. Change that and it
may work much better. That particular error message is not very helpful.
Michael Sterrett
-Mr. Bones.-
[EMAIL PROTECTED]
___
Bug-make mailing list
[EMAIL PROTECTED]
http://mai
copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Report bugs to <[EMAIL PROTECTED]>.
Reading makefiles...
Reading makefile `makefile'...
makefile:345: *** missing separator. Stop.
when using this makefile:
<>
I have no clu
%% Larry Knibb <[EMAIL PROTECTED]> writes:
lk> I'm trying to 'make test' to check a Perl module before installing
lk> on Win32 and I get
lk> "makefile:770: *** missing separator. Stop."
lk> I had a look around line 770 of the makefile and
I'm trying to 'make test' to check a Perl module before installing on Win32
and I get
"makefile:770: *** missing separator. Stop."
I had a look around line 770 of the makefile and it looks like this:
765: pm_to_blib: $(TO_INST_PM)
766: @$(PERL) "-I$(INST_A
24 matches
Mail list logo