From: Pete Zaitcev <zaitcev@redhat.com>
To: kai@tp1.ruhr-uni-bochum.de
Cc: linux-kernel@vger.kernel.org
Subject: Perl in the toolchain
Date: Fri, 31 Jan 2003 13:39:29 -0500 [thread overview]
Message-ID: <20030131133929.A8992@devserv.devel.redhat.com> (raw)
Kai, what's your opinion? I suspect you missed my posing to l-k
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0301.3/1203.html
-- Pete
Date: Thu, 30 Jan 2003 14:53:59 +0100
From: Konrad Eisele <eiselekd@web.de>
To: "PeteZaitcev" <zaitcev@redhat.com>
Subject: Adding sparc-leon linux to sourcetree
.....
There is also one change I have made on the buildsystem. Because I'm using some
perl inline scripts in the $cmd_xxx the >'< and >$< signs in the inline perl scripts
cause trouble (perl -e '...$x=....'), the >'< because of the echo command, the >$< when
rereading from the xxx..cmd files. Could this be applied to the original file?
scripts/Makefile.lib:
+-------------------------------+
# ===========================================================================
# Generic stuff
# ===========================================================================
# function to only execute the passed command if necessary
# the ' -> '\'' and $ to $$ substitution are done if $(cmd_$(1)) includes a inline perlscript
if_changed = $(if $(strip $? \
$(filter-out $(cmd_$(1)),$(cmd_$@))\
$(filter-out $(cmd_$@),$(cmd_$(1)))),\
@set -e; \
$(if $($(quiet)cmd_$(1)),echo ' $(subst ','\'',$($(quiet)cmd_$(1)))';) \
$(cmd_$(1)); \
echo 'cmd_$@ := $(subst $$,$$$$,$(subst ','\'',$(cmd_$(1))))' > $(@D)/.$(@F).cmd)
----- End forwarded message -----
next reply other threads:[~2003-01-31 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 18:39 Pete Zaitcev [this message]
2003-01-31 19:41 ` Perl in the toolchain Kai Germaschewski
2003-01-31 19:48 ` Jeff Garzik
2003-01-31 19:55 ` Mr. James W. Laferriere
2003-01-31 20:41 ` Sam Ravnborg
2003-01-31 22:50 ` Ben Greear
2003-01-31 21:38 ` J.A. Magallon
2003-01-31 22:22 ` Sam Ravnborg
2003-01-31 23:23 ` Jeff Garzik
2003-02-01 0:29 ` H. Peter Anvin
2003-02-01 12:12 ` Sam Ravnborg
2003-01-31 23:40 ` J.A. Magallon
[not found] ` <mailman.1044055681.1939.linux-kernel2news@redhat.com>
2003-02-01 1:06 ` Pete Zaitcev
2003-02-01 6:02 ` Ryan Anderson
2003-01-31 22:51 ` Roman Zippel
2003-01-31 23:27 ` Jeff Garzik
2003-01-31 23:40 ` J.A. Magallon
2003-01-31 23:40 ` Jeff Garzik
2003-02-01 0:01 ` Roman Zippel
2003-02-01 0:05 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2003-01-31 20:13 Ed Vance
2003-02-01 3:28 ` Scott Robert Ladd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030131133929.A8992@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox