Public bug reported:

Trying to dlopen() "/usr/lib/arm-linux-gnueabihf/libx264.so.164" fails
with the error:

/usr/lib/arm-linux-gnueabihf/libx264.so.164: cannot enable executable
stack as shared object requires: Invalid argument

But it works on amd64.

Attaching two C codes to test.
Steps:
1. Use amd64 chroot or vm
2. install libx264-164.
3. cc test_amd64.c
4. ./a.out
5. It prints "no error in dlopen".

Try same with armhf chroot or vm.
Steps:
1. Use armhf chroot or vm
2. install libx264-164.
3. cc test_armhf.c
4. ./a.out
5. It fails with the error "/usr/lib/arm-linux-gnueabihf/libx264.so.164: cannot 
enable executable stack as shared object requires: Invalid argument".

** Affects: x264 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to x264 in Ubuntu.
https://bugs.launchpad.net/bugs/2099733

Title:
  fails to dlopen on armhf

Status in x264 package in Ubuntu:
  New

Bug description:
  Trying to dlopen() "/usr/lib/arm-linux-gnueabihf/libx264.so.164" fails
  with the error:

  /usr/lib/arm-linux-gnueabihf/libx264.so.164: cannot enable executable
  stack as shared object requires: Invalid argument

  But it works on amd64.

  Attaching two C codes to test.
  Steps:
  1. Use amd64 chroot or vm
  2. install libx264-164.
  3. cc test_amd64.c
  4. ./a.out
  5. It prints "no error in dlopen".

  Try same with armhf chroot or vm.
  Steps:
  1. Use armhf chroot or vm
  2. install libx264-164.
  3. cc test_armhf.c
  4. ./a.out
  5. It fails with the error "/usr/lib/arm-linux-gnueabihf/libx264.so.164: 
cannot enable executable stack as shared object requires: Invalid argument".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/2099733/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to