lynx port

Ryan Schmidt ryandesign at
Sat Mar 31 01:34:50 PDT 2007

On Mar 31, 2007, at 03:16, Boey Maun Suang wrote:

>> LD_LIBRARY_PATH and DYLD_LIBRARY_PATH, and any other similar  
>> variables I may not yet know about, and give advice about the  
>> scenarios in which one might want to use each of them, or point to  
>> a document where such explanations are already made?
> As I understand it (if anyone else knows better, please correct  
> me), it works like this:
> Apologies for the length of this post, and do keep in mind that,  
> though the above is long, it's still only my two cents.

My my. That's a lot to remember. But now I understand it much better.  
Thank you for being so verbose and so clear!

With CFLAGS, LDFLAGS and friends, we have to be careful not to  
overwrite but merely to append, in case some things are already  
defined in those variables. For example, CFLAGS by default includes - 
O2; if we overwrite CFLAGS we've just dropped optimization back to - 
O0, which may not have been intended. Do we have the same problem  
with CPATH and LIBRARY_PATH, or can I assume that they are empty to  
begin with and just set them to what I want?

More information about the macports-dev mailing list