Opened 15 years ago

Last modified 5 years ago

#17217 accepted defect

mod_mono does not generate mod_mono.so

Reported by: vnyx Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: mod_mono

Description

A symlink is created that points to mod_mono.0.0.0.so but this file does not exist after installation. Using Mac OS X 10.4 and 10.5 finding same result.

Change History (4)

comment:1 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Priority: HighNormal

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.

comment:2 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:3 Changed 5 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Owner: changed from macports-tickets@… to MarcusCalhoun-Lopez
Status: newaccepted

comment:4 Changed 5 years ago by mf2k (Frank Schima)

Keywords: mono removed
Note: See TracTickets for help on using tickets.