From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: Jan Viktorin <viktorin@rehivetech.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: [dpdk-dev] [PATCH] app/test: call objdump in platform-independent way
Date: Fri, 17 Jun 2016 14:52:47 +0200 [thread overview]
Message-ID: <1466167967-12873-1-git-send-email-viktorin@rehivetech.com> (raw)
Using of the /dev/stdin generates a warning when compiling on FreeBSD:
objcopy: Warning: '/dev/stdin' is not an ordinary file
app/test/Makefile:78: recipe for target 'test_resource_c.res.o' failed
# ls -l /dev/stdin
lrwxr-xr-x 1 root wheel 4 Jun 17 12:24 /dev/stdin -> fd/0
Replace /dev/stdin by a temporary file.
Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
Reported-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
app/test/Makefile | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/app/test/Makefile b/app/test/Makefile
index 5e3ebdc..36ff089 100644
--- a/app/test/Makefile
+++ b/app/test/Makefile
@@ -43,13 +43,14 @@ define linked_resource
SRCS-y += $(1).res.o
$(1).res.o: $(2)
@ echo ' MKRES $$@'
+ $Q ln -fs $$< resource.tmp
$Q $(OBJCOPY) -I binary -B $(RTE_OBJCOPY_ARCH) -O $(RTE_OBJCOPY_TARGET) \
--rename-section \
.data=.rodata,alloc,load,data,contents,readonly \
- --redefine-sym _binary__dev_stdin_start=beg_$(1) \
- --redefine-sym _binary__dev_stdin_end=end_$(1) \
- --redefine-sym _binary__dev_stdin_size=siz_$(1) \
- /dev/stdin $$@ < $$<
+ --redefine-sym _binary_resource_tmp_start=beg_$(1) \
+ --redefine-sym _binary_resource_tmp_end=end_$(1) \
+ --redefine-sym _binary_resource_tmp_size=siz_$(1) \
+ resource.tmp $$@ && rm -f resource.tmp
endef
ifeq ($(CONFIG_RTE_APP_TEST_RESOURCE_TAR),y)
--
2.8.0
next reply other threads:[~2016-06-17 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 12:52 Jan Viktorin [this message]
2016-06-17 13:19 ` Thomas Monjalon
2016-06-17 13:33 ` Thomas Monjalon
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=1466167967-12873-1-git-send-email-viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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;
as well as URLs for NNTP newsgroup(s).