[asterisk-bugs] [JIRA] (ASTERISK-27595) [patch] BuildSystem: Invoke ldconfig with previous paths.
Alexander Traud (JIRA)
noreply at issues.asterisk.org
Wed Jan 17 08:11:50 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Traud updated ASTERISK-27595:
---------------------------------------
Comment: was deleted
(was: Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].)
> [patch] BuildSystem: Invoke ldconfig with previous paths.
> ---------------------------------------------------------
>
> Key: ASTERISK-27595
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27595
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/BuildSystem
> Affects Versions: 13.19.0, 15.2.0
> Environment: OpenBSD 6.2
> Reporter: Alexander Traud
> Severity: Critical
>
> When you go for{code}gmake uninstall{code}the Makefile calls {{ldconfig}} without any parameter like a directory. On OpenBSD, only the default directory is scanned: /usr/lib. {{ldconfig}} does not scan /usr/local/lib. Therefore, the user is not able to run {{gmake}} anymore after an uninstall. To escape this situation, the user has to exit the shell, reboot the computer, or do{code}ldconfig /usr/local/lib{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list