#16139: erlang R12B-3 fails to build on upgrade ---------------------------------+------------------------------------------ Reporter: db.evans@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Resolution: | Keywords: erlang odbc ---------------------------------+------------------------------------------ Comment (by db.evans@gmail.com): More information: This error only occurs when port unixODBC '''IS''' present. The problem is due to the way that erlang's test for ODBC support in configure works. The summary for this ticket should changed to {{{ erlang R12B-3 fails to build when unixODBC is present }}} Configure checks for sql.h in a number of "standard" places (which does '''NOT''' include ${prefix}. It finds sql.h (provided by iodbc that comes with darwin) in /usr/include and decides that odbc is installed in prefix /usr Configure then checks for libodbc to confirm but uses the ${prefix} install prefix this time and finds libodbc (provided by unixODBC) in ${prefix}/lib. It concludes that ODBC support is present (true) but uses the install path from the sql.h check (/usr) as the location for libodbc (false). As a result, configure turns on ODBC support but inserts {{{ -L /usr/lib -lodbc }}} in the link command which fails because there is no libodbc at /usr/lib (only libiodbc). There are at least two ways to fix this. Patch configure to look for libiodbc on darwin platforms in which case the correct flags are {{{ -L/usr/lib -liodbc -liodbcinst }}} (as provided by iodbc-config) but this mixes /usr prefixes with ${prefix} prefixes which may cause problems? or Patch configure to add ${prefix} to the list of paths that it searches for sql.h so that it will find the correct install path for unixODBC or other MacPorts ODBC provider in which case the flags {{{ -L${prefix}/lib -lodbc }}} should be generated. or both (with MacPorts libodbc overriding libiodbc if present) I'm willing to take a crack at a patch for this but would welcome any input or suggestions on approach from the principal maintainer (or anyone else for that matter). -- Ticket URL: <http://trac.macports.org/ticket/16139#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS