Missing library on Fedora 16

[Steven Oliver]

I just finished setting up falcon on a new Fedora 16 install. For
posterity's sake I wrote down the process I followed and shared it with
the world here:

http://steveno.wordpress.com/2012/01/02/compiling-falcon-pl-on-fedora-16/

Now that I've finished that, though, I'm getting this error on the
command line:

<code>
steveno@odrade:/usr/local/lib $ ls
falcon libfalcon_engine.so libfalcon_engine.so.1
libfalcon_engine.so.1.22.2
steveno@odrade:/usr/local/lib $ falcon -v
falcon: error while loading shared libraries:
libfalcon_engine.so.1: cannot open shared object file: No such file or
directory
</code>

As you can see the library is there. Any ideas why I'm still getting
that message?

[Giancarlo Niccolai]

On 03/01/2012 01:04, Steven Oliver wrote:
> I just finished setting up falcon on a new Fedora 16 install. For
> posterity's sake I wrote down the process I followed and shared it
> with the world here:
>
> http://steveno.wordpress.com/2012/01/02/compiling-falcon-pl-on-fedora-16/
>
> Now that I've finished that, though, I'm getting this error on the
> command line:
>
> <code>
> steveno@odrade:/usr/local/lib $ ls
> falcon libfalcon_engine.so libfalcon_engine.so.1
> libfalcon_engine.so.1.22.2
> steveno@odrade:/usr/local/lib $ falcon -v
> falcon: error while loading shared libraries:
> libfalcon_engine.so.1: cannot open shared object file: No such file or
> directory
> </code>

maybe usr/local/lib is not in ldcache.conf?

Gian.

[MIURA Masahiro]

On my PC running Fedora 16 x86_64, I have successfully installed Falcon from the Git repository.
I have added /usr/local/lib to /etc/ld.so.conf , which now looks like

include ld.so.conf.d/*.conf
/usr/local/lib

After modifying the file, do "ldconfig" as root.
Do "ldd /path/to/your/falcon" to make sure Falcon can actually find libfalcon_engine.so.

As for steveno's installing instruction, after "cmake .." I prefer to do "ccmake .." and set CMAKE_BUILD_TYPE to Release, though I'm not sure if this is really needed :-)

[Giancarlo Niccolai]

I think cmake wants the "Release" option to be explicitly given (it's a CMAKE standard) so yes.

Another option might be that of using /usr instead of /usr/local for a prefix, but /usr/local is well known as the default installation directory for packages compiled from source.

For security reasons, many distros don't include /usr/local/lib in the default search path anymore. The effect is that packages compiled from source with default options won't usually run. AFAIK this is a desired effect, to force ppl to either chose a target directory willfully or accept and manage the security risks involved in adding /usr/local to ld.conf

Gian.

[Giancarlo Niccolai]

Il giorno 04/gen/2012, alle ore 03:54, MIURA Masahiro ha scritto:

I think cmake wants the "Release" option to be explicitly given (it's a CMAKE standard) so yes.