OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: cwall on April 09, 2006, 07:40:50 am

Title: Ldd Tool
Post by: cwall on April 09, 2006, 07:40:50 am

Installed ldd from 3.5.4 on sl-5500 and tried it against libqdasher.so, libqmultikey.so and libqpickboard.so, and did not get any output.  Tried ldd --help and that gives an output. Are the libq* files complied as static, or am I missing something for ldd to fully work? It did not indicate any depends in its ipkg description.
   Thanks
      Carl

Title: Ldd Tool
Post by: lardman on April 10, 2006, 06:19:26 am

Interesting....

Does it work against the actual lib file (rather than the symlink)?

What about when you run it against a binary executable (rather than a lib)?


Si

Title: Ldd Tool
Post by: cwall on April 11, 2006, 04:43:26 am

No it also does not work with executables or run against the direct file instead of the link.
   Carl

Title: Ldd Tool
Post by: Mickeyl on April 11, 2006, 06:08:41 pm

export LD_TRACE_LOADED_OBJECTS=1
./runTheObjectToInspect

Title: Ldd Tool
Post by: cwall on April 18, 2006, 08:21:01 pm

Hi Mickey
  Not sure what you are suggesting, since that line is in the ldd script.  On the weekend I got the ldd scipt from Debian 3.1 and changed the first line to use sh instead of bash, and installed on the SL-5500.  It works fine and gives the outputs which I would expect when it is run against executables and also the plugin libs.  So something is not right in the existing script in the 3.5.4 feed.
         Cheers
           Carl

Title: Ldd Tool
Post by: lardman on April 19, 2006, 05:01:29 am

Can you submit a bug report about this please?


Si

Title: Ldd Tool
Post by: cwall on April 19, 2006, 01:46:58 pm

Quote

Can you submit a bug report about this please?


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=123740\"][{POST_SNAPBACK}][/a][/div]

  Done
     Carl

Title: Ldd Tool
Post by: cwall on April 22, 2006, 10:45:27 am

Looking further on the net I have found that "set -o pipefail"  in the ldd script casues ash shell in busybox to exit.

Busy box bug  

http://bugs.uclibc.org/view.php?id=794 (http://bugs.uclibc.org/view.php?id=794)

The work arount is to remove the "set -o pipefail" which is a test to see if it is running on Bash 3.x or fix busybox so it does not choke on the line.

    Carl