From: Dietmar Hahn <dietmar.hahn@ts.fujitsu.com>
To: xen-devel@lists.xen.org
Subject: Error on make dist in xen-unstable
Date: Thu, 07 Mar 2013 10:11:27 +0100 [thread overview]
Message-ID: <4168930.OQMBFBY8PY@amur> (raw)
Hi,
I cloned a fresh xen-unstable tree and did:
# ./configure
# make dist
...
ld -r -d -nostdlib -L/home/hahn/Src/Xen/WorkingTree/xen-unstable.hg/stubdom/cross-root-x86_64/x86_64-xen-elf/lib -m elf_x86_64 -\( /home/hahn/Src/Xen/WorkingTree/xen-unstable.hg/stubdom/vtpm/vtpm.a app.lds -\) -ltpm -ltpm_crypto -lgmp -lpolarssl --undefined main -o /home/hahn/Src/Xen/WorkingTree/xen-unstable.hg/stubdom/mini-os-x86_64-vtpm/mini-os_app.o
ld: warning: app.lds contains output sections; did you forget -T?
ld: cannot find -lgmp
make[2]: *** [/home/hahn/Src/Xen/WorkingTree/xen-unstable.hg/stubdom/mini-os-x86_64-vtpm/mini-os_app.o] Error 1
make[2]: Leaving directory `/home/hahn/Src/Xen/WorkingTree/xen-unstable.hg/extras/mini-os'
make[1]: *** [vtpm-stubdom] Error 2
What I found is that libgmp gets built and stored in
.../stubdom/cross-root-x86_64/x86_64-xen-elf/lib64
while on linking only the path
.../stubdom/cross-root-x86_64/x86_64-xen-elf/lib
gets used where all other libs are located.
The solution for me was:
--- a/stubdom/Makefile Thu Feb 28 09:22:41 2013 +0100
+++ b/stubdom/Makefile Thu Mar 07 10:00:10 2013 +0100
@@ -47,7 +47,8 @@
TARGET_CPPFLAGS += -I$(CURDIR)/include
TARGET_CPPFLAGS += -I$(XEN_ROOT)/xen/include
-TARGET_LDFLAGS += -nostdlib -L$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/lib
+TARGET_LDFLAGS += -nostdlib -L$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/lib \
+ -L$(CROSS_PREFIX)/$(GNU_TARGET_ARCH)-xen-elf/lib64
TARGETS=$(STUBDOM_TARGETS)
Id had this behavior on different machines but all with opensuse-12.2.
Do I something wrong in configure/compiling?
Thanks.
Dietmar.
next reply other threads:[~2013-03-07 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 9:11 Dietmar Hahn [this message]
2013-03-11 8:50 ` Error on make dist in xen-unstable Dietmar Hahn
2013-03-12 11:44 ` Ian Campbell
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=4168930.OQMBFBY8PY@amur \
--to=dietmar.hahn@ts.fujitsu.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.