From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] [RELEASE] Userspace RCU 0.6.0
Date: Mon, 13 Jun 2011 10:02:23 -0400 [thread overview]
Message-ID: <20110613140223.GB29349@Krystal> (raw)
In-Reply-To: <20110613042340.GH2212@linux.vnet.ibm.com>
* Paul E. McKenney (paulmck at linux.vnet.ibm.com) wrote:
> On Mon, Jun 13, 2011 at 10:06:09AM +0800, Cui, Dexuan wrote:
[...]
> > Hi Mathieu,
> > The release can't build in my side:
> >
> > $ tar -jxf userspace-rcu-0.6.0.tar.bz2 && cd userspace-rcu-0.6.0 && ./configure && make
> >
> > make all-recursive
> > make[1]: Entering directory `/home/dcui/userspace-rcu-0.6.0'
> > Making all in .
> > make[2]: Entering directory `/home/dcui/userspace-rcu-0.6.0'
> > CC wfqueue.lo
> > CC wfstack.lo
> > CC rculfqueue.lo
> > CC rculfstack.lo
> > CCLD liburcu-cds.la
> > CC urcu.lo
> > urcu.c:438:32: error: urcu-call-rcu-impl.h: No such file or directory
> > urcu.c:439:29: error: urcu-defer-impl.h: No such file or directory
> > make[2]: *** [urcu.lo] Error 1
> > make[2]: Leaving directory `/home/dcui/userspace-rcu-0.6.0'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/dcui/userspace-rcu-0.6.0'
> > make: *** [all] Error 2
> >
> > Can you please have a look?
>
> I get the same thing from the tarball. But the git tree works just fine,
> so my guess is that the tarball creation left out a couple of files.
Indeed, I missed those two headers in the Makefile.am EXTRA_DIST. I just
released 0.6.1, which fixes this issue. I've made sure the tarball
builds fine.
Thanks for reporting this so quickly!
Mathieu
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2011-06-13 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 1:14 Mathieu Desnoyers
2011-06-13 2:06 ` Cui, Dexuan
2011-06-13 4:23 ` Paul E. McKenney
2011-06-13 14:02 ` Mathieu Desnoyers [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=20110613140223.GB29349@Krystal \
--to=mathieu.desnoyers@efficios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox