From: grel <grelamen@lycos.com>
To: xen-devel@lists.xensource.com
Subject: Problems with xen 3.0.3 install on debian sarge
Date: Tue, 2 Jan 2007 15:17:26 -0800 (PST) [thread overview]
Message-ID: <8132718.post@talk.nabble.com> (raw)
In-Reply-To: <45914B6A.5040501@tegger.de>
Hi,
Having issues installing xen 3.0.3 source on debian sarge
I am still at the install level and when I run "make install" it ends with
the error:
collect2: ld returned 1 exit status
make[3]: *** [tapdisk] Error 1
make[3]: Leaving directory '/usr/src/xen-3.0.3_0-src/tools/blktap/drivers'
make[2]: *** [install] Error 2
make[2]: Leaving directory '/usr/src/xen-3.0.3_0-src/tools/blktap'
make[1]: *** [install] Error 2
make[1]: Leaving directory '/usr/src/xen-3.0.3_0-src/tools'
make: *** [install-tools] Error 2
Please help
--
View this message in context: http://www.nabble.com/Problems-with-XEN-3.0.4-and-Python-tf2882875.html#a8132718
Sent from the Xen - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2007-01-02 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 16:18 Problems with XEN 3.0.4 and Python Velten Spägele
2006-12-26 16:22 ` Christopher G. Stach II
2006-12-26 16:28 ` Keir Fraser
2006-12-30 15:32 ` Henning Sprang
2007-01-02 23:17 ` grel [this message]
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=8132718.post@talk.nabble.com \
--to=grelamen@lycos.com \
--cc=xen-devel@lists.xensource.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 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.