On Jul 21, 2013, at 16:19, MacPorts <[email protected]> wrote:

> + You can also consider using the `--enable-readline` flag if you want the 
> [wiki:SummerOfCode#interactive "interactive" `port(1)` command] to have 
> readline support; however, if you have a custom version of readline 
> installed, you might have to use the `--disable-readline` flag instead. You 
> will also have to tell the configure script where your X11 is. On older 
> versions of OS X, this can be done with the following flags:
> +{{{
>   --x-includes=/usr/X11R6/include \
>   --x-libraries=/usr/X11R6/lib \
> -  --with-tclpackage=$HOME/macports/share/macports/Tcl
> -
> +}}}
> + On newer versions of OS X, the flags are:
> +{{{
> +  --x-includes=/usr/X11/include \
> +  --x-libraries=/usr/X11/lib \
> +}}}
> + On versions of OS X where only XQuartz is available (i.e. Mountain Lion and 
> later), the flags are:
> +{{{
> +  --x-includes=/opt/X11/include \
> +  --x-libraries=/opt/X11/lib \
> +}}}

Surely MacPorts itself doesn't require any part of X11?

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to