From: bernhard@bwalle.de
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <walle@corscience.de>
Subject: [ptxdist] [PATCH] lsof: Use cross ar and ranlib
Date: Mon, 12 Mar 2012 17:00:14 +0100 [thread overview]
Message-ID: <1331568014-17039-1-git-send-email-bernhard@bwalle.de> (raw)
From: Bernhard Walle <walle@corscience.de>
The lsof build system uses host ar and ranlib. With that patch it uses
the tools provided by the cross toolchain.
On a Gentoo system, without that patch, I get following error:
ar cr liblsof.a ckkv.o cvfs.o dvch.o fino.o isfn.o lkud.o pdvn.o prfp.o ptti.o rdev.o regex.o rmnt.o rnam.o rnch.o rnmh.o snpf.o
ranlib liblsof.a
make[2]: Leaving directory `/home/tweber/work/COR4098_ptxdist/platform-upmed/build-target/lsof-4.81.dfsg.1/lib'
arm-cortexa8-linux-gnueabi-gcc -DLINUXV=32006 -DGLIBCV=213 -DHASIPv6 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE \
-DHAS_STRFTIME -DLSOF_VSTR=\"3.2.6-gentoo\" -O2 -c -o usage.o usage.c
arm-cortexa8-linux-gnueabi-gcc -o lsof dfile.o dmnt.o dnode.o dproc.o dsock.o dstore.o arg.o main.o misc.o node.o print.o proc.o \
store.o usage.o util.o -L./lib -llsof
./lib/liblsof.a: could not read symbols: Archive has no index; run ranlib to add one
collect2: ld returned 1 exit status
Signed-off-by: Bernhard Walle <walle@corscience.de>
---
rules/lsof.make | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/rules/lsof.make b/rules/lsof.make
index b021758..4fa4ac9 100644
--- a/rules/lsof.make
+++ b/rules/lsof.make
@@ -41,12 +41,14 @@ LSOF_PATH := PATH=$(CROSS_PATH)
LSOF_ENV := \
$(CROSS_ENV) \
- LINUX_HASSELINUX=N
+ LINUX_HASSELINUX=N \
+ LSOF_AR="$(CROSS_AR) cr"
LSOF_MAKEVARS := \
$(CROSS_ENV_CC) \
LSOF_USER=none \
- DEBUG=-O2
+ DEBUG=-O2 \
+ RANLIB="$(CROSS_RANLIB) liblsof.a"
#
# autoconf
--
1.7.9.3
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-03-12 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 16:00 bernhard [this message]
2012-03-13 9:34 ` Michael Olbrich
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=1331568014-17039-1-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
--cc=walle@corscience.de \
/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