[arch-dev-public] [arch-general] [signoff] syslog-ng-3.0.1-1

[Allan McRae]

Gerardo Exequiel Pozzi wrote:
> Pierre Schmitz wrote:
>   
>> Does anybody know what this message in dmesg is about? Was syslog-ng compiled 
>> for i686?
>>
>> warning: `syslog-ng' uses 32-bit capabilities (legacy support in use)
>>
>>   
>>     
> Very out-of-date libcap, not only syslog-ng, also proftpd, vsftpd,
> pulseaudio, ntpd, virtualbox, etc, etc...
>
> http://www.archlinux.org/packages/extra/i686/libcap/ (for linux 2.4)
>
> Need to have libcap2 package for kernel 2.6 in Arch Linux
> http://www.kernel.org/pub/linux/libs/security/linux-privs/
>   

I was confused about this as libcap is in [extra] so how can it make
problems with a package in [core]?

So going from this comment in the bug report about libcap
(http://bugs.archlinux.org/task/11917#comment41046) I get...

> readelf -s /usr/sbin/syslog-ng | grep cap
    33: 00000000     0 FUNC    GLOBAL DEFAULT  UND capset at GLIBC_2.1 (4)
   177: 00000000     0 FUNC    GLOBAL DEFAULT  UND capget at GLIBC_2.1 (4)
   473: 08228bd8     4 OBJECT  GLOBAL DEFAULT   26 OPENSSL_ia32cap_P

Looks like libcap is a soft dep there.  How?

Then rebuild in clean chroot:
> readelf -s syslog-ng | grep cap
   467: 08221b18     4 OBJECT  GLOBAL DEFAULT   26 OPENSSL_ia32cap_P

And then the dmesg warning goes away...  So, the lesson to learn is to 
_always build in a clean chroot_!

Allan