#17217: mod_mono does not generate mod_mono.so -------------------------------+-------------------------------------------- Reporter: ggreen@mailw.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mono Port: mod_mono | -------------------------------+-------------------------------------------- Changes (by ryandesign@macports.org): * cc: ryandesign@macports.org (added) * priority: High => Normal Comment: Here's what I can figure out. mod_mono builds a shared library mod_mono.0.0.0.so in its build directory and has two symlinks that point to it, mod_mono.0.so and mod_mono.so. During destroot, it calls upon apxs (part of apache2) to install this into the apache2 modules directory. apxs calls instdso.sh (part of apache2). instdso.sh calls libtool (part of apr). libtool copies mod_mono.0.0.0.so into the modules directory, and recreates the mod_mono.0.so and mod_mono.so symlinks. Then after libtool is finished, instdso.sh deletes mod_mono.0.0.0.so and mod_mono.0.so, leaving us with only the symlink mod_mono.so pointing at something nonexistent. Upgrading the mod_mono port to 2.0 didn't change this. Every other module in the apache2 modules directory exists only once: the shared library itself is called mod_whatever.so. There are no symlinks, and no modules with version numbers in their name. I don't know whose problem this is, but we should probably start by reporting the problem to the developers of mod_mono. -- Ticket URL: <http://trac.macports.org/ticket/17217#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS