Go to previous topic
Go to next topic
Last Post 11 Feb 2016 08:50 AM by  Adam Ford
ldconfig -p yields no found libraries
 1 Replies
Author Messages
Jay Thomas
New Member
New Member
Posts:3


--
08 Feb 2016 04:40 PM

     

    Hi all,

    I noticed after building and deploying an image onto the Torpedo AM37x SOM via LTIB that when I went to the command line and typed:

    ldconfig -p

    The system indicated that it could not find anything.  It complained of not having an ld.so.conf.d directory

    It seems that this is a requirement for Linux in general so that it can reliably find it's shared objects that are required for the embedded application.

    To solve the issue, I created the /etc/ld.so.conf.d directory and then created a file /etc/ld.so.conf with the following contents:

    include /etc/ls.so.conf.d/*

    after I did this, ldconfig -p returned a whole slew of shared object libraries that would be required for any application running in the Linux environment

    Is there a standard way to make LTIB create this directory structure? Why is it not included as standard?

    Thanks

    Jay

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    11 Feb 2016 08:50 AM
    I did a little digging, and the ldconfig package was considered optional and not required for Linux. I'm going to work internally with some people to see if we can develop patch to resolve the issue, but in the meantime, I would suggest continuing with what you are doing.

    adam


    ---