NSLU2 plugin link/build problem

[Mitch]

I am having a problem with mt-daapd not being able to load plugins when it starts up.

I have built the 1236 codebase on my unslung slug, and mt-daapd works just fine – except that the plugins don’t load.

Looking at the log output I get the error :
“Error loading plugin /public/src/mt-daapd-svn-1236/src/plugins/rsp.la: /public/src/mt-daapd-svn-1236/src/plugins/rsp.la: ELF file version does not match current
one”

I’m thinking the plugins and mt-daapd are linked differently but I can’t see what the problem could be. The plugins seemed to compile ok (the .la files are there). Anyone got any ideas what this could be?

I think I have all my slug’s packages up-to-date (ipkg update) but maybe I’m not doing something right?

Please help!!! Thanks.

[rpedde]

@Mitch wrote:

I am having a problem with mt-daapd not being able to load plugins when it starts up.

I have built the 1236 codebase on my unslung slug, and mt-daapd works just fine – except that the plugins don’t load.

Looking at the log output I get the error :
“Error loading plugin /public/src/mt-daapd-svn-1236/src/plugins/rsp.la: /public/src/mt-daapd-svn-1236/src/plugins/rsp.la: ELF file version does not match current
one”

I’m thinking the plugins and mt-daapd are linked differently but I can’t see what the problem could be. The plugins seemed to compile ok (the .la files are there). Anyone got any ideas what this could be?

I think I have all my slug’s packages up-to-date (ipkg update) but maybe I’m not doing something right?

Please help!!! Thanks.

Hm… You should be looking for the .so files, not the .la files. If you are trying to run it directly from the build tree, they should be in src/plugins/.libs, a hidden directory. Don’t ask me why, that’s just what libtool does. 🙂

— Ron

[Mitch]

Thanks.
I’ll try that tonight and let you know!

[Mitch]

Worked perfectly – many thanks.
I’m now wondering why I can only pipe wav files through from the ssc-script.sh plugin?
Is there a way to pipe other supported formats (i.e. mp3?) – does the server somehow tell the client to expect wav file data?

Many thanks again,
Mitch

[rpedde]

@Mitch wrote:

Worked perfectly – many thanks.
I’m now wondering why I can only pipe wav files through from the ssc-script.sh plugin?
Is there a way to pipe other supported formats (i.e. mp3?) – does the server somehow tell the client to expect wav file data?

Many thanks again,
Mitch

It does. There is a patch floating around here to do mp3 transcoding, but it’s an all-or-nothing thing. I hoped to integrate it in so I could choose whether to transcode to mp3 or wav depending on client address or client type, etc, but there’s no way I can get that before a 1.0, so I pushed that to a 1.1 feature.

— Ron

[Author]

Posts