From: Andrew Cooper <andrew.cooper3@citrix.com>
To: David Denny <david_denny@verizon.net>
Cc: xen-devel@lists.xen.org
Subject: Re: [BUG] Bugs during building 4.3.1
Date: Sun, 3 Nov 2013 18:24:31 +0000 [thread overview]
Message-ID: <527694DF.3050107@citrix.com> (raw)
In-Reply-To: <00d401ced8be$d7289530$8579bf90$@net>
[-- Attachment #1.1: Type: text/plain, Size: 1757 bytes --]
On 03/11/13 18:02, David Denny wrote:
>
> Hi!
>
>
>
> Thanks for the great software! I use it constantly. Thought I'd let
> you know of a few issues I ran into. #3 might be pretty easy to fix.
>
>
>
> 1. No spaces allowed in the base directory path! I guess some
> quotes are missing on variables in the makefiles. At least this is a
> "known limitation."
>
Spaces in paths are generally frowned upon. Having said that, it is
probably something worth fixing if you can identify what is at fault.
>
>
> 2. Configuration process does not check for openssl and x11,
> which I believe are both required.
>
How are you building qemu upstream? It is certainly not expected to be
used with x11 enabled. If you are using the defaults as present in Xen
4.3.1 then we really do have some fixing to do.
>
>
> 3. APPEND_LIB doesn't carry through to all the makefiles.
>
This looks plausible. If I remember correctly, the idea was always to
fault in APPEND_LIB to new bits of the build system as and when needed.
I suppose you have come across this because of x11 and openssl ?
To submit patches, you should follow the instructions at
http://wiki.xen.org/wiki/Submitting_Xen_Patches - particularity "Signing
off a patch"
~Andrew
>
>
> My openssl and x11 libraries are in non-standard locations (not in
> /usr/X11 or /usr/openssl).
>
> I've provided three very trivial patches that I hope will be more
> illustrative than my typing, but they are probably not production grade.
>
> I applied them prior to configuration and got a clean build.
>
>
>
> Best regards,
>
>
>
> David
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 7090 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-03 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 18:02 [BUG] Bugs during building 4.3.1 David Denny
2013-11-03 18:24 ` Andrew Cooper [this message]
2013-11-03 20:16 ` David Denny
2013-11-04 11:15 ` 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=527694DF.3050107@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=david_denny@verizon.net \
--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.