<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: sysdeputil.c:162: error: expected declaration specifiers or &#8216;&#8230;&#8217; before &#8216;capset&#8217;</title>
	<link>http://www.andreaswacker.com/blog/2009/01/23/sysdeputilc162-error-expected-declaration-specifiers-or-before-capset/</link>
	<description>weblog</description>
	<pubDate>Mon, 21 May 2012 19:55:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.2</generator>

	<item>
		<title>by: Andreas Wacker</title>
		<link>http://www.andreaswacker.com/blog/2009/01/23/sysdeputilc162-error-expected-declaration-specifiers-or-before-capset/#comment-2335</link>
		<pubDate>Sat, 02 Jan 2010 18:14:56 +0000</pubDate>
		<guid>http://www.andreaswacker.com/blog/2009/01/23/sysdeputilc162-error-expected-declaration-specifiers-or-before-capset/#comment-2335</guid>
					<description>installing vsftpd again from source on 64 bit machines I encountered this hick-up again in two different flavors: 

When libcap.i386 was installed (f* knows why) the error was:

/lib/libcap.so.1: could not read symbols: File in wrong format

This time I cured that via

yum remove libcap-1.10-26.i386

then I got the same error then on the machines with only the X86_64 libcap installed:

/usr/bin/ld: cannot find -lcap

A somewhat hackish fix was to just link the 64bit library in where vsftpd is expecting it:

ln -s /lib64/libcap.so.1 /lib/libcap.so.1</description>
		<content:encoded><![CDATA[	<p>installing vsftpd again from source on 64 bit machines I encountered this hick-up again in two different flavors: </p>
	<p>When libcap.i386 was installed (f* knows why) the error was:</p>
	<p>/lib/libcap.so.1: could not read symbols: File in wrong format</p>
	<p>This time I cured that via</p>
	<p>yum remove libcap-1.10-26.i386</p>
	<p>then I got the same error then on the machines with only the X86_64 libcap installed:</p>
	<p>/usr/bin/ld: cannot find -lcap</p>
	<p>A somewhat hackish fix was to just link the 64bit library in where vsftpd is expecting it:</p>
	<p>ln -s /lib64/libcap.so.1 /lib/libcap.so.1
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bjornar Hansen</title>
		<link>http://www.andreaswacker.com/blog/2009/01/23/sysdeputilc162-error-expected-declaration-specifiers-or-before-capset/#comment-2328</link>
		<pubDate>Fri, 04 Sep 2009 23:49:16 +0000</pubDate>
		<guid>http://www.andreaswacker.com/blog/2009/01/23/sysdeputilc162-error-expected-declaration-specifiers-or-before-capset/#comment-2328</guid>
					<description>Thanks, this helped me.

I tried using the latest version of vsftpd, but there seems to be a bug in it that makes browsing directories very slow when using ssl.

Thanks to you I have successfully compiled vsftpd 2.0.5, and it seems to be working as it should.</description>
		<content:encoded><![CDATA[	<p>Thanks, this helped me.</p>
	<p>I tried using the latest version of vsftpd, but there seems to be a bug in it that makes browsing directories very slow when using ssl.</p>
	<p>Thanks to you I have successfully compiled vsftpd 2.0.5, and it seems to be working as it should.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

