Cached configure?

Greg greg at
Sun Apr 22 09:28:36 PDT 2007

Thanks Maun Suang!

I was beginning to worry that I would receive no reply at all to this  
inquiry.  To be honest I don't even remember anymore which port I was  
having this problem, but I can say that in my experience it seems to  
have been the vast majority of them.

Correct me if I'm wrong, but since I don't want to override the  
default configure arguments I think I want to use configure.args- 
append="-C", correct?

Thanks again for your reply!

- Greg

On Apr 12, 2007, at 11:04 AM, Boey Maun Suang wrote:

> On the other hand, if you're talking about overriding the flags on  
> the command line, you can just specify them at the end, e.g.:
> sudo port install <port> configure.args="<other_args> -C <other_args>"
> I imagine that configure.args-append will also work, but I haven't  
> tested it yet (I really should).
> I'm curious, however, as to which port or ports you're experiencing  
> this problem with, as it seems to me that this might be better  
> reported to the upstream maintainers.  Speaking only for myself,  
> I've noticed that the various ports related to the Courier project  
> (courier-imapd, courier-authlib, maildrop) run a separate instance  
> of configure in each subdirectory of the unpacked source, and I  
> don't imagine that forcing caching will help in this case, as the  
> cache from the previous run of configure won't appear in the  
> directory in which the new run of configure occurs.  (I've really  
> been meaning to contact them about this too; it's the only project  
> that I can recall building where the configure time significantly  
> exceeds the compile time.)
> Kind regards,
> Maun Suang
> -- 
> Boey Maun Suang (Boey is my surname)
> Mobile: +61 403 855 677
> Email: boeyms at

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the macports-dev mailing list