I saw at http://www.privoxy.org/faq/misc.html#TOR how I can configure the
config file to forward calls to tor by uncommenting
#forward-socks5 / 127.0.0.1:9050 .
in the file config. But the config file in /opt/local/etc/privoxy seems to
be empty . So is config.new . Is
Dear list,
I'm curious to know whether this is intended behaviour or not.
(I would have created a ticket in tracker, but I'm not sure if this is
actually a bug or simply the way how macports operates and there is
not much that could be done about it anyway.)
port installed pango cairo
The
As the error message indicates, pango and cairo should be installed with the
same x11 and quartz variants.
You have cairo installed with +x11 +quartz and are trying to install pango -x11
+quartz.
I'm curious to know whether this is intended behaviour or not.
(I would have created a ticket in
Hello,
I have two installations of Python 2.7.2 -- from MacPorts and Enthought --
on my Mac. I use the Enthought Python as the primary one for performance
reasons(MKL Blas included); however, my MacPorts distribution has several
additional packages like pymacs, rope etc., which I would like to
On Tue, Apr 17, 2012 at 14:43, Jeremy Lavergne wrote:
As the error message indicates, pango and cairo should be installed with the
same x11 and quartz variants.
You have cairo installed with +x11 +quartz and are trying to install pango
-x11 +quartz.
I understand that there has to be a
I understand that there has to be a match between versions. What
wasn't perfectly clear to me was whether or not macports could use a
disabled (already installed) version with matching options or not
(possibly by switching versions back and forth).
MacPorts can swap between installed versions
On Apr 17, 2012, at 08:15, Kamesh Krishnamurthy wrote:
I have two installations of Python 2.7.2 -- from MacPorts and Enthought -- on
my Mac. I use the Enthought Python as the primary one for performance
reasons(MKL Blas included); however, my MacPorts distribution has several
additional
Is there a clean way to make the MacPorts packages available to the
Enthought Python without breaking anything? I'd prefer not having multiple
copies of rope, pymacs etc., if possible.
They're not designed to be used that way; I don't know if they can be made to
work that way.
If you
Kamesh,
I do not use the Enthought python distribution, but in other python
distributions the path that is searched for modules is affected by the
PYTHONPATH environment variable, and is also accessible/editable in the python
interpreter by
import sys
sys.path.append('/path/to/add/')
In article 71147bab-dd71-4110-91d9-e7bb11370...@fusion.gat.com,
Sterling Smith smit...@fusion.gat.com wrote:
I do not use the Enthought python distribution, but in other python
distributions the path that is searched for modules is affected by the
PYTHONPATH environment variable, and is also
My main reason for using Enthought Python is that they build Numpy and
Scipy with intel MKL libraries -- these are significantly faster than the
Accelerate framework on the Mac which MacPorts Numpy and Scipy use.
It would be great if MacPorts can include the Intel MKL runtime libraries
in their
Hi,
On 17 Apr 2012, at 7:56pm, Kamesh Krishnamurthy wrote:
My main reason for using Enthought Python is that they build Numpy and Scipy
with intel MKL libraries -- these are significantly faster than the
Accelerate framework on the Mac which MacPorts Numpy and Scipy use.
Based on the
py-numpy and py-scipy have atlas variants which use the atlas port instead of
the Accelerate framework. The atlas port does tune to your processor. Have you
tried that? I have Cc'ed Adam, the maintainer of these ports, if he could
comment on their performance with the atlas variant? Maybe the
Nope. Sorry. But the it works for me argument just isn't going to work.
I have tried both i386 (32 bit) and x86_64…and have the same issues
(eventually) and IT IS because of Clang. I have never had so many problems
compiling with GCC, and then maintaining them through normal upgrades. I
use
On Apr 15, 2012, at 10:56 AM, Michael_google gmail_Gersten wrote:
I am not sure which version of Wine to install from Macports (there
are three), or if this is even the right approach for what I want to
do.
The goal: Edit a movie (screen recording), from the view that 80-90%
of what I
On Apr 17, 2012, at 4:16 p.m., Jeff Singleton wrote:
If its not Clang as you suggest, and you think its a linking issue, then it
is a Macports problem. I don't mix my architectures. My macports.conf either
says build_arch i386 or it says build_arch x86_64. I don't add anything to
the
On Apr 16, 2012, at 11:51 a.m., Jeff Singleton wrote:
If you are able to build Pango weekly…then you must be doing something
differently that I. Possibly not using the same Arch/Platform or possibly
you customize your Portfile prior to building. My issues stem from the
default Portfile
Nope. Sorry. But the it works for me argument just isn't going to work.
Continuing to chant it doesn't work is just as helpful. Post logs detailing
your issues and point them out. You've been asked to do this a couple times now.
Without those, the whole thread appears useless.
I have tried
On Tue, 17 Apr 2012, Michael_google gmail_Gersten wrote:
On Apr 15, 2012, at 10:56 AM, Michael_google gmail_Gersten wrote:
I am not sure which version of Wine to install from Macports (there
are three), or if this is even the right approach for what I want to
do.
The goal: Edit a movie
No one else seems to be having the issues you are. I personally compiler a lot
of ports with clang, no problem. Doesn't that tell you something ?
Your rants below are useless. Unless you intend to actually start posting
useful bug reports, build logs etc. then please take your outburst
On Apr 17, 2012, at 1:16 PM, Jeff Singleton gvib...@gmail.com wrote:
Nope. Sorry. But the it works for me argument just isn't going to work.
I have tried both i386 (32 bit) and x86_64…and have the same issues
(eventually) and IT IS because of Clang.
Prove it. File a bug, and I will fix
I'm not sure why the pango won't build portion of this thread is continuing,
since it's already been fixed:
https://trac.macports.org/ticket/32722
___
macports-users mailing list
macports-users@lists.macosforge.org
22 matches
Mail list logo
