Binary can only run on startup after creating a symbolic link to it

I am facing a rather strange problem. I have a 32 bit qmake binary located on a very deep path. So for ease of use, I created a link using

ln -s / complex / path / to / qmake ~ / qmake

I am running a 64 bit machine. So I installed 32 bit libraries. Binary does not load on startup

~ / QMAKE

it reports an error not specifying such a file or directory when the file is. but it works smoothly when i use 32 bit laoder

/lib/ld-linux.so.2 ~ / qmake

More interesting thing here. If I run

/lib/ld-linux.so.2/complex/path/to/qmake

an error is displayed like

qmake: @ ɇ: QRU 4] ZY: H: error 18446744073564424934

but as I mentioned the binaries are loaded using a symbolic link

so i have 2 problems.

  • Why should I explicitly mention the bootloader with the app
  • Why is there an error with the full path ... when the symlink works fine?
+3


source to share


1 answer


As for # 2, it may happen that the original file path is longer than your shell or other operating environment can handle.



0


source







All Articles