Hello everyone,
I'm rather new to the MacPorts project and still not too sure about efficient
troubleshooting in that environment. So I thought I'd ask about the following
error first before reporting a bug:
--- Building qt4-mac
Error: Target org.macports.build returned: shell command cd
On Dec 11, 2009, at 04:56, Jürgen Starek wrote:
I'm rather new to the MacPorts project and still not too sure about efficient
troubleshooting in that environment. So I thought I'd ask about the following
error first before reporting a bug:
--- Building qt4-mac
Error: Target
Am 11.12.2009 um 14:19 schrieb Jochen Küpper:
On 11.12.2009, at 12:16, Ryan Schmidt wrote:
There are also many other bugs reported against qt4-mac in our issue
tracker, and it doesn't build for me on my systems either. If you can help
figure out why that is and what we can do about it,
All,
Right now, Nokia has Qt to version 4.6.0, which is a stable release. MacPorts
has this reflected in qt4-mac-devel, but not in qt4-mac. Should the current
qt4-mac become qt4-mac-45, and the current qt4-mac-devel become qt4-mac? It's
just a thought, and qt4-mac-devel, at least on my Snow
On Dec 11, 2009, at 4:16 AM, Ryan Schmidt wrote:
On Dec 11, 2009, at 04:56, Jürgen Starek wrote:
I'm rather new to the MacPorts project and still not too sure about
efficient troubleshooting in that environment. So I thought I'd ask about
the following error first before reporting a bug:
On Dec 11, 2009, at 10:01, Anthony Michael Agelastos wrote:
Right now, Nokia has Qt to version 4.6.0, which is a stable release. MacPorts
has this reflected in qt4-mac-devel, but not in qt4-mac. Should the current
qt4-mac become qt4-mac-45, and the current qt4-mac-devel become qt4-mac? It's
On Dec 11, 2009, at 11:19, Frank Schima wrote:
On Dec 11, 2009, at 4:16 AM, Ryan Schmidt wrote:
Sounds like this ticket:
http://trac.macports.org/ticket/20199
That ticket describes two qt4-mac conflicts, one with libevent which has
been resolved, and another which hasn't. The notes
It's the first time I use Macport, I tried to install Gimp and here is the
message I received:
macbook-de-gabriel-baril:~ gabrielbaril$ sudo port install gimp
--- Computing dependencies for gimpError: Unable to execute port: can't
read build.cmd: Failed to locate 'make' in path:
On 2009-12-12 09:31 , Gabriel Baril wrote:
It's the first time I use Macport, I tried to install Gimp and here is
the message I received:
macbook-de-gabriel-baril:~ gabrielbaril$ sudo port install gimp
--- Computing dependencies for gimpError: Unable to execute port:
can't read
Xcode
Thanks!
Gabriel
2009/12/11 Joshua Root j...@macports.org
On 2009-12-12 09:31 , Gabriel Baril wrote:
It's the first time I use Macport, I tried to install Gimp and here is
the message I received:
macbook-de-gabriel-baril:~ gabrielbaril$ sudo port install gimp
--- Computing
Hello,
Trying to install qt4-x11 on a PPC platform running MacOS 10.5.8
resulted in the following error:
--- Building qt4-x11
Error: Target org.macports.build returned: shell command cd /opt/
local/var/macports/build/
_opt_local_var_macports_sources_rsync
On Dec 11, 2009, at 23:39, Frank J. R. Hanstick wrote:
Trying to install qt4-x11 on a PPC platform running MacOS 10.5.8
resulted in the following error:
bindings/js/JSPluginCustom.cpp: In static member function 'static bool
WebCore::JSPlugin::canGetItemsForName(KJS::ExecState*,
Hello,
This installation is not an imperative, so I can wait.
On Dec 11, 2009, at 9:58 PM, Ryan Schmidt wrote:
On Dec 11, 2009, at 23:39, Frank J. R. Hanstick wrote:
Trying to install qt4-x11 on a PPC platform running MacOS 10.5.8
resulted in the following error:
Hello,
In stalling ProjectCenter, the following warning occurred:
Warning: violation by /opt/local/GNUstep
Warning: ProjectCenter violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is intended),
it will be an error in future releases!
On Dec 12, 2009, at 00:19, Frank J. R. Hanstick wrote:
In stalling ProjectCenter, the following warning occurred:
Warning: violation by /opt/local/GNUstep
Warning: ProjectCenter violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior (if it is
Hello,
Not my night. Attempting to install gorm resulted in the following
error:
Error: Target org.macports.build returned: shell command cd /opt/
local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_gnustep_gorm/work/gorm-1.2.1 /usr/bin/
gnumake
On Dec 12, 2009, at 00:26, Ryan Schmidt wrote:
On Dec 12, 2009, at 00:19, Frank J. R. Hanstick wrote:
The following error occurred for ProjectManager:
We don't appear to have any tickets filed for ProjectManager. Would you
please file one?
However, note that nobody is maintaining
Hi! I see that the rails port is on v2.2.2, where the official rails is
on v2.3.5. My original version on Snow Leopard is 2.3.4. Do you know if
there's any particular reason for not upgrading the available port?
BYe!
___
macports-users mailing list
18 matches
Mail list logo
