All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Tim Moore <timothy.moore@expidas.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [XCI] build.git does not work! fails patch apply
Date: Thu, 23 Jul 2009 10:01:58 +0100	[thread overview]
Message-ID: <4A682706.6000009@eu.citrix.com> (raw)
In-Reply-To: <14D9C9E2ED61ED41BC3B37ACDF4E880002CE11E9FB0D@heavy-vm03.heavy.org.uk>

Tim Moore wrote:
> Hi Vincent,
> 
> My guilt version is also 0.32.1 
> 
> The first problem is with the buildroot .. (Daniel, do you have this problem also?)
> 
> ########### snippet ##########
> mv -f .deps/dbus-bash-completion-helper.Tpo .deps/dbus-bash-completion-helper.Po
> grep: /usr/src/build.git/build_i686/staging_dir/usr/src/build.git/build_i686/libglib2-2.15.4/glib/libglib-2.0.la: No such file or directory
> /usr/src/build.git/toolchain_build_i686/bin/sed: can't read /usr/src/build.git/build_i686/staging_dir/usr/src/build.git/build_i686/libglib2-2.15.4/glib/libglib-2.0.la: No such file or directory
> libtool: link: `/usr/src/build.git/build_i686/staging_dir/usr/src/build.git/build_i686/libglib2-2.15.4/glib/libglib-2.0.la' is not a valid libtool archive
> make[5]: *** [libdbus-glib-1.la] Error 1
> make[5]: *** Waiting for unfinished jobs....
> mv -f .deps/dbus-binding-tool-glib.Tpo .deps/dbus-binding-tool-glib.Po
> mv -f .deps/dbus-gparser.Tpo .deps/dbus-gparser.Plo
> make[5]: Leaving directory `/usr/src/build.git/build_i686/dbus-glib-0.80/dbus'
> make[4]: *** [all-recursive] Error 1
> make[4]: Leaving directory `/usr/src/build.git/build_i686/dbus-glib-0.80/dbus'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/usr/src/build.git/build_i686/dbus-glib-0.80/dbus'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/usr/src/build.git/build_i686/dbus-glib-0.80'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/usr/src/build.git/build_i686/dbus-glib-0.80'
> make: *** [/usr/src/build.git/build_i686/dbus-glib-0.80/.compiled] Error 2
> ########### end snippet ##########
> 
> The problem seems to be a duplicated path reference, see:
> /usr/src/build.git/build_i686/staging_dir/usr/src/build.git/build_i686/libglib2-2.15.4/glib/libglib-2.0.la
> 
> Which can be worked around with:
> ln -s /usr/src /usr/src/build.git/build_i686/staging_dir/usr/src
> (and then removed immediately)

this is quite ugly. I'll have a look this morning, but i'm not sure why 
we're not seeing this one.

> 2) But then same problem with compiling xenclient-xen-tip detailed here: (same problem Daniel is getting)
> 
> http://lists.xensource.com/archives/html/xen-devel/2009-07/msg00673.html

see my reply to daniel and col sanders. hopefully once and for all fixed 
now.

> 3) also xenclient-ioemu fails with exactly the same problem detailed here:
> 
> http://lists.xensource.com/archives/html/xen-devel/2009-07/msg00674.html

same problems than with the xen repo. patchqueue applied to the main 
repository by mistake, and fixed manually only in one place.

also want to mentions that since yesterday night, we have an automated 
building daemon now on XCI, which hopefully means that we will catch any 
glitches before any of you experience it.

-- 
Vincent

  reply	other threads:[~2009-07-23  9:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 18:53 [XCI] build.git does not work! fails patch apply Tim Moore
     [not found] ` <d1ee18fa0907210929j23e9a68ck42e5ee738283b10a@mail.gmail.com>
2009-07-22 11:31   ` Tim Moore
2009-07-22 15:06     ` Vincent Hanquez
2009-07-22 17:48       ` Daniel Barden
2009-07-22 18:14       ` Tim Moore
2009-07-23  9:01         ` Vincent Hanquez [this message]
2009-07-23 11:19           ` Daniel Barden
2009-07-23 16:47           ` iicolsandersii
2009-07-24 14:53             ` Vincent Hanquez
2009-07-22 18:24       ` iicolsandersii
2009-07-23  8:56         ` Vincent Hanquez
2009-07-23 14:52         ` Daniel Barden
2009-07-23 22:36           ` Jean Guyader

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=4A682706.6000009@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=timothy.moore@expidas.net \
    --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.