From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/ipsec-tools
Date: Sun, 23 Sep 2007 02:56:22 -0700 (PDT) [thread overview]
Message-ID: <20070923095622.B34E530075@busybox.net> (raw)
Author: ulf
Date: 2007-09-23 02:56:21 -0700 (Sun, 23 Sep 2007)
New Revision: 19959
Log:
Fix syntax error when using addprefix in ipsec-tools.mk
Modified:
trunk/buildroot/package/ipsec-tools/ipsec-tools.mk
Changeset:
Modified: trunk/buildroot/package/ipsec-tools/ipsec-tools.mk
===================================================================
--- trunk/buildroot/package/ipsec-tools/ipsec-tools.mk 2007-09-23 09:55:17 UTC (rev 19958)
+++ trunk/buildroot/package/ipsec-tools/ipsec-tools.mk 2007-09-23 09:56:21 UTC (rev 19959)
@@ -112,14 +112,14 @@
$(TARGET_DIR)/$(IPSEC_TOOLS_TARGET_BINARY_RACOON) \
$(TARGET_DIR)/$(IPSEC_TOOLS_TARGET_BINARY_RACOONCTL)
ifneq ($(BR2_HAVE_MANPAGES),y)
- rm -f $(addprefix $(TARGET_DIR)/usr/man/,
+ rm -f $(addprefix $(TARGET_DIR)/usr/man/, \
man3/ipsec_strerror.3 man3/ipsec_set_policy.3 \
man5/racoon.conf.5 \
man8/racoonctl.8 man8/racoon.8 \
man8/plainrsa-gen.8 man8/setkey.8)
endif
ifeq ($(strip $(BR2_PACKAGE_IPSEC_TOOLS_LIBS)), y)
- install -D $(addprefix $(IPSEC_TOOLS_DIR)/src/,
+ install -D $(addprefix $(IPSEC_TOOLS_DIR)/src/, \
libipsec/.libs/libipsec.a libipsec/.libs/libipsec.la \
racoon/.libs/libracoon.a racoon/.libs/libracoon.la) \
$(STAGING_DIR)/lib
next reply other threads:[~2007-09-23 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 9:56 ulf at uclibc.org [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 19:56 [Buildroot] svn commit: trunk/buildroot/package/ipsec-tools jacmet at uclibc.org
2007-11-29 13:06 ulf at uclibc.org
2007-06-25 9:41 aldot at uclibc.org
2006-11-22 20:26 aldot at uclibc.org
2006-11-20 13:37 aldot at uclibc.org
2006-11-17 11:48 aldot at uclibc.org
2006-08-28 13:46 aldot at uclibc.org
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=20070923095622.B34E530075@busybox.net \
--to=ulf@uclibc.org \
--cc=buildroot@busybox.net \
/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