Bug #577
absolute build path in liboml2.so.0.6.1 and libocomm.so.0.0.0
| Status: | Closed | Start date: | 24/08/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | Olivier Mehani | % Done: | 0% |
|
| Category: | build | |||
| Target version: | 2.7.0 |
Description
If you just do a ./configure; make; make install with OML, the installed liboml2.so.0.6.1 and libocomm.so.0.0.0 will contain the absolute path of the directory you built in. It can be seen when opening the library in vim.
Stripping does get rid of it, my solution for now is to run make install-strip for now in the RPM .spec file.
Note that this does not occur when building the debian packages, since we call "dh_strip" in the debian/rules by default.
This may not be an issue at all, so feel free to close it anytime.
History
Updated by Thierry Rakotoarivelo 7 months ago
- Target version set to 2.7.0
Updated by Olivier Mehani 2 months ago
Christoph: isn't this issue fixed by 6b56d6d83246d62f8a95f07a9ba019eae6a4d687 and c60699814ce5384884206f28fcc073874aa4904e ?
Updated by Christoph Dwertmann 2 months ago
- Status changed from Assigned to Closed
6b56d6d83246d62f8a95f07a9ba019eae6a4d687 fixes it in the .la file only. c60699814ce5384884206f28fcc073874aa4904e added stripping to the RPM build.
Stripping fixes it for the binary package distribution. I was just wondering how the full path ended up in the libraries in the first place. Maybe this can somehow be rectified by automake?
Since it's a non-issue I'm closing this now.