Created attachment 371334 [details] Build log Long story short, in systemd-209 the libsystemd-* libraries were removed and replaced with single libsystemd. We install compatibility libsystemd-*.pc pkg-config files, so apps using pkg-config are not affected (yet :)). Since this package tries to link libsystemd-daemon directly, it fails terribly with >=systemd-209. The possibilities are: 1. use pkg-config to query libsystemd-daemon -- compatible with all versions but at some point we will be removing compat pkg-config files, 2. use pkg-config to query libsystemd, fallback to querying libsystemd-daemon -- future- and backwards-compatible, 3. just use libsystemd, and dep on >=systemd-210 in the ebuild (we didn't add -209). Preferably, always use pkg-config :). If you need any help, please let us know.
Created attachment 371336 [details] config.log
pulseaudio uses pkg-config to find systemd libraries and both -4.99.4-r1 and -5.0 compiles fine on my system with systemd-211. You probably compiled pulseaudio[abi_x86_32] against systemd[-abi_x86_32] and this is actually a bug in pulseaudio ebuild. Two possible solutions: 1. add MULTILIB_USEDEP: systemd? ( >=sys-apps/systemd-39 ) systemd? ( >=sys-apps/systemd-39[${MULTILIB_USEDEP}] ) 2. disable journald support for non-native ABI (probably the preferred solution): --disable-systemd-journal
Created attachment 373840 [details, diff] pulseaudio-5.0.ebuild.patch Note that I can't test it myself.
Hmm, weird that I got this issue but well, whatever... + 29 Mar 2014; Michał Górny <mgorny@gentoo.org> pulseaudio-5.0.ebuild: + Enforce MULTILIB_USEDEP on systemd for libsystemd (past libsystemd-journal), + bug #502528. it is used in the common lib for logging, so I guess it makes sense for lib32 variant.
(In reply to Michał Górny from comment #4) > Hmm, weird that I got this issue but well, whatever... Maybe you forgot to reemerge systemd after the following fix: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-apps/systemd/systemd-210.ebuild?hideattic=0&r1=1.1&r2=1.2
Yes, it could be that I actually reported the bugs before fixing that. Thanks.
