On Thu, Jul 28, 2011 at 03:07:00PM -0500, Ryan Schmidt wrote:
> That sounds like qt3 is not properly observing the destroot. I'm guessing it
> should be running ranlib on the copy in the destroot, not an existing copy
> already in prefix.
No, it appears to be intentional. It's doing a ranlib on
On Jul 28, 2011, at 14:34, Dan Ports wrote:
> On Thu, Jul 28, 2011 at 08:57:09AM -0500, Rodolfo Aramayo wrote:
>> The original problem was related to file permissions?? I was unable to
>> solve this problem any other way, like changing permissions on the
>> files that could not be written to and
On Thu, Jul 28, 2011 at 08:57:09AM -0500, Rodolfo Aramayo wrote:
> The original problem was related to file permissions?? I was unable to
> solve this problem any other way, like changing permissions on the
> files that could not be written to and or running selfupdate and port
> upgrade outdated
FYI
I was able to solve the problem I was having updating qt3 by doing the
following:
uninstalling the active (outdated) installation of qt3
installing the up-to-date version of qt3
The original problem was related to file permissions?? I was unable to
solve this problem any other way, like cha
People,
After upgrading from Mac Ports base 1.9.2 to the latest Mac Ports base 2.0
and running the 'port upgrade outdated' I got the following error:
Error: Target org.macports.build returned: shell command failed (see
log for details)
Log for qt3 is at:
/opt/local/var/macports/logs/_opt_local_va
