[libcxx-commits] [PATCH] D110887: [libcxx][test] Use python specified by build rather than system default python

[Leonard Chan via Phabricator via libcxx-commits]

leonardchan added a comment.

Oh, thanks for catching a bunch of things I missed and reverting (both the u16 test and this patch). I completely missed that `python` in this case was a gdb command here. Thanks for the explanation also.

> Could you tell me your:
>
> - OS/architecture

x86_64-unknown-linux-gnu

> - gdb version

`GNU gdb (GDB) 10.0-gg5`

> - python version that gdb is linked to

I think my libpython appears to be statically linked in(?)

  $ ldd $(which gdb)
  	linux-vdso.so.1 (0x00007ffe6a340000)
  	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa2a7b13000)
  	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa2a7af1000)
  	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa2a7aeb000)
  	libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fa2a7ae6000)
  	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa2a7921000)
  	/usr/grte/v4/lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fa2a7c82000)

But I think I should be able to check with:

  $ gdb --ex "python import sys; print sys.version" --batch
  2.7.6 (default, Mar 30 2016, 12:21:08) 
  [GCC 4.8.x-google 20131105 (prerelease)]


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D110887/new/

https://reviews.llvm.org/D110887