Several errors building gnutls

Ryan Schmidt ryandesign at macports.org
Thu May 29 20:18:30 PDT 2008


On May 17, 2008, at 14:27, Brian P. Flaherty wrote:

> On Wed, 14 May 2008, Chris Pickel wrote:
>
>> If you're concerned about your MacPorts installation, the best  
>> thing to do
>> would be to remove the configure args you added, then `sudo port - 
>> f configure
>> libgcrypt`, and find config.log in `sudo port dir libgcrypt`/work.  
>> That might
>> have some info.
>
> Thank you for the suggestion.  I just had a similar problem with mc  
> being unable to find pkg-config.  I ran sudo port -f configure as  
> suggested above and it shows this as the path:
>
> PATH: ${prefix}/bin
> PATH: ${prefix}/sbin
> PATH: /bin
> PATH: /sbin
> PATH: /usr/bin
> PATH: /usr/sbin
> PATH: /usr/X11R6/bin
> PATH: /usr/texbin

I didn't quite understand... what command causes these paths to be  
printed out like this?

> I assume ${prefix} is to be /opt/local (it is defined as such on  
> the configure call), but it is getting lost somewhere.  I  
> temporarily created a soft link from /opt/local/bin/pkg-config to / 
> usr/bin/ and then mc configured without error.  Is there a short  
> list of places where these paths are defined for the MacPorts build  
> environment that I can check?

What is the error you experienced when configuring mc without this hack?



More information about the macports-users mailing list