About new default configure-{c(pp|xx)?,ld}flags

[Paul Guyot]

On May 26, 2007, at 5:48 AM, N_Ox wrote:

> Hello,
>
> The new configure flags change made in 1.4 seems to cause problems  
> with some ports (at least 2, maybe more).
> This change introduces things like default ldflags -L/opt/local/lib.
> The problem with these flags is that some ports write ENV flags  
> before the configure script ones.
> On a port upgrade, this causes gcc to include the installed headers  
> instead of the distfile ones, the same goes
> for ld and liking against libs.
>
> As this is useful only if the port depends on some other ports, why  
> not put these defaults settings only if
> the port does depend on another one?

This problem is not new and it is not related to the default flags.  
For example, it occurs with ruby where, before I patched it, the  
bootstrap ruby interpreter that was used was the one in /opt/local on  
upgrade.

The virtual chroot technology will fix that globally, by hiding a  
previous version of an installed port on upgrade. In the meanwhile,  
port maintainers are invited to fix the problem on each port. And  
removing ldflags is only a partial fix, as a previous version of the  
software could be elsewhere on the -L path (e.g. in /usr/).

Paul
-- 
http://paul-guyot.com/