Hi, Is there any way of knowing what build flags were used for a given port? Specifically I am tryng to work out with the Apache2 build has been configured with IPv6 support. Andre
On 12.05.2007, at 17:38, Andre-John Mas wrote:
Is there any way of knowing what build flags were used for a given port?
If you are talking about variants: you can see the variants used for an installed port in the list you get with sudo port installed They are listed at the end of the version string: py-matplotlib @0.90.0_0+gtk2 (active) This prort was build with variant gtk2 for me. HTH Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On May 12, 2007, at 10:38, Andre-John Mas wrote:
Is there any way of knowing what build flags were used for a given port? Specifically I am tryng to work out with the Apache2 build has been configured with IPv6 support.
If you install the port using the -dv options you can see the commands as they're assembled, including the ./configure command which would show all the flags. sudo port install -dv apache2
On 12-May-07, at 11:38 , Andre-John Mas wrote:
Hi,
Is there any way of knowing what build flags were used for a given port? Specifically I am tryng to work out with the Apache2 build has been configured with IPv6 support.
Turns out another approach is to go to: http://svn.macports.org/repository/macports/trunk/ navigate to the package you are interested in and then open up the 'Portfile'. In my case it turns out that IPv6 is not enabled. Andre
On May 13, 2007, at 11:33, Andre-John Mas wrote:
Is there any way of knowing what build flags were used for a given port? Specifically I am tryng to work out with the Apache2 build has been configured with IPv6 support.
Turns out another approach is to go to:
http://svn.macports.org/repository/macports/trunk/
navigate to the package you are interested in and then open up the 'Portfile'.
In my case it turns out that IPv6 is not enabled.
Sure, if you'd like to read the portfile, that's another option. You can do so directly on your system using either "port edit foo", if you have your EDITOR environment variable set up properly, or otherwise with "port cat foo" or even "port cat foo | less".
participants (3)
-
Andre-John Mas
-
Jochen Küpper
-
Ryan Schmidt