On 07.11.13 00:47, Ryan Schmidt wrote:
>
> On Nov 6, 2013, at 18:43, Jann Röder wrote:
>
>> /usr/include doesn't exist on Mavericks.
>
> It does if you install the Xcode command line tools, which MacPorts requires,
> as it always has.
>
>
Ok fine. I didn't realize that this is now a complete
In article ,
Jann Roder wrote:
> /usr/include doesn't exist on Mavericks. Its content is now at
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer
> /SDKs/MacOSX10.9.sdk/usr/include/
That's not true. You have to properly install the Command Line Tools package,
ju
On Nov 6, 2013, at 18:43, Jann Röder wrote:
> /usr/include doesn't exist on Mavericks.
It does if you install the Xcode command line tools, which MacPorts requires,
as it always has.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
ht
/usr/include doesn't exist on Mavericks. Its content is now at
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/
I found that xcrun --show-sdk-path gives me the desired path. Now I just
need to feed this into a tcl variable. Unfortunate
On 2013-11-7 11:31 , Jann Röder wrote:
> Hi,
> it appears that in order to build gpg using Xcode 5 correctly we need to
> specify the absolute path to stdint.h in the portfile. On my system the
> files is at
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOS
Hi,
it appears that in order to build gpg using Xcode 5 correctly we need to
specify the absolute path to stdint.h in the portfile. On my system the
files is at
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/stdint.h
I was wondering i
