* Bradley Giesbrecht b...@pixilla.com [18.01.09 04:58]wrote:
On Jan 17, 2009, at 7:33 PM, Mark wrote:
John R. Carter, Sr. wrote:
On a Mac:
$ sudo nano -w `which startx`
(Use back quotes in the above.)
Change the first occurrence of defaultserverargs to read as follows:
I am trying to install Apache 2.0 on a Power Mac G5 running Leopard
10.5.4
I get the folowing error
--- Fetching apache2
--- Attempting to fetch httpd-2.2.11.tar.bz2 from
http://www.ibiblio.org/pub/mirrors/apache/httpd
--- Verifying checksum(s) for apache2
--- Extracting apache2
Error:
On Sun, Jan 18, 2009 at 05:13:23PM -0400, Jason Hirsh said:
I am trying to install Apache 2.0 on a Power Mac G5 running Leopard
10.5.4
I get the folowing error
--- Fetching apache2
--- Attempting to fetch httpd-2.2.11.tar.bz2 from
http://www.ibiblio.org/pub/mirrors/apache/httpd
---
Begin forwarded message:
From: Jason Hirsh hir...@att.net
Date: January 18, 2009 5:59:06 PM GMT-04:00
To: Bryan Blackburn b...@macports.org
Subject: Re: error apache2 from macports 1.70
On Jan 18, 2009, at 5:29 PM, Bryan Blackburn wrote:
On Sun, Jan 18, 2009 at 05:13:23PM -0400, Jason
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
outdated' and it failed after a while with errors like:
sudo port upgrade outdated
--- Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3
Here's what I got when I installed Apache2.0 on my Mac Pro running
10.5.6 (being a dodo, I am wondering why my port command fetched from http://distfiles.macports.org/apache2
rather than from http://www.ibiblio.org/pub/mirrors/apache/httpd):
t...@cotopaxi:~$ sudo port install apache2
Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
outdated' and it failed after a while with errors like:
sudo port upgrade outdated
--- Deactivating gettext @0.17_3
Error:
Hello, I am back on this again. Had to get a new computer. I
remember I used to do `edit port ASSP` and it would open a file, that
I had done some work on. I have MacPorts installed on my new machine
now, but how do I get the old edited port over to my new machine, so I
can work where I
On Sun, Jan 18, 2009 at 6:46 PM, Rainer Müller rai...@macports.org wrote:
Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
outdated' and it failed after a while with errors like:
sudo
On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
[...]
Ok ther still seems to be an issue with that configure directory not
being created
I took a llok and I have nothing in the tree under work in the path
shown in the error
[Bluefish:/opt/local] jason% sudo port -d extract
On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a 'sudo port upgrade
outdated' and it failed after a while with errors like:
sudo port
On Jan 18, 2009, at 3:47 PM, Scott Haneda wrote:
Hello, I am back on this again. Had to get a new computer. I
remember I used to do `edit port ASSP` and it would open a file,
that I had done some work on. I have MacPorts installed on my new
machine now, but how do I get the old edited
Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port
outdated ...
iMac:~ mark$ sudo port outdated
The following installed ports are outdated:
vim7.2.077_0 7.2.077_1
iMac:~ mark$ sudo port upgrade outdated
--- Fetching vim
--- Verifying
On Mon, Jan 19, 2009 at 12:06:38AM +, Mark Hattam said:
[...]
iMac:~ mark$ sudo port upgrade outdated
--- Fetching vim
--- Verifying checksum(s) for vim
--- Extracting vim
--- Applying patches to vim
--- Configuring vim
--- Building vim
[...]
Undefined symbols:
__Xsetlocale,
On 19 Jan 2009, at 00:20, Bryan Blackburn wrote:
On Mon, Jan 19, 2009 at 12:06:38AM +, Mark Hattam said:
[...]
iMac:~ mark$ sudo port upgrade outdated
--- Fetching vim
--- Verifying checksum(s) for vim
--- Extracting vim
--- Applying patches to vim
--- Configuring vim
--- Building
Begin forwarded message:
From: Adam Dershowitz
Date: 19 January 2009 00:28:44 GMT
To: Mark Hattam m...@dxradio.demon.co.uk
Subject: Re: upgrading VIM errors
On Jan 18, 2009, at 4:06 PM, Mark Hattam wrote:
Did a selfupdate on Macports 1.7 running on OSX 10.5.6, then a port
outdated ...
Doctor Who wrote:
On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn b...@macports.org wrote:
On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo port outdated' and had
5 or 6 ports that needed updating. I then ran a
I get exactly the same error output; however, I'm upgrading (or trying
to) from vim @7.2.021_0 (active). Also lots of xorg upgrades that
succeed and a python that doesn't. Frustrating! openssl and vim are
the only active ports that are outdated and won't upgrade on my system.
Tim
On Jan
On Jan 18, 2009, at 17:54, Bryan Blackburn wrote:
On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
sh: /opt/local/bin/bzip2: Bad CPU type in executable
Was this MacPorts install copied over from a different architecture
(eg from
a PowerPC to Intel)?
I would have thought
On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:
Along the way it also installed python26! It looks like this is
because it installed xorg-xcb-proto @1.3_0+python26. I am not sure
if this will work or not because I have not, and was not planning
to run: sudo python_select python26.
On Sun, Jan 18, 2009 at 8:10 PM, Rainer Müller rai...@macports.org wrote:
Doctor Who wrote:
On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn b...@macports.org wrote:
On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
Doctor Who wrote:
I have MacPorts 1.7.0 installed. I did a 'sudo
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover from this. I cannot
even list files on my file system in Terminal.app (as evidenced by
the
attempt at the ls command above).
It is trying to use /opt/local/bin/ls which is
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover from this. I cannot
even list files on my file system in Terminal.app (as evidenced by the
attempt at
On Jan 18, 2009, at 20:18, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover from this. I cannot
even list files on my file system in Terminal.app (as
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 18, 2009, at 20:18, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 19:10, Rainer Müller wrote:
Doctor Who wrote:
Well, I hope there is some way to fix/recover
On Jan 18, 2009, at 20:39, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 20:18, Doctor Who wrote:
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more. Would you please outline the steps I should
take one
On Jan 18, 2009, at 20:53, Doctor Who wrote:
Also, does removing coreutils cause a problems with paths for tools
like 'ls' now? How do I fix the paths so I can use the tools again?
tbook:~ who$ ls
-bash: /opt/local/bin/ls: No such file or directory
Since /opt/local/bin/ls doesn't exist,
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 18, 2009, at 20:39, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 20:18, Doctor Who wrote:
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
On Jan 18, 2009, at 20:50, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt wrote:
Try:
sudo port install gettext
Thanks...that worked.
Great!
Should I now try to update with 'sudo port upgrade outdated'?
Sure, go ahead. I know there have been a lot of
On Sun, Jan 18, 2009 at 9:57 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 18, 2009, at 20:53, Doctor Who wrote:
Also, does removing coreutils cause a problems with paths for tools
like 'ls' now? How do I fix the paths so I can use the tools again?
tbook:~ who$ ls
-bash:
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Jan 18, 2009, at 20:39, Doctor Who wrote:
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:
On Jan 18, 2009, at 20:18, Doctor Who wrote:
Not to be a pain, but I'm pretty new to MacPorts and I don't want to
On Jan 18, 2009, at 7:54 PM, Bryan Blackburn wrote:
On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
[...]
Ok ther still seems to be an issue with that configure directory not
being created
I took a llok and I have nothing in the tree under work in the path
shown in the error
On Jan 18, 2009, at 21:23, Jason Hirsh wrote:
On Jan 18, 2009, at 7:54 PM, Bryan Blackburn wrote:
On Sun, Jan 18, 2009 at 07:12:45PM -0400, Jason Hirsh said:
sh: /opt/local/bin/bzip2: Bad CPU type in executable
Was this MacPorts install copied over from a different
architecture (eg from
On Sun, Jan 18, 2009 at 08:01:57PM -0600, Ryan Schmidt said:
[...]
We should also consider forcing MacPorts base to always use vital
utilities like ln and touch via their absolute paths in /bin or /usr/bin
and not allow a MacPorts version to interfere. We might consider the same
for tar,
On Sun, Jan 18, 2009 at 07:49:16PM -0600, Ryan Schmidt said:
On Jan 18, 2009, at 18:51, Adam Dershowitz wrote:
Along the way it also installed python26! It looks like this is
because it installed xorg-xcb-proto @1.3_0+python26. I am not sure if
this will work or not because I have not,
Could someone help me interpret this error? I tried installing
Gnome-Control-Center, and early it bombed on this:
--- Building nspr
Error: Target org.macports.build returned: shell command cd
36 matches
Mail list logo
