On Fri, Aug 6, 2010 at 9:34 PM, Ryan Schmidt ryandes...@macports.org wrote:
The real error is hidden further up, but it's probably because you have an
sqlite library (possibly under /usr/local) that is not the right architecture.
You haven't by chance migrated this MacPorts installation to
On Aug 11, 2010, at 01:22, Alexy Khrabrov wrote:
http://trac.macports.org/wiki/Migration
Indeed. Following that, has reached step 3, and get:
--- Cleaning am-utils
Error: Unable to open port: can't read compiler.cpath: no such variable
compiler.cpath is new; it was added in MacPorts
On Wed, Aug 11, 2010 at 2:52 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 11, 2010, at 01:22, Alexy Khrabrov wrote:
http://trac.macports.org/wiki/Migration
Indeed. Following that, has reached step 3, and get:
--- Cleaning am-utils
Error: Unable to open port: can't read
Hi Adam - Thanks for the info. Two points:
(1) You can ignore the warning; is will not impact the installation
and/or select of qt4-mac.
(2) Interestingly, I removed that section of code from the Portfile a
ways back, since it is unnecessary. It's odd that it seems to still be
in your
On Wed, Aug 11, 2010 at 11:54, Michael Dickens michae...@macports.org wrote:
(1) You can ignore the warning; is will not impact the installation
and/or select of qt4-mac.
Good to know.
(2) Interestingly, I removed that section of code from the Portfile a
ways back, since it is unnecessary.
On Wed, 11 Aug 2010 11:57 -0500, Adam Mercer r...@macports.org wrote:
$ grep \?honon `port dir qt4-mac`/Portfile
Interesting again. Try this see if either generates the warning:
{{{
sudo port deactivate qt4-mac
sudo port activate qt4-mac
}}}
If not, then it makes me wonder if the Portfile upon
I received the warning too, and imagined that an old version of the Portfile
must have included this code, and that the code wasn't quite right, at least
not in all cases.
On Aug 11, 2010, at 12:01, Michael Dickens wrote:
On Wed, 11 Aug 2010 11:57 -0500, Adam Mercer wrote:
$ grep \?honon
I remember building mono under macports a while ago, and wanting
quartz, no X. I had to painfully uninstall all gnomy things and
rebuild with no_x11. Is there a way now to set it globally
beforehand, so no matter what builds, a quartz variant is build and
no_x11 preserved, if possible? Or, is
On Aug 11, 2010, at 16:46, Alexy Khrabrov wrote:
I remember building mono under macports a while ago, and wanting
quartz, no X. I had to painfully uninstall all gnomy things and
rebuild with no_x11. Is there a way now to set it globally
beforehand, so no matter what builds, a quartz variant
Yep ... Here is what I have in mine. Because I know what each of
these variants do, I know that something I build and use regularly
requires features provided by one of them.
# variants.conf
-ipv6 +no_x11 -x11 +quartz -x11_xcb +gvfs +python26 +help_browser
+no_gcc43 -speex +mysql5 +postgresql84
On Aug 11, 2010, at 10:17, Alexy Khrabrov wrote:
(Perhaps a link from reinstall MacPorts to the latest
release would be better noticeable! :)
Ok, I made this change.
The script helps you install a set of ports that you had installed before,
as recorded by the command port installed
11 matches
Mail list logo
