Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qcc: Shared libraries reference dependencies with absolute paths #85

Closed
aelkhour opened this issue Aug 10, 2015 · 1 comment · Fixed by #162
Closed

qcc: Shared libraries reference dependencies with absolute paths #85

aelkhour opened this issue Aug 10, 2015 · 1 comment · Fixed by #162

Comments

@aelkhour
Copy link

I tried building boost 1.57 for qnxnto using
./b2 toolset=qcc target-os=qnxnto variant=release link=shared install
and I encountered the same issue as the one described here blackberry/Boost#11

The proposed solution of removing HAVE_SONAME in qcc.jam worked for me, and I was wondering:

  • whether this issue has been solved since 1.57,
  • whether removing SO_NAME is a clean solution.
@vprus
Copy link
Collaborator

vprus commented Nov 19, 2015

Antonio,

there were not changes. Removing HAVE_SONAME is a suitable solution. Since qnx apparently has soname option in the compiler, there is no reason to be overly generic in qcc.jam.

Possible, it is possible to entirely remove definition of link.dll function and action from qcc.jam, so that it inherits one from gcc jam, but I don't have any way to test such a change, and don't recall why qcc.jam overrides these.

grafikrobot pushed a commit that referenced this issue Oct 4, 2021
This resolves a warning that popped up when we switched to Clang as
Clang defines unix in addition to __unix__ unlike GCC.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants