Summary: | systemd master: out-of-tree build broken | ||
---|---|---|---|
Product: | systemd | Reporter: | Maksim Melnikau <maxposedon> |
Component: | general | Assignee: | Lennart Poettering <lennart> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
URL: | https://bugs.gentoo.org/show_bug.cgi?id=422927 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
The build log
The (correct) build log |
Description
Maksim Melnikau
2012-05-04 00:12:23 UTC
Your command sequence works totally fine here. "make distcheck", which checks out-of-tree builds, also passes without any problems too. If you want to investigate your setup, you might check if the old udev repo works for you with building gudev, and then compare what udev does here to what we do in systemd. I have no good idea. I'm closing this for now, if you find the issue, and it makes sense to apply it to the systemd repo, please let us know in this bug. Thanks! Works for me now too. Looks like its reproduces at least in Gentoo. Created attachment 63346 [details]
The build log
Created attachment 63347 [details]
The (correct) build log
Sorry, the wrong one.
Is this still broken? Yes, it i(In reply to comment #6) > Is this still broken? Yes, it is. Might it be, because of released tar.xz, with pre-runned ./autogen.sh?.. ====== >>> Source configured. >>> Compiling source in /var/tmp/portage/sys-apps/systemd-187/work/systemd-187 ... >>> Working in BUILD_DIR: "/var/tmp/portage/sys-apps/systemd-187/work/systemd-187_build" make -j2 GEN src/core/syscall-list.txt GEN src/gudev/gudevmarshal.h /bin/sh: src/core/syscall-list.txt: No such file or directory /bin/sh: src/gudev/gudevmarshal.h: No such file or directory make: *** [src/gudev/gudevmarshal.h] Error 1 make: *** Waiting for unfinished jobs.... make: *** [src/core/syscall-list.txt] Error 1 Fixed in bd923ff29e0. Explanation in commit message. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.