Use configure.ldflags-delete instead of configure.ldflags?

Anders F Björklund afb at
Fri Mar 18 01:41:48 PDT 2011

Ryan Schmidt wrote:

>>>> and 'ldflags' should (imho) be safe for a port to simply reset. This seems demonstrative of the problems that can emerge with base implicitly setting environmental variables and other build-time arguments; it's much harder to control them directly from a port when you need something different.
>>> Then how would you suggest the user's need -- of building all libraries with maximum header padding -- be met?
>> "port install inkscape" ?
> does that meet the need? To my knowledge, by default, software does not build using the maximum header padding flag. This thread is the discussion about adding that flag to base.

"I am trying to have "-Xlinker -headerpad_max_install_names" added to all ports' ldflags by modifying /opt/local/share/macports/Tcl/port1.0/portconfigure.tcl"

"I managed to build the dependencies for inkscape (the reason why I am doing all this) with "-Wl,-headerpad_max_install_names" added to portconfigure.tcl without apparent problem."

So it seems like the main reason to add the maximum header padding is so that one can modify the libraries with install_name_tool to be able to relocate them to outside MacPorts for inclusion in an application bundle ?

If instead including the application in MacPorts, there is no need for such relocation... Of course, there might be other reasons to modify the ldflags. Just like there are some valid reasons to modify cflags.


More information about the macports-dev mailing list