[systemd-devel] build failures in latest master from d848b9cbfa0ba72381363accce481600169df2eb

[Zbigniew Jędrzejewski-Szmek]

On Wed, Jan 30, 2013 at 04:30:39PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Jan 30, 2013 at 08:50:09AM -0500, Colin Walters wrote:
> > In gnome-ostree (tracking systemd git master), the first failure is the
> > recent commit:
> > 
> > commit d848b9cbfa0ba72381363accce481600169df2eb
> > Author: Zbigniew Jędrzejewski-Szmek <zbyszek at in.waw.pl>
> > Date:   Sun Jan 27 19:44:52 2013 -0500
> > 
> >     Move generic specifier functions to shared
> >     
> >     No functional change. This makes it possible to use them in install.c.
> > 
> > This one fails because libudev isn't linked to the shared library.
> How does it fail?
> 
> > Moving on
> > to current git master ( 06637f8bd1ceb6dc567d3a79a6b9745376797352 ), it
> > falls over like this, from:
> > 
> > http://ostree.gnome.org/work/tasks/gnomeos-3.8/systemd/x86_64/2013.160/log
> > 
> > /usr/bin/objcopy: 'systemd': No such file
> > make[2]: *** [org.freedesktop.systemd1.Manager.xml] Error 1
> > make[2]: *** Waiting for unfinished jobs....
> > /usr/bin/objcopy: 'systemd': No such file
> Hm, the Makefile.am rules looks like this:
> 
> org.freedesktop.systemd1.%.xml: systemd
> 	$(AM_V_GEN)$(LIBTOOL) --mode=execute $(OBJCOPY) ...
> 
> Unless make is doing something very strange, systemd binary should be there.
> Looking at the log linked above, it is created:
> 
> Looking at the log linked above, it is created:
> l. 1442: /bin/sh ./libtool  --tag=CC -o systemd ...
> l. 1484: /bin/sh ./libtool --mode=execute /usr/bin/objcopy -O binary -j introspect.Timer systemd ...
Ooops, wrong log file. So in your logfile line 1442 is missing :)
 
> It looks like al of the introspection jobs fail with the same error.
> Is 'systemd' binary there in the directory? Could you add an 'ls >> /tmp/log'
> to the introspection rule and retest? Was this in a clean build directory?
So a different set of questions then:
1. Was this in a pristine build directory? If not, does it reproduce
   in a new build dir?
2. What happens if you do 'make org.freedesktop.systemd1.Target.xml'?

Zbyszek

> > >From what I can tell, this looks like a race condition.  But studying
> > the patches, the cause isn't obvious to me right now, though I'm pretty
> > jetlagged.  Zbigniew, any ideas?
> Not really. I cannot reproduce this.
> 
> Zbyszek