| 21 | | I finally understood that gcc is actually **not checking /usr/include** (and /usr/lib) which is the default path where the CommandLineTOols SDKs is included. |
| 22 | | I think it has been changed since I'm pretty sure that previous versions of the gcc port have been checking /usr/include. A fix for now is to use {{{gcc -I/usr/include -L/usr/lib}}}... Is there a way to change this default behavior? i.e. add /usr/include and /usr/lib to the default searching path of macports' gcc? |
| | 21 | I finally understood that gcc is actually **not checking /usr/include** (and /usr/lib) which is the default path where the CommandLineTOols SDKs is installed. |
| | 22 | |
| | 23 | I think it has been changed since I'm pretty sure that previous versions of the gcc port did check /usr/include. A fix for now is to use {{{gcc -I/usr/include -L/usr/lib}}}... Is there a way to change this default behavior? i.e. add /usr/include and /usr/lib to the default searching path of macports' gcc? |
