Summary: | dev-libs/libaio not in samba-3.0.x dependency tree | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Richard Foltyn <richard.foltyn> |
Component: | [OLD] Server | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | vostorga |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Richard Foltyn
2009-06-27 09:00:56 UTC
Can't reproduce this issue using amd64, can you provide full ldd output and build logs? (In reply to comment #1) > Can't reproduce this issue using amd64, can you provide full ldd output and > build logs? > I've done some further research. From my rudimentary understanding of the matter, there are two aio libraries on linux: libaio with is specific to the Linux kernel, and librt which is a POSIX-compliant implementation provided by glibc. Now the problem arises because the samba configure script is not very transparent to the user. When --with-aio-support is requested, then 1. if configure finds libaio, it uses that one and links smbd against it; 2. if configure does not find libaio, it falls back to librt; So you can readily compile samba with USE=async without libaio. However, if you happen to have it installed and compile time, smbd is linked against it. Unfortunately, since libaio does not show up as a dependency in the ebuild, nothing prevents libaio from being unmerged by emerge --depclean, and then smbd won't start anymore (as in my case). I guess there is nothing to be done here, since the real "problem" lies in samba's configure script, which ideally would let the user decide which library to use (then this could be reflected by two distinct USE flags, e.g. async-libaio and async-librt, and the appropriate dependency). |