error while loading shared libraries: libsndfile.so.1

I used libsndfile and created a binary - then I moved it into Ubuntu and the binaries worked.

Now I moved the same binary into a Linux server hosted by 1and1.com - it is giving me the following error (for that executable binary):
"error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory"

What is happening? What is the fix?

Thanks

On Fri, 13 Mar 2015 22:35:37 -0700, speech2020 wrote:

> I used libsndfile and created a binary - then I moved it into Ubuntu and
> the binaries worked.
> 
> Now I moved the same binary into a Linux server hosted by 1and1.com - it
> is giving me the following error (for that executable binary):
> "error while loading shared libraries: libsndfile.so.1: cannot open
> shared object file: No such file or directory"
> 
> What is happening? What is the fix?
> 
> Thanks

It sounds like whatever libsndfile.so.1 is, it's not on that server.

If it's for playing sound, that's to be expected -- servers living in big 
noisy rooms don't usually need to present the whole multimedia experience 
to their fellow servers.

-- 
www.wescottdesign.com

speech2020@gmail.com writes:

> I used libsndfile and created a binary - then I moved it into Ubuntu and the binaries worked.
>
> Now I moved the same binary into a Linux server hosted by 1and1.com - it is giving me the following error (for that executable binary):
> "error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory"
>
> What is happening? What is the fix?

You don't have libsndfile installed on the server. Install it.
-- 
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com

On Saturday, March 14, 2015 at 8:30:46 AM UTC-7, Randy Yates wrote:
>  writes:
> 
> > I used libsndfile and created a binary - then I moved it into Ubuntu and the binaries worked.
> >
> > Now I moved the same binary into a Linux server hosted by 1and1.com - it is giving me the following error (for that executable binary):
> > "error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory"
> >
> > What is happening? What is the fix?
> 
> You don't have libsndfile installed on the server. Install it.
> -- 
> Randy Yates
> Digital Signal Labs
> http://www.digitalsignallabs.com

Randy,
1) I tested in another Ubuntu without libsndfile installed and the binary ran fine
2) Does the binary still dependent on  libsndfile?

On Sat, 14 Mar 2015 09:46:33 -0700, speech2020 wrote:

> On Saturday, March 14, 2015 at 8:30:46 AM UTC-7, Randy Yates wrote:
>>  writes:
>> 
>> > I used libsndfile and created a binary - then I moved it into Ubuntu
>> > and the binaries worked.
>> >
>> > Now I moved the same binary into a Linux server hosted by 1and1.com -
>> > it is giving me the following error (for that executable binary):
>> > "error while loading shared libraries: libsndfile.so.1: cannot open
>> > shared object file: No such file or directory"
>> >
>> > What is happening? What is the fix?
>> 
>> You don't have libsndfile installed on the server. Install it.
>> --
>> Randy Yates Digital Signal Labs http://www.digitalsignallabs.com
> 
> Randy,
> 1) I tested in another Ubuntu without libsndfile installed and the
> binary ran fine 2) Does the binary still dependent on  libsndfile?

If it's erroring out on the lack of libsndfile.so.1, then it needs that 
file to be present.  So the binary file is dependent on having that 
shared library file, which certainly LOOKS like it'd come with libsndfile!

-- 
www.wescottdesign.com

speech2020@gmail.com writes:

> On Saturday, March 14, 2015 at 8:30:46 AM UTC-7, Randy Yates wrote:
>>  writes:
>> 
>> > I used libsndfile and created a binary - then I moved it into Ubuntu and the binaries worked.
>> >
>> > Now I moved the same binary into a Linux server hosted by 1and1.com - it is giving me the following error (for that executable binary):
>> > "error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory"
>> >
>> > What is happening? What is the fix?
>> 
>> You don't have libsndfile installed on the server. Install it.
>> -- 
>> Randy Yates
>> Digital Signal Labs
>> http://www.digitalsignallabs.com
>
> Randy,
> 1) I tested in another Ubuntu without libsndfile installed and the binary ran fine
> 2) Does the binary still dependent on  libsndfile?

Your program either does or does not depend on libsndfile. It can't be
both. My guess is that the other Ubuntu you tested in DID have
libsndfile installed, thus your program ran fine there, and that in both
cases your program depends on libsndfile.

In any case, try running "ldd" on your program. For example, if your
program is named "myprog", and your current working directory is the
directory containing the program, run "ldd myprog" (without the quotes).
If your program is in the path, you can more simply issue "ldd `which
myprog`".
-- 
Randy Yates
Digital Signal Labs
http://www.digitalsignallabs.com

Tim Wescott wrote:
> On Fri, 13 Mar 2015 22:35:37 -0700, speech2020 wrote:
>
>> I used libsndfile and created a binary - then I moved it into Ubuntu and
>> the binaries worked.
>>
>> Now I moved the same binary into a Linux server hosted by 1and1.com - it
>> is giving me the following error (for that executable binary):
>> "error while loading shared libraries: libsndfile.so.1: cannot open
>> shared object file: No such file or directory"
>>
>> What is happening? What is the fix?
>>
>> Thanks
>
> It sounds like whatever libsndfile.so.1 is, it's not on that server.
>
> If it's for playing sound, that's to be expected -- servers living in big
> noisy rooms don't usually need to present the whole multimedia experience
> to their fellow servers.
>

libsndfile is for "parsing" sound files more than playing them.

-- 
Les Cargill

On Sat, 14 Mar 2015 15:45:19 -0400, Randy Yates
<yates@digitalsignallabs.com> wrote:

<snip>
>
>In any case, try running "ldd" on your program. For example, if your
>program is named "myprog", and your current working directory is the
>directory containing the program, run "ldd myprog" (without the quotes).
>If your program is in the path, you can more simply issue "ldd `which
>myprog`".

I second this suggestion.  You could also link statically against
libsndfile.  Might save a whole bunch of time figuring out which files
you need to copy, and how to setup LD_LIBRARY_PATH properly...

Mark

Mac Decman wrote:
> On Sat, 14 Mar 2015 15:45:19 -0400, Randy Yates
> <yates@digitalsignallabs.com> wrote:
>
> <snip>
>>
>> In any case, try running "ldd" on your program. For example, if your
>> program is named "myprog", and your current working directory is the
>> directory containing the program, run "ldd myprog" (without the quotes).
>> If your program is in the path, you can more simply issue "ldd `which
>> myprog`".
>
> I second this suggestion.  You could also link statically against
> libsndfile.

I am not sure that this is true. I expect it's a .so sort of
thing only.

> Might save a whole bunch of time figuring out which files
> you need to copy, and how to setup LD_LIBRARY_PATH properly...
>
> Mark
>

-- 
Les Cargill

On Saturday, March 14, 2015 at 6:35:43 PM UTC+13, speec...@gmail.com wrote:
> I used libsndfile and created a binary - then I moved it into Ubuntu and the binaries worked.
> 
> Now I moved the same binary into a Linux server hosted by 1and1.com - it is giving me the following error (for that executable binary):
> "error while loading shared libraries: libsndfile.so.1: cannot open shared object file: No such file or directory"
> 
> What is happening? What is the fix?
> 
> Thanks

Little and big Endian