Update of bug #52267 (project make):
Status:None => Duplicate
Open/Closed:Open => Closed
___
Follow-up Comment #1:
This is a duplicate of
-modules\"" -DNDEBUG -D_
_ANDROID_API__=26 -MMD -MF apps/lib/libapps-lib-s_socket.d.tmp -MT apps/lib/liba
pps-lib-s_socket.o -c -o apps/lib/libapps-lib-s_socket.o apps/lib/s_socket.c
make[1]: *** No rule to make target 'crypto/(0x55ae24c35998).o',
needed by 'libcrypto.a'
URL:
<http://savannah.gnu.org/bugs/?52267>
Summary: No rule to make target, when re-including file
after being generated
Project: make
Submitted by: kvho
Submitted on: Mon 23 Oct 2017 11:24:53 AM CEST
Sever
On 27/11/15 17:58, th...@vmware.com wrote:
Jonny Grant writes:
> > If you do it that way, now you've got two different formats for the
> > same message. This can be confusing to users, and certainly
> > complicates factors if there is software sitting on top of Make and
> > ope
Jonny Grant writes:
> > If you do it that way, now you've got two different formats for the
> > same message. This can be confusing to users, and certainly
> > complicates factors if there is software sitting on top of Make and
> > operating on the messages (continuous integration / au
On 26/11/15 00:04, th...@vmware.com wrote:
Jonny Grant writes:
>
>
> On 25/11/15 13:59, th...@vmware.com wrote:
> > Jonny Grant writes:
> > > Hello
> > >
> > > Could line numbers be added to output for the case where it says
Jonny Grant writes:
>
>
> On 25/11/15 13:59, th...@vmware.com wrote:
> > Jonny Grant writes:
> > > Hello
> > >
> > > Could line numbers be added to output for the case where it says "No
> > > rule to make targe
On 25/11/15 13:59, th...@vmware.com wrote:
Jonny Grant writes:
> Hello
>
> Could line numbers be added to output for the case where it says "No
> rule to make target" please?
>
> Example below. GNU Make 4.1
>
> I'm not on this list, so
Jonny Grant writes:
> Hello
>
> Could line numbers be added to output for the case where it says "No
> rule to make target" please?
>
> Example below. GNU Make 4.1
>
> I'm not on this list, so please include my email address is any
> replies Regar
Hello
Could line numbers be added to output for the case where it says "No
rule to make target" please?
Example below. GNU Make 4.1
I'm not on this list, so please include my email address is any replies
Regards, Jonny
makefile.mak
%.o : %.d
all: test.o
echo processing
I am getting this message:
make[2]: *** No rule to make target `dep-gnu-pw-mgr.1', needed by
`gnu-pw-mgr.1'. Stop.
make[2]: Leaving directory `/u/gnu/proj/gnu-pw-mgr-bld/doc'
make[1]: *** [all-recursive] Error 1
Seems like a real neophyte problem, but this neophyte has a prob
On 04/11/15 11:25, Bruce Korb wrote:
I am getting this message:
Never mind. I was playing with "$(call ...)" stuff and the text was permuted
in an unexpected way...Sorry.
___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/list
hi,
i am developing the pjsip application for bb 10.
after building the code i am facing the error : no rule to make target
simulator debug stop..
plzzz help me..
thanks in advance
___
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org
Update of bug #18435 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Fixed Release:
; The command (1)
> make elf
> gives the result "make: *** No rule to make target `elf'. Stop."
> when no makefile exists.
>
> The command (2)
> make -f mmm aaa
> gives the result
> make: mmm: No such file or directory
> make: *** No rule to make tar
Please keep my email-address confidential, as I don't want to get spam.
The command (1)
make elf
gives the result "make: *** No rule to make target `elf'. Stop."
when no makefile exists.
The command (2)
make -f mmm aaa
gives the result
make: mmm: No such file or dire
PS> what does this information do for you?
I don't know, all I am thinking is hooks (i.e., differing error
messages that can be post processed by:) for a future hand holding
system so one can "ask what went wrong?" And have super basic tutorial
information given... (target implementation date 2050
On Tue, 2008-06-10 at 01:49 +0800, [EMAIL PROTECTED] wrote:
> Do differentiate error messages from different triggers,
I'm not sure this is fruitful, but to reiterate: there are no different
triggers. There is one procedure. It looks something like this (100%
psuedo code):
rule *r;
Do differentiate error messages from different triggers, all in
preparation for a perl-like
See perldiag for explanations of all Perl's diagnostics. The "use
diagnostics" pragma automatically turns Perl's normally terse warnings
and errors into these longer forms.
hand holding facility for
On Mon, 2008-06-09 at 12:02 +0800, [EMAIL PROTECTED] wrote:
> Maybe whatever prints messages prefixed by
>make: *** No rule to make target
> is called from several different points in the code, and could give
> finer grained messages, all still on one line.
>
> Maybe the
PS> I don't understand the distinction you're making here between "no rule
PS> at all" and "no best rule" (what's a "best rule"?), and just "no rule".
Maybe whatever prints messages prefixed by
make: *** No rule to make target
is cal
On Mon, 2008-06-09 at 11:28 +0800, [EMAIL PROTECTED] wrote:
> OK, OK, is perhaps this message,
> make: *** No rule to make target `z', needed by `a'. Stop.
> is actually triggered by several different conditions, and could
> instead be refashioned into several mo
OK, OK, is perhaps this message,
make: *** No rule to make target `z', needed by `a'. Stop.
is actually triggered by several different conditions, and could instead
be refashioned into several more exact messages, e.g., no rule at all,
no best
On Fri, 2008-06-06 at 19:49 +0800, [EMAIL PROTECTED] wrote:
> All is well:
> $ cat Makefile
> all:z.bak
> %.bak:;
> $ make
> make: Nothing to be done for `all'.
> Until we add a %:
> $ cat Makefile
> all:z.bak
> %.bak:%;
> $ make
>
On Fri, Jun 6, 2008 at 5:49 AM, <[EMAIL PROTECTED]> wrote:
> All is well:
> $ cat Makefile
> all:z.bak
> %.bak:;
> $ make
> make: Nothing to be done for `all'.
> Until we add a %:
> $ cat Makefile
> all:z.bak
> %.bak:%;
> $ make
> make: ***
All is well:
$ cat Makefile
all:z.bak
%.bak:;
$ make
make: Nothing to be done for `all'.
Until we add a %:
$ cat Makefile
all:z.bak
%.bak:%;
$ make
make: *** No rule to make target `z.bak', needed by `all'. Stop.
Suddenly it can't find the rule anymore.
URL:
<http://savannah.gnu.org/bugs/?18435>
Summary: no rule to make target whose name contains close
parenthesis
Project: make
Submitted by: mdorey
Submitted on: Friday 12/01/2006 at 18:52
Severity: 3 -
27 matches
Mail list logo
