On Jun 18, 2008, at 11:45 PM, Eugene Vilensky wrote:
>> Why do you need glib 1.2.10, by the way? The current version of
>> glib is in
>> the glib2 port. glib 1.2.10 is old and may not be expected to work on
>> Leopard.
>
> I was actually trying to install xeyes as a test, which told me I was
> m
> Why do you need glib 1.2.10, by the way? The current version of glib is in
> the glib2 port. glib 1.2.10 is old and may not be expected to work on
> Leopard.
I was actually trying to install xeyes as a test, which told me I was
missing pkgconfig.
Here is a bunch of the output. I'm pretty lost;
On Jun 18, 2008, at 11:01 PM, Ryan Schmidt wrote:
> On Jun 18, 2008, at 10:46 PM, Eugene Vilensky wrote:
>
>> I have searched Trac, Google, and the list archives; I can't build
>> any
>> ports from a clean install because it seems like my base dependencies
>> refuse to build.
>>
>> I am using an
On Jun 18, 2008, at 10:46 PM, Eugene Vilensky wrote:
> I have searched Trac, Google, and the list archives; I can't build any
> ports from a clean install because it seems like my base dependencies
> refuse to build.
>
> I am using an svn trunk from just a few hours ago, in desperation, but
> the
Am 18.06.2008 um 16:06 schrieb Mike:
> What advantage is there to using python from ports vs the native osx
> python installation in /usr/bin/ ?
>
> -mike
Well, using Macports I follow the philosophy not to play around
(install additional packages i.e.) with the system frameworks but
havi
On Jun 18, 2008, at 7:54 AM, Jochen Küpper wrote:
> Hi,
>
> so in Ticket #15049 I proposed a patch to install man-files and info-
> pages of gcc-4.3 in a custom location in order to get them installed
> without conflicts between different gcc version.
>
> However, the line
> file copy ${destroo
Hi,
so in Ticket #15049 I proposed a patch to install man-files and info-
pages of gcc-4.3 in a custom location in order to get them installed
without conflicts between different gcc version.
However, the line
file copy ${destroot}${prefix}/share/man/man7/* ${destroot}${prefix}/
share/gcc43
When upgrading rb-rubygems, I noticed the following:
install -c -m 0644 ubygems.rb /opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_ruby_rb-rubygems/work/destroot/opt/local/
lib/ubygems.rb
note: that is "ubygems.rb" appearing twice. Is this correc
Martin,
What do you mean by the standard site-packages directory. The system
python and the macports python are going to completely different
locations. Virtual python? You mean Virtualenv?
Regards,
Ken
On Jun 18, 2008, at 8:37 AM, Martin Stadler wrote:
> I'm not shure about the deta
Am 18.06.2008 um 15:49 schrieb Rainer Müller:
> Martin Stadler wrote:
>> I'm not shure about the details but Python is installed as a OS X
>> framework in
>> /opt/local/Library/Frameworks/Python.framework
>> Python packages are not installed in the standard site-packages
>> directory an
Martin Stadler wrote:
> I'm not shure about the details but Python is installed as a OS X
> framework in
> /opt/local/Library/Frameworks/Python.framework
>
> Python packages are not installed in the standard site-packages
> directory and virtual python[1] is not working with setuptools th
I'm not shure about the details but Python is installed as a OS X
framework in
/opt/local/Library/Frameworks/Python.framework
Python packages are not installed in the standard site-packages
directory and virtual python[1] is not working with setuptools this way.
Martin
[1]
http://peak.
Hi!
I'm using python24 with the puredarwin variant because it seems to fit
better with virtual python, easy install and Plone. Then I upgraded my
Python and now it looks like the puredarwin variant was not used. Now
I uninstalled and cleaned everything and tried to install but I get an
err
13 matches
Mail list logo