| Summary: | Please add a configure check that 'struct file_handle' and 'name_to_handle_at' are properly defined for the target glibc | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Sean McGovern <gseanmcg> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED NOTOURBUG | QA Contact: | systemd-bugs |
| Severity: | enhancement | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | PowerPC | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Sean McGovern
2012-09-27 07:29:14 UTC
Sorry, apparently I can't read: hanyuu systemd-192 # egrep -n "(file_handle|name_to_handle_at)" configure.ac 175:AC_CHECK_FUNCS([fanotify_init fanotify_mark name_to_handle_at]) and from configure.log: configure:15421: checking for name_to_handle_at configure:15421: powerpc-unknown-linux-gnu-gcc -std=gnu99 -o conftest -pipe -O2 -mcpu=7450 -fno-strict-aliasing -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,--sort-common conftest.c -ldl -lrt >&5 configure:15421: $? = 0 configure:15421: result: yes Here's the failure to build: hanyuu systemd-192 # make CC src/shared/path-util.lo src/shared/path-util.c: In function 'path_is_mount_point': src/shared/path-util.c:348:10: error: dereferencing pointer to incomplete type src/shared/path-util.c:350:9: warning: implicit declaration of function 'name_to_handle_at' [-Wimplicit-function-declaration] src/shared/path-util.c:368:10: error: dereferencing pointer to incomplete type make: *** [src/shared/path-util.lo] Error 1 Hmm, so in ppc: is the function exported? is the function in the header files? If it's in one but not the other, then please fix the libc for that port, we will not work around this in systemd. Will close this bug as it looks this way. Feel free to reopen if the AC check we do in systemd really is broken. This issue is currently being worked upstream in the libc-alpha mailing list: http://sourceware.org/ml/libc-alpha/2012-10/msg00401.html |
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.