From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Roger Pau Monne <roger.pau@entel.upc.edu>, AL13N <alien@rmail.be>,
Vincent Bernardoff <vb@luminar.eu.org>,
"Vincent Bernardoff (Intern)" <vincent.bernardoff@citrix.com>
Subject: Re: [PATCH] tools/ocaml: Fix library generation [and 1 more messages]
Date: Wed, 10 Apr 2013 13:01:06 +0100 [thread overview]
Message-ID: <51655482.2000507@citrix.com> (raw)
In-Reply-To: <1365593609.27868.5.camel@zakaz.uk.xensource.com>
On 10/04/13 12:33, Ian Campbell wrote:
> On Tue, 2013-04-09 at 15:50 +0100, Andrew Cooper wrote:
>> I was not aware of Rogers commit, but at the very least it break
>> static linking.
> How? The change is only about dynamic linking against libraries in the
> current tree.
>
> Ian.
>
This is the issue I reported 6 months ago in
http://lists.xen.org/archives/html/xen-devel/2012-10/msg01166.html
Although back then I was simply trying to make Xen 4.2 to compile in the
XenServer build system, and did not pay too much attention to why the
build had regressed from 4.1
~Andrew
next prev parent reply other threads:[~2013-04-10 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 17:26 [PATCH] tools/ocaml: Fix library generation Vincent Bernardoff
2013-04-08 17:31 ` Andrew Cooper
2013-04-09 14:30 ` [PATCH] tools/ocaml: Fix library generation [and 1 more messages] Ian Jackson
2013-04-09 14:50 ` Andrew Cooper
2013-04-09 15:10 ` Ian Jackson
2013-04-10 11:32 ` Ian Campbell
2013-04-10 11:33 ` Ian Campbell
2013-04-10 12:01 ` Andrew Cooper [this message]
2013-04-10 12:07 ` 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=51655482.2000507@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=alien@rmail.be \
--cc=roger.pau@entel.upc.edu \
--cc=vb@luminar.eu.org \
--cc=vincent.bernardoff@citrix.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.