Maneage - Bugs: bug #58465, Default Maneage on clean FreeBSD
You are not allowed to post comments on this tracker with your current authentication level.
bug #58465: Default Maneage on clean FreeBSD
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Sun 31 May 2020 04:02:33 AM UTC | ||
Category: | Software | Severity: | 3 - Normal |
Item Group: | Crash | Status: | Postponed |
Privacy: | Public | Assigned to: | makhlaghi |
Open/Closed: | Open |
Mon 01 Jun 2020 05:32:52 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi> |
Sun 31 May 2020 04:02:33 AM UTC, original submission:
It would help if we test Maneage on FreeBSD also (with its default settings). So I just made Virtual Machine of FreeBSD 12.1 and tried building Maneage there. So far, I found these complications:
|
Mohammad Akhlaghi <makhlaghi> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-f8d8.
Corresponding source code
The previous two issues are now being addressed as part of task #15667, but another important issue that comes up in FreeBSD is that its shared libraries (and patching them when necessary) are like GNU/Linux ('.so' suffix), not macOS (with '.dylib' suffix).
So as done in task #15667, we now read the kernel name with 'uname -s' and to fix problems with shared libraries, we should use PatchELF (which is also available with FreeBSD, it doesn't use macOS's 'install_name_tool'!).