reconfigure doesn't take?

[Rainer Müller]

On 2013-04-21 00:07, Roger Pack wrote:
> Possibly this is caused by having a version of macports "already in
> the path"?  Can anyone confirm?  Maybe configure should fail or warn
> in this case, if so?

I haven't checked the original problem yet, but yes, having another
MacPorts installation in PATH will cause problems. You want to link
against software provided by Mac OS X and not from the other MacPorts
installation. The configure script automatically removes the target
prefix from PATH, but not any other MacPorts installation.

Rainer