On Nov 10, 2014, at 5:30 PM, René J.V. Bertin wrote:
> On Monday November 10 2014 17:13:56 Ryan Schmidt wrote:
>
>> Apple intentionally does not provide a way to tell the linker which version
>> of the framework to use; the intention is that you will link with the latest
>> version. The reason
On Monday November 10 2014 17:13:56 Ryan Schmidt wrote:
> Apple intentionally does not provide a way to tell the linker which version
> of the framework to use; the intention is that you will link with the latest
> version. The reason for continuing to provide old versions of a framework is
> s
On Nov 10, 2014, at 4:31 AM, René J.V. Bertin wrote:
>
> I've always wondered: Apple describe how you can make frameworks containing
> several main versions, but never document how to tell the linker which one to
> use... It clearly doesn't pick the newest version because I don't have Python
>
On Monday November 10 2014 16:08:46 Jeremy Lavergne wrote:
> I think Python builds as a framework, so you’d want to check the
> Library/Framework/Python/ directories instead.
It does, hence I pass
-DPYTHON_SITE_PACKAGES_INSTALL_DIR=${frameworks_dir}/Python.framework/Versions/${python.branch}/lib
I think Python builds as a framework, so you’d want to check the
Library/Framework/Python/ directories instead.
On Nov 10, 2014, at 16:06, René J.V. Bertin wrote:
> /opt/local/lib/pythonX/site-packages
___
macports-users mailing list
macports-users@l
On Monday November 10 2014 11:31:23 René J.V. Bertin wrote:
I've gotten a bit further. Stuff installs, but apparently MacPorts' python
doesn't look in /opt/local/lib/pythonX/site-packages so I'll have to figure out
why things get installed there.
Also, I'll have to figure out how to convince th
Okay, it’s starting to sound like apxs needs run since php5 was made obsolete
(that’s the package libphp5.so belonged to).
I’d just follow the next steps for setting up php56 with Apache to get you up
and running again (uses php56-apache2handler), after deleting that libphp5.so
reference from l
It was installed and working before the update, but when I do:
which php
I get usr/bin/php not the one that macports would have installed, so it
appears that it may have gotten hosed as well.
When I install php56, it acts like it's already installed. Same with apache2.
Jeff
> On Nov 10, 2
Is PHP installed?
Also, don’t manually do things inside the directories that Macports owns. It’ll
just bite you harder than this if you aren’t mindful of the consequences.
On Nov 10, 2014, at 11:27, SH Development wrote:
> What happened here, and how do I fix it? Can I just copy that module
Ran selfupdate a few days ago, it upgraded to 2.3.2. Rebooted the machine,
noticed that Apache was no longer running.
When I try to start Apache 2.2.9, I now get:
httpd: Syntax error on line 118 of /opt/local/apache2/conf/httpd.conf: Cannot
load /opt/local/apache2/modules/libphp5.so into serve
The long paths are not a MacPorts specific issue
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750231
On 10/11/14 08:20, Nicolas Pavillon wrote:
Hello,
It's been some time, but I had tried to make a Portfile for pykde4, and
then gave up because of several different issues, including the
d
Hello,
It's been some time, but I had tried to make a Portfile for pykde4, and
then gave up because of several different issues, including the
dependencies to X11. These repeated paths also surely ring a bell. I
don't think I ever got around them, but did not try that hard either.
Cheers,
N
12 matches
Mail list logo
