On Sat, 20.08.11 20:25, Mike Kazantsev ([email protected]) wrote: > > Reexec reacts on these units right before "Deserializing state..." msg, > > with the same messages. > > I'll check whether they go away on reexec to 32 and reappear in 33, and > > if that's the case, will have results shortly. > > Got the results (attached, list of commits is at the end, should look > better in less, since I ran it through a script(1)), but it's mostly > failed builds. > > Error behind most (if not all) build failures seem to be: > > /bin/mkdir -p src/ && \^M > gperf < src/load-fragment-gperf.gperf > src/load-fragment-gperf.c > > Empty input keyword is not allowed. > To recognize an empty input keyword, your code should check for > len == 0 before calling the gperf generated lookup function. > > Any idea what might cause that? > Looks like some autotools failure to me since tarballs work fine. > I'll try to figure it out and run bisect again.
Well, I forgot to add a file to the git repo and didn't notice this right-away. This issue is unrelated to yours. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
