Issue 13 in socket-sentry: Installation problem on Fedora 12, 64-bit

[socket...@googlecode.com]

Status: New
Owner: rhasselbaum
Labels: Type-Defect Priority-Medium

New issue 13 by rhasselbaum: Installation problem on Fedora 12, 64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

User reports installation failure on Fedora 12 64-bit using install script.
At first, socksent-client fails to find libsocketsent-client-common.so.* in
/usr/lib. (Should probably be in /usr/lib64 like openSUSE. User says that
libpcap is installed in "both" directories.) After moving it to /usr/lib64,
applet fails to start with: "This object could not be created for following
reasons; could not find request component:socketsentry".

[socket...@googlecode.com]

Updates:
Labels: -Priority-Medium Priority-High

Comment #1 on issue 13 by rhasselbaum: Installation problem on Fedora 12,
64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

(No comment was entered for this change.)

[socket...@googlecode.com]

Comment #2 on issue 13 by matsatzpolatsss: Installation problem on Fedora
12, 64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

Is in both directories because I should install libpcap/devel.i686 to be
able to compile and install correctly. I already had libpcap/devel.x64
installed but i get a libpcap error related at compilation process
anayway, so I installed i686 version, just then I could compile and
install.

[socket...@googlecode.com]

Comment #3 on issue 13 by rhasselbaum: Installation problem on Fedora 12,
64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

Reportedly affects Fedora 13 as well.

[socket...@googlecode.com]

Comment #4 on issue 13 by rhasselbaum: Installation problem on Fedora 12,
64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

Issue 14 has been merged into this issue.

[socket...@googlecode.com]

Comment #5 on issue 13 by GBia...@gmail.com: Installation problem on Fedora
12, 64-bit
http://code.google.com/p/socket-sentry/issues/detail?id=13

I have the same problem, but I am using Fedora 14, and it is NOT 64 bit.
Any possible workaround?