i'm reading section 10.5.5 of the gnu make manual and i'm confused
about the definition of terminal rules that i find there:
One choice is to mark the match-anything rule as terminal by defining
it with a double colon. When a rule is terminal, it does not apply
unless its prerequisites
Robert P. J. Day wrote:
One choice is to mark the match-anything rule as terminal by defining
it with a double colon. When a rule is terminal, it does not apply
unless its prerequisites actually exist. Prerequisites that could be
made with other implicit rules are not good enough. In other
%% Eric Hanchrow [EMAIL PROTECTED] writes:
eh At first, I thought this behavior was a bug, but then I realized
eh that it's working exactly as specified: notdir treats its argument
eh as a _whitespace-separated_ list of file names. That makes it
eh difficult to deal with file names that
Here's an example makefile that doesn't do what I want.
name := I have a space/x
worse:
@echo input is $(name)
@echo output is $(notdir $(name))
# I see
# input is I have a space/x
# output is I have a x
# But I wish I'd have seen
#
ok, i have a far more specific question about double-colon rules.
it has to do with their use in paul's multi-arch build recipe here:
http://make.paulandlesley.org/multi-arch.html#advanced
part of that makefile are the rules:
Makefile : ;
%.mk :: ;
% :: $(OBJDIR) ; :
and the question
%% Martin Sebor [EMAIL PROTECTED] writes:
ms ...are attached. I don't know enough to say how serious the
ms failures are but I'm hoping you'll find the results helpful.
Thanks Martin. Good stuff.
I'll have to think about the best way to handle systems like AIX which
use non-traditional
%% Martin Sebor [EMAIL PROTECTED] writes:
ms Here's the version output. Seems pretty ancient:
ms $ perl -v
ms This is perl, version 5.004_04 built for irix-n32
Huh. OK, I'll add the second argument to mkdir().
--
Hi,
The simplest way to do this is to convert every space in the
file name to a ? (since ? won't appear in a real file name we can
safely use it)
Although in practice that is generally true, that could be dangerous
assumption:
[host]- touch ?file
[host]- ls -l ?file
-rw-r--r-- 1 user
i'm pretty sure i asked about this long ago but i managed to misplace
the response(s). i'm interested if anyone has a sample make-based
build structure for building an entire linux-based embedded system.
that system would involve configuring, compiling and combining various
standard bits of an
On 2006-3-4 9:22 UTC, CARTER-HITCHIN, David, FM wrote:
The chances of anyone having ?'s in their filenames are approximately
equal, I'd say, to having spaces :-)
Depends on the platform. This question most often arises on msw,
where '?' is forbidden in filenames while spaces are all too
Eric Hanchrow wrote:
Here's an example makefile that doesn't do what I want.
name := I have a space/x
worse:
@echo input is $(name)
@echo output is $(notdir $(name))
# I see
# input is I have a space/x
# output is I have a x
# But I wish
I have just obtained a Dell Precision 670n workstation with a 3.6
GHzIntel Xeon Processor running Red Hat Enterprise Linux WS v4 for EM64T
64bit system. I am also using The Portland Group 64bit Linux complete
compilers 6.1. When I run a Make file I am getting this error:
make[4]:
%% Matt England [EMAIL PROTECTED] writes:
me Preliminary results in complex (but not all) conditions show that
me make3.81-beta4 compiled under mingw does not always stop when
me experiencing an error while executing commands in a rule.
me I can provide more details tomorrow (after I get
13 matches
Mail list logo
