• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 2399 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GStreamer: Alsasink, Undefined symbols

Glenn Wainwright
Expert 1605 points
Other Parts Discussed in Thread: DM3730

I'm unable to load the alsasink plugin for GStreamer.  Running "gst-inspect-1.0 /usr/lib/gstreamer-1.0/libgstalsa.so" gives me this error:

(gst-inspect-1.0:1589): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gs
treamer-1.0/libgstalsa.so': /usr/lib/gstreamer-1.0/libgstalsa.so: undefined symb
ol: snd_pcm_readi

libasound is installed in /usr/lib.
The following environment variables are set up:
export GST_PLUGIN_PATH=/usr/lib/gstreamer-1.0/
export GST_PLUGIN_SCANNER=/usr/libexec/gstreamer-1.0/gst-plugin-scanner
export LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH
So, libgstalsa should have easy access to libasound.

Any idea what could be going wrong here?

Thanks,
Glenn Wainwright

  • 0
    Expert 1605 points

    Reverted to GStreamer 0.10.25 built using gst-ti-plugin-full-1.02.00, and it still gives undefined symbol - for "snd_mixer_first_elem" this time.  Any idea what's going on?

  • 0 in reply to Glenn Wainwright
    Expert 1605 points

    Other plugins from this 0.10.25 build, such as TIViddec2 and TIDmaiVideoSink, are working just fine.  It seems to be just alsasink so far that's having problems.  Again, this is not on the build - it's building fine, but when it gets onto the target device (which again appears to have libasound.* installed properly), it gives an undefined symbol.

  • 0 in reply to Glenn Wainwright
    TI__Intellectual 1830 points

    Hello,

    Are you running a TI SDK release on TI Hardware? Where did the root file system you are using come from? Was libasound built and installed by you?


    Regards,

    Dave

  • 0 in reply to Dave Gerlach
    Expert 1605 points

    Thanks for the reply.  Yes, I'm running DVSDK 4.00 on a DM3730.  Root fs is coming from the DVSDK's minimal filesystem, and I copied over the asound libraries from $/dvsdk_4_00_00_17/linux-devkit/arm-non-linux-gnueabi/usr/lib to /usr/lib on the target device.

    Is there perhaps a better version of the alsa tools that might be more compatible with gst-plugins-base-0.10.25?

  • 0 in reply to Glenn Wainwright
    TI__Intellectual 1830 points

    The version of gstreamer you are referring to should build and run fine against alsa-lib-1.0.24.1, it may be advisable to try and rebuild this from source. Are you able to run amixer on your platform without receiving errors?

  • 0 in reply to Dave Gerlach
    Expert 1605 points

    I built alsa-lib-1.0.24.1 and installed it on my target at /usr/lib.  I verified that the new libasound* libraries are at that location and have today's date.  Unfortunately, the gstreamer plugin seems to have the same problem as before.

    root@omap3evm:~# export GST_PLUGIN_PATH=/usr/opt/gstreamer/lib                  
    root@omap3evm:~# export LD_LIBRARY_PATH=/usr/lib:$LD_LIBRARY_PATH               
    root@omap3evm:~# gst-inspect alsasink                                           
                                                                                    
    (gst-inspect-0.10:1526): GStreamer-WARNING **: Failed to load plugin '/usr/opt/g
    streamer/lib/gstreamer-0.10/libgstalsa.so': /usr/opt/gstreamer/lib/gstreamer-0.1
    0/libgstalsa.so: undefined symbol: snd_mixer_first_elem  

    I'm going to try rebuilding the plugin pointing at the new 1.0.24.1 library includes, but I don't think that will make much difference.  Anything else I can try?

  • 0 in reply to Glenn Wainwright
    Expert 1605 points

    To answer your earlier question that I missed, amixer runs just fine.

  • 0 in reply to Glenn Wainwright
    Expert 1605 points

    A gstreamer rebuild after all of the above seems to have addressed the issue.