Re: Running strip on libpython3.so twice creates statically linked files

[Nick Clifton]

Hi Junsong,

  Please could you refile this problem using the binutils bug reporting
  system here:

    https://sourceware.org/bugzilla/enter_bug.cgi?product=binutils

  It really helps to have a bug report where we can track problems and
  their solutions.


> Hello, I find out strip (version 2.7 and 

  I assume that you mean version 2.37 ?

> $ ldd python/install/lib/libpython3.so
>          statically linked

  Strangely for me when I tried this sequence of instructions using
  a version of strip built from the latest sources I get a slightly
  different behaviour:

    $ ldd python/install/lib/libpython2.so
    $

  (ie no output at all).  Plus file still thinks that the binary
  is a dynamically linked entity:

    $ file python/install/lib/libpython3.so
    libpython3.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), 
dynamically linked, stripped

  But obviously there is a problem here that needs to be resolved.

Cheers
  Nick