On Sun, Sep 20, 2009 at 07:46:32PM -0500, Ryan Schmidt wrote:
> On Sep 20, 2009, at 11:11, Carson H. wrote:
>
> >With MP 1.8.0 under 10.6.1, "port install p5-macosx-file" yields:
> >
> >---> Building p5-macosx-file
>
> [snip]
>
> >Catalog.xs: In function 'xs_getcatalog':
> >Catalog.xs:70: error
On Wed, Sep 02, 2009 at 10:21:53AM -0500, Ryan Schmidt said:
> On Aug 31, 2009, at 11:25, Ryan Schmidt wrote:
>
> >I am attaching a script which reproduces the problem on my system
> >(clean install of Snow Leopard), and the output I get. When you run
> >it, do you see the problem on your system a
Am 21.09.2009 um 17:25 schrieb Ryan Schmidt:
/opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdebase4
-runtime/work/kdebase-runtime-4.3.0/kpasswdserver/kpasswdserver.h:
28:32: error: Qt3Support/Q3PtrList: No such file or directory
As such,
On Sep 21, 2009, at 3:46 PM, Luís Beça wrote:
On 2009-09-21, at 3:34 PM, Ryan Schmidt wrote:
On Sep 21, 2009, at 14:33, Luís Beça wrote:
I think it's probably because of the way the swig port is
written. It says:
default_variants+python +perl +ruby +php5
This means: these variants w
On 2009-09-21, at 3:34 PM, Ryan Schmidt wrote:
On Sep 21, 2009, at 14:33, Luís Beça wrote:
I think it's probably because of the way the swig port is written.
It says:
default_variants+python +perl +ruby +php5
This means: these variants will be autoselected. Always. Even if
you
On Sep 21, 2009, at 14:33, Luís Beça wrote:
I think it's probably because of the way the swig port is written.
It says:
default_variants+python +perl +ruby +php5
This means: these variants will be autoselected. Always. Even if
you have already requested other variants for this por
I think it's probably because of the way the swig port is written.
It says:
default_variants+python +perl +ruby +php5
This means: these variants will be autoselected. Always. Even if you
have already requested other variants for this port. Try deselecting
the undesired variants e
On Sep 21, 2009, at 14:23, Ryan Schmidt wrote:
I think it's probably because of the way the swig port is written.
It says:
default_variants+python +perl +ruby +php5
This means: these variants will be autoselected. Always. Even if you
have already requested other variants for this p
On Sep 21, 2009, at 14:18, Luís Beça wrote:
What command did you run to produce this output?
sudo port -vud install py26-scipy +gcc44
What do you have in variants.conf?
+bash_completion
I think it's probably because of the way the swig port is written. It
says:
default_variants
What command did you run to produce this output?
sudo port -vud install py26-scipy +gcc44
What do you have in variants.conf?
+bash_completion
Luís
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/
On 2009-09-21, at 2:50 PM, Ryan Schmidt wrote:
On Sep 21, 2009, at 13:43, Luís Beça wrote:
This is probably a stupid question but I'm trying to install py26-
scipy +gcc44 on Snow Leopard.
port deps py26-scipy +gcc44 says that scipy depends on python26,
py26-numpy, py26-nose,
SuiteSparse, s
On Sep 21, 2009, at 13:43, Luís Beça wrote:
This is probably a stupid question but I'm trying to install py26-
scipy +gcc44 on Snow Leopard.
port deps py26-scipy +gcc44 says that scipy depends on python26,
py26-numpy, py26-nose,
SuiteSparse, swig, gcc44 all of which I have installed. Howeve
Hi
This is probably a stupid question but I'm trying to install py26-
scipy +gcc44 on Snow Leopard.
port deps py26-scipy +gcc44 says that scipy depends on python26, py26-
numpy, py26-nose,
SuiteSparse, swig, gcc44 all of which I have installed. However, when
I try to install scipy, ports
st
Am 21.09.2009 um 17:25 schrieb Ryan Schmidt:
I haven't filed a bug report yet, because I'm entirely not sure
whether the problem is not sitting behind the desk.
Anyone got some ideas what is going wrong, or what I'm doing wrong
(or make a better bug report - I did built with the -v option
On Sep 21, 2009, at 10:04, Dominik Reichardt wrote:
I'm currently trying to build Krusader and it is proving to be a
tiresome thing to do.
All the dependencies are crazy.
A lot of things are broken when you choose to install "krusader
+universal", so that path has proven to be fruitless.
N
Hi all,
I'm currently trying to build Krusader and it is proving to be a
tiresome thing to do.
All the dependencies are crazy.
A lot of things are broken when you choose to install "krusader
+universal", so that path has proven to be fruitless.
Not building universal these dependencies stil
On 2009-9-22 00:21, Ryan Schmidt wrote:
> On Sep 21, 2009, at 09:14, William Davis wrote:
>
>> On Sep 21, 2009, at 7:46 AM, Mark Blackman wrote:
>>
>>> On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
>>>
>>>
The correct fix when upgrading from one major OS version to another
is to uninstal
On Sep 21, 2009, at 09:14, William Davis wrote:
On Sep 21, 2009, at 7:46 AM, Mark Blackman wrote:
On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
The correct fix when upgrading from one major OS version to
another is to uninstall all ports and reinstall them. See the
Migration page in the
On Sep 21, 2009, at 7:46 AM, Mark Blackman wrote:
On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
The correct fix when upgrading from one major OS version to another
is to uninstall all ports and reinstall them. See the Migration
page in the wiki:
http://trac.macports.org/wiki/Migration
On 21 Sep 2009, at 14:52, Ryan Schmidt wrote:
On Sep 21, 2009, at 08:48, Mark Blackman wrote:
Actually, is there some explicit provision for building a new
/opt from scratch in some other directory, then switching
it in as "the" new /opt (macport binaries).
Note the MacPorts prefix is /opt
On Sep 21, 2009, at 08:48, Mark Blackman wrote:
Actually, is there some explicit provision for building a new
/opt from scratch in some other directory, then switching
it in as "the" new /opt (macport binaries).
Note the MacPorts prefix is /opt/local, not /opt. There may be things
in /opt o
On Sep 21, 2009, at 08:48, Mark Blackman wrote:
On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
The correct fix when upgrading from one major OS version to another
is to uninstall all ports and reinstall them. See the Migration
page in the wiki:
http://trac.macports.org/wiki/Migration
Act
On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
The correct fix when upgrading from one major OS version to another
is to uninstall all ports and reinstall them. See the Migration page
in the wiki:
http://trac.macports.org/wiki/Migration
Actually, is there some explicit provision for bui
On 21 Sep 2009, at 12:41, Ryan Schmidt wrote:
The correct fix when upgrading from one major OS version to another
is to uninstall all ports and reinstall them. See the Migration page
in the wiki:
http://trac.macports.org/wiki/Migration
I thought you might say something like that. :)
I'
On Sep 21, 2009, at 06:23, Mark Blackman wrote:
Just as a heads-up and for the archives, I had a macports perl
installation 5.8.8 that predated Leopard and Snow Leopard.
After upgrading to Snow Leopard I was unable to
compile XS modules for perl, resulting in messages
something like 'ld: wrong
Hi,
Just as a heads-up and for the archives, I had a macports perl
installation 5.8.8 that predated Leopard and Snow Leopard.
After upgrading to Snow Leopard I was unable to
compile XS modules for perl, resulting in messages
something like 'ld: wrong architecture' at link time.
After some dete
26 matches
Mail list logo
