Re: GnuCash Default Font

2009-01-18 Thread Olaf Foellinger
* 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:

 defaultserverargs=”-dpi 96”

 You will have to restart X11 if it is already active.

 All this does is ensure that the X11 display resolution is the same  
 as the default system font.

 On Jan 16, 2009, at 11:59 PM, Mark wrote:

 (I just posted on a related GnuCash topic, so please forgive the
 repetition of my system details.) I have just finished a complete  
 fresh
 install of Macports, followed by a native Quartz, minimal  
 (+without_hbci
 +without_ofx +without_quotes) install of GnuCash on MBP 10.5.6.

 I can't figure out how to change the default font for the program.  
 When
 I used to run GnuCash under X11 (Fink package GnuCash2), I had --  
 and
 still have -- a file in my home directory named .gtkrc-2.0 which
 contains a single line: gtk-font-name = Luxi Mono 16 -- and that  
 used
 to cause GnuCash to use that font in all its windows.

 But not anymore! Apparently native Quartz GnuCash installed via  
 MacPorts
 isn't consulting ~/gtkrc-2.0, or is somehow overriding it?  
 Anything I
 can do to get my big beautiful font back?

 How do you build the Quartz version?
 I see no Quartz variant.


Sorry, only in German:
http://blog.foellinger.de/2009/01/04/gnucash-fur-mac-os-x-mit-quartz-oberflache-stark-vereinfacht/

Gruß Olaf
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


error apache2 from macports 1.70

2009-01-18 Thread Jason Hirsh
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: reinplace: couldn't read file /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/configure:  
no such file or directory

Error: Target org.macports.extract returned: reinplace sed(1) failed
Error: Status 1 encountered during processing.


It would seem there is an issue with the what I fetched??



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: error apache2 from macports 1.70

2009-01-18 Thread Bryan Blackburn
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
 ---  Verifying checksum(s) for apache2
 ---  Extracting apache2
 Error: reinplace: couldn't read file /opt/local/var/macports/build/ 
 _opt_local_var_macports_sources_rsync 
 .macports.org_release_ports_www_apache2/work/httpd-2.2.11/configure: no 
 such file or directory
 Error: Target org.macports.extract returned: reinplace sed(1) failed
 Error: Status 1 encountered during processing.


 It would seem there is an issue with the what I fetched??

If the file downloaded wasn't right, it would have failed during the
checksum, so the download should be okay.  Try running

$ sudo port clean --work apache2
$ sudo port -d extract apache2

and see if that gives us some more information on what's going on.  FWIW, I
have that version of apache2 installed here without such issues.

Bryan

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Fwd: error apache2 from macports 1.70

2009-01-18 Thread Jason Hirsh



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 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
---  Verifying checksum(s) for apache2
---  Extracting apache2
Error: reinplace: couldn't read file /opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
configure: no

such file or directory
Error: Target org.macports.extract returned: reinplace sed(1) failed
Error: Status 1 encountered during processing.


It would seem there is an issue with the what I fetched??


If the file downloaded wasn't right, it would have failed during the
checksum, so the download should be okay.  Try running

$ sudo port clean --work apache2
$ sudo port -d extract apache2

and see if that gives us some more information on what's going on.   
FWIW, I

have that version of apache2 installed here without such issues.

Bryan


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 apache2
DEBUG: Found port in 
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/apache2
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/www/apache2

DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing  
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- 
existing procedure. Target override will not be provided

DEBUG: adding the default universal variant
DEBUG: Requested variant powerpc is not provided by port apache2.
DEBUG: Requested variant macosx is not provided by port apache2.
DEBUG: Executing variant darwin provides darwin
DEBUG: Executing variant darwin_9 provides darwin_9
DEBUG: Executing org.macports.main (apache2)
---  Fetching apache2
DEBUG: Executing org.macports.fetch (apache2)
---  Verifying checksum(s) for apache2
DEBUG: Executing org.macports.checksum (apache2)
---  Checksumming httpd-2.2.11.tar.bz2
DEBUG: Correct (md5) checksum for httpd-2.2.11.tar.bz2
DEBUG: Correct (sha1) checksum for httpd-2.2.11.tar.bz2
DEBUG: Correct (rmd160) checksum for httpd-2.2.11.tar.bz2
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
---  Extracting apache2
DEBUG: Executing org.macports.extract (apache2)
---  Extracting httpd-2.2.11.tar.bz2
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/apache2/httpd-2.2.11.tar.bz2

DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_apache2/work  /opt/local/bin/ 
bzip2 -dc /opt/local/var/macports/distfiles/apache2/ 
httpd-2.2.11.tar.bz2 | /usr/bin/gnutar --no-same-owner -xf -'

sh: /opt/local/bin/bzip2: Bad CPU type in executable
DEBUG: Executing proc-post-org.macports.extract-extract-0
DEBUG: couldn't read file /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
configure: no such file or directory

   while executing
exec /usr/bin/sed {s|-export-symbols-regex ssl_module||g}  /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_p...

   (eval body line 1)
   invoked from within
eval exec $cmdline
Error: reinplace: couldn't read file /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
configure: no such file or directory

Error: Target org.macports.extract returned: reinplace sed(1) failed
Warning: the following items did not execute (for apache2):  
org.macports.extract

Error: Status 1 encountered during processing.


Its probably me... but can't figure how I screwed up




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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 failed:
---  Activating perl5.8 @5.8.9_2
Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/touch
  Reason: image not found
---  Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3 failed:
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
---  Deactivating gettext @0.17_3
Error: Deactivating gettext 0.17_3 failed:
---  Activating perl5.8 @5.8.9_2
Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/touch
  Reason: image not found
Error: Unable to exec port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found
Error: Unable to upgrade port: dyld: Library not loaded:
/opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ln
  Reason: image not found

What is the issue here and how can I fix?  Any command I now run from
Terminal.app gives an error such as:

$ ls
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/ls
  Reason: image not found
Trace/BPT trap

$ uptime
dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
  Referenced from: /opt/local/bin/uptime
  Reason: image not found
Trace/BPT trap

Thanks for any help!
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: error apache2 from macports 1.70

2009-01-18 Thread Timothy Goins
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
Password:
---  Fetching apr
---  Attempting to fetch apr-1.3.3.tar.bz2 from 
http://distfiles.macports.org/apr
---  Verifying checksum(s) for apr
---  Extracting apr
---  Configuring apr
---  Building apr
---  Staging apr into destroot
---  Installing apr @1.3.3_1
---  Activating apr @1.3.3_1
---  Cleaning apr
---  Fetching apr-util
---  Attempting to fetch apr-util-1.3.4.tar.bz2 from 
http://distfiles.macports.org/apr-util
---  Verifying checksum(s) for apr-util
---  Extracting apr-util
---  Configuring apr-util
---  Building apr-util
---  Staging apr-util into destroot
---  Installing apr-util @1.3.4_1
---  Activating apr-util @1.3.4_1
---  Cleaning apr-util
---  Fetching apache2
---  Attempting to fetch httpd-2.2.11.tar.bz2 from 
http://distfiles.macports.org/apache2
---  Verifying checksum(s) for apache2
---  Extracting apache2
---  Applying patches to apache2
---  Configuring apache2
---  Building apache2
---  Staging apache2 into destroot
---  Creating launchd control script
###
# A startup item has been generated that will aid in
# starting apache2 with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/ 
org.macports.apache2.plist

###
Warning: apache2 requests to install files outside the common  
directory structure!

---  Installing apache2 @2.2.11_0+darwin_9
---  Activating apache2 @2.2.11_0+darwin_9
---  Cleaning apache2

Tim

On Jan 18, 2009, at 4:12 PM, Jason Hirsh wrote:




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 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
---  Verifying checksum(s) for apache2
---  Extracting apache2
Error: reinplace: couldn't read file /opt/local/var/macports/ 
build/

_opt_local_var_macports_sources_rsync
.macports.org_release_ports_www_apache2/work/httpd-2.2.11/ 
configure: no

such file or directory
Error: Target org.macports.extract returned: reinplace sed(1)  
failed

Error: Status 1 encountered during processing.


It would seem there is an issue with the what I fetched??


If the file downloaded wasn't right, it would have failed during the
checksum, so the download should be okay.  Try running

$ sudo port clean --work apache2
$ sudo port -d extract apache2

and see if that gives us some more information on what's going  
on.  FWIW, I

have that version of apache2 installed here without such issues.

Bryan


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 apache2
DEBUG: Found port in 
file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/www/apache2
DEBUG: Changing to port directory: /opt/local/var/macports/sources/ 
rsync.macports.org/release/ports/www/apache2

DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing  
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a  
pre-existing procedure. Target override will not be provided

DEBUG: adding the default universal variant
DEBUG: Requested variant powerpc is not provided by port apache2.
DEBUG: Requested variant macosx is not provided by port apache2.
DEBUG: Executing variant darwin provides darwin
DEBUG: Executing variant darwin_9 provides darwin_9
DEBUG: Executing org.macports.main (apache2)
---  Fetching apache2
DEBUG: Executing org.macports.fetch (apache2)
---  Verifying checksum(s) for apache2
DEBUG: Executing org.macports.checksum (apache2)
---  Checksumming httpd-2.2.11.tar.bz2
DEBUG: Correct (md5) checksum for httpd-2.2.11.tar.bz2
DEBUG: Correct (sha1) checksum for httpd-2.2.11.tar.bz2
DEBUG: Correct (rmd160) checksum for httpd-2.2.11.tar.bz2
DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
---  Extracting apache2
DEBUG: Executing org.macports.extract (apache2)
---  Extracting httpd-2.2.11.tar.bz2
DEBUG: setting option extract.args to /opt/local/var/macports/ 
distfiles/apache2/httpd-2.2.11.tar.bz2

DEBUG: Environment: 

Re: Error after trying to upgrade installed

2009-01-18 Thread Rainer Müller
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: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found

Looks like you have coreutils +with_default_names installed, but you
broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
some reason it seems not to be active.

Try to fix it by
  sudo port activate gettext

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: ASSP out of date

2009-01-18 Thread Scott Haneda
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 left off?


I also want to rename it, so I can `edit port ASSP-new` or whatever,  
and not conflict with the current port for the time being.


Thank you.
--
Scott

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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 port upgrade outdated
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found

 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.

 Try to fix it by
  sudo port activate gettext

 Rainer


sudo port activate gettext
Password:
---  Activating gettext
Error: port activate failed: Image error: gettext @0.17_3 is already active.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Fwd: error apache2 from macports 1.70

2009-01-18 Thread Bryan Blackburn
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 apache2
[...]
 DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
 ---  Extracting apache2
 DEBUG: Executing org.macports.extract (apache2)
 ---  Extracting httpd-2.2.11.tar.bz2
 DEBUG: setting option extract.args to /opt/local/var/macports/ 
 distfiles/apache2/httpd-2.2.11.tar.bz2
 DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
 DEBUG: Assembled command: 'cd /opt/local/var/macports/build/ 
 _opt_local_var_macports_sources_rsync 
 .macports.org_release_ports_www_apache2/work  /opt/local/bin/bzip2 
 -dc /opt/local/var/macports/distfiles/apache2/httpd-2.2.11.tar.bz2 | 
 /usr/bin/gnutar --no-same-owner -xf -'
 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)?

Odd though that it continued on after that as it should have failed at this
point instead of continuing.

Bryan

[...]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Bryan Blackburn
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 upgrade outdated
  ---  Deactivating gettext @0.17_3
  Error: Deactivating gettext 0.17_3 failed:
  ---  Activating perl5.8 @5.8.9_2
[...]
 
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.

Somebody reported this same issue last night on IRC, where it fails to
deactivate gettext but not giving any actual error message.  It ends up
removing all files from ${prefix} but then fails to set the port as not
active, and ends up confused.

You can't force-activate as it complains that it is already active, and any
further deactivate results in the same output above.

Unfortunately I didn't see any way to deal with this or what the cause was,
and was hoping it was a one-off issue.  This is two now this weekend, so
maybe something strange is going on in base...

Bryan


 
 Try to fix it by
   sudo port activate gettext
 
 Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: ASSP out of date

2009-01-18 Thread Bradley Giesbrecht

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 port over to my new  
machine, so I can work where I left off?


There are so many ways to get a file from one machine to another. You  
must mean something else.


If it's a Mac you want to copy the file from on Leopard you should be  
able to see the machine in a Finder window in the sidebar under  
SHARED.
Just click the computer name and Connect As and type in your  
credentials when prompted.

Then find your Portfile and copy it over.

If you are just looking for your port file.

port dir port name


I also want to rename it, so I can `edit port ASSP-new` or whatever,  
and not conflict with the current port for the time being.



This is what I do.

http://guide.macports.org/#development.local-repositories
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


upgrading VIM errors

2009-01-18 Thread Mark Hattam
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 checksum(s) for vim
---  Extracting vim
---  Applying patches to vim
---  Configuring vim
---  Building vim
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72  make all   
returned error 2
Command output: /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/ 
opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 -o objects/quickfix.o  
quickfix.c
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1 -o objects/regexp.o regexp.c


[lots more of these FORTIFY_SOURCE lines ending with ...]

/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/include  
-DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/FlatCarbon  -O - 
D_FORTIFY_SOURCE=1 version.c -o objects/version.o
  /usr/bin/gcc-4.0   -L/opt/local/lib 	-o vim objects/buffer.o  
objects/charset.o objects/diff.o objects/digraph.o objects/edit.o  
objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ex_docmd.o  
objects/ex_eval.o objects/ex_getln.o objects/fileio.o objects/fold.o  
objects/getchar.o objects/hardcopy.o objects/hashtab.o  objects/ 
if_cscope.o objects/if_xcmdsrv.o objects/main.o objects/mark.o objects/ 
memfile.o objects/memline.o objects/menu.o objects/message.o objects/ 
misc1.o objects/misc2.o objects/move.o objects/mbyte.o objects/ 
normal.o objects/ops.o objects/option.o objects/os_unix.o objects/ 
pathdef.o objects/popupmnu.o objects/quickfix.o objects/regexp.o  
objects/screen.o objects/search.o objects/spell.o objects/syntax.o   
objects/tag.o objects/term.o objects/ui.o objects/undo.o objects/ 
window.o   objects/os_macosx.o objects/os_mac_conv.o  objects/ 
netbeans.o  objects/version.o   -lm  -lncurses -liconv -framework  
Carbon

Undefined symbols:
  __Xsetlocale, referenced from:
  _get_locale_val in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _ex_language in ex_cmds2.o
  _main in main.o
  _main in main.o
  _enc_locale in mbyte.o
  _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Previous updates to VIM have worked OK.

iMac:~ mark$ sudo port installed | grep vim
  vim @7.2.077_0 (active)


Previously today, gd2 was updated
---  Deactivating gd2 @2.0.35_2
---  Installing gd2 @2.0.35_3

whose upgrade process downloaded, built, installed and activated 70  
(seventy) xorg- packages ...



Mark

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Bryan Blackburn
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, referenced from:

Looks like #17606:

http://trac.macports.org/ticket/17606

Bryan

[...]

 Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Mark Hattam


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 vim

[...]

Undefined symbols:
 __Xsetlocale, referenced from:


Looks like #17606:

http://trac.macports.org/ticket/17606

Bryan

[...]


Mark



The previous version upgrade built without a problem ... so this seems  
a newer problem - or a problem that didn't affect 7.2.077_0


vim7.2.077_0  7.2.077_1

Today update seems to have been forced as a result of the X11  
changes detailed in the email

subject: [45603] trunk/dports
x11 dependent ports: Force port: based X11 dependencies

Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Fwd: upgrading VIM errors

2009-01-18 Thread Mark Hattam


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 ...


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



Previously today, gd2 was updated
---  Deactivating gd2 @2.0.35_2
---  Installing gd2 @2.0.35_3

whose upgrade process downloaded, built, installed and activated 70  
(seventy) xorg- packages ...



Mark


I also did an upgrade that is still going...with a whole bunch of  
xorg packages (I didn't count, like you did).  I think that some of  
these got installed also because of a change in xrender.  So some  
got installed as that was upgrading.
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.





I didn't count ... computers are good at that :-)

iMac:~ mark$ sudo port installed | grep xorg -c
70


Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Rainer Müller
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 '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 failed:
 ---  Activating perl5.8 @5.8.9_2
 [...]
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.
 Somebody reported this same issue last night on IRC, where it fails to
 deactivate gettext but not giving any actual error message.  It ends up
 removing all files from ${prefix} but then fails to set the port as not
 active, and ends up confused.

 You can't force-activate as it complains that it is already active, and any
 further deactivate results in the same output above.

 Unfortunately I didn't see any way to deal with this or what the cause was,
 and was hoping it was a one-off issue.  This is two now this weekend, so
 maybe something strange is going on in base...

 Bryan


 
 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 broken. You can still use
/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.

Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
with receipt files, so it was unable to operate with the broken
coreutils in PATH.

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Timothy Goins
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 18, 2009, at 5:06 PM, Mark Hattam wrote:

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 checksum(s) for vim
---  Extracting vim
---  Applying patches to vim
---  Configuring vim
---  Building vim
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_editors_vim/work/vim72  make all   
returned error 2
Command output: /usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/ 
opt/local/include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/ 
Headers/FlatCarbon  -O -D_FORTIFY_SOURCE=1 -o objects/ 
quickfix.o quickfix.c
/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 -o objects/regexp.o  
regexp.c


[lots more of these FORTIFY_SOURCE lines ending with ...]

/usr/bin/gcc-4.0 -c -I. -Iproto -DHAVE_CONFIG_H   -I/opt/local/ 
include -DMACOS_X_UNIX -no-cpp-precomp -I/Developer/Headers/ 
FlatCarbon  -O -D_FORTIFY_SOURCE=1 version.c -o objects/ 
version.o
 /usr/bin/gcc-4.0   -L/opt/local/lib 	-o vim objects/buffer.o  
objects/charset.o objects/diff.o objects/digraph.o objects/edit.o  
objects/eval.o objects/ex_cmds.o objects/ex_cmds2.o objects/ 
ex_docmd.o objects/ex_eval.o objects/ex_getln.o objects/fileio.o  
objects/fold.o objects/getchar.o objects/hardcopy.o objects/ 
hashtab.o  objects/if_cscope.o objects/if_xcmdsrv.o objects/main.o  
objects/mark.o objects/memfile.o objects/memline.o objects/menu.o  
objects/message.o objects/misc1.o objects/misc2.o objects/move.o  
objects/mbyte.o objects/normal.o objects/ops.o objects/option.o  
objects/os_unix.o objects/pathdef.o objects/popupmnu.o objects/ 
quickfix.o objects/regexp.o objects/screen.o objects/search.o  
objects/spell.o objects/syntax.o  objects/tag.o objects/term.o  
objects/ui.o objects/undo.o objects/window.o   objects/ 
os_macosx.o objects/os_mac_conv.o  objects/netbeans.o  objects/ 
version.o   -lm  -lncurses -liconv -framework Carbon

Undefined symbols:
 __Xsetlocale, referenced from:
 _get_locale_val in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _ex_language in ex_cmds2.o
 _main in main.o
 _main in main.o
 _enc_locale in mbyte.o
 _mac_lang_init in os_mac_conv.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[1]: *** [vim] Error 1
make: *** [all] Error 2

Error: Unable to upgrade port: 1


Previous updates to VIM have worked OK.

iMac:~ mark$ sudo port installed | grep vim
 vim @7.2.077_0 (active)


Previously today, gd2 was updated
---  Deactivating gd2 @2.0.35_2
---  Installing gd2 @2.0.35_3

whose upgrade process downloaded, built, installed and activated 70  
(seventy) xorg- packages ...



Mark

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: error apache2 from macports 1.70

2009-01-18 Thread Ryan Schmidt


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 that a PowerPC binary on an Intel Mac would work  
correctly through Rosetta.



Odd though that it continued on after that as it should have failed  
at this

point instead of continuing.


No, unfortunately, that is a known problem that it does not error out  
at this point if the decompression program is faulty. We need to fix  
that.


http://trac.macports.org/ticket/16223

I have thought that it would be nice to separate extraction from  
decompression instead of putting them in a single phase. Besides  
being cleaner and fixing the above issue, it would enable us to  
handle formats that cannot be decompressed and extracted in a single  
step, such as .dmg.zip. Unfortunately, so many ports have hacked the  
arguments of the existing extract phase that changing it at all at  
this point may be problematic.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Ryan Schmidt


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.


It is not necessary to run sudo python_select python26 unless you  
want to be able to type python and have it run python26. Any port  
that depends on python26 (or any other python) should function  
correctly without using python_select. Perhaps the message printed by  
the python ports could be worded differently, so that it is not  
implied that running python_select is necessary.



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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 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 failed:
 ---  Activating perl5.8 @5.8.9_2
 [...]
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.
 Somebody reported this same issue last night on IRC, where it fails to
 deactivate gettext but not giving any actual error message.  It ends up
 removing all files from ${prefix} but then fails to set the port as not
 active, and ends up confused.

 You can't force-activate as it complains that it is already active, and any
 further deactivate results in the same output above.

 Unfortunately I didn't see any way to deal with this or what the cause was,
 and was hoping it was a one-off issue.  This is two now this weekend, so
 maybe something strange is going on in base...

 Bryan



 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 broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Rainer


I get this when trying to deactivate:

$ sudo port deactivate gettext
Password:
---  Deactivating gettext
Error: port deactivate failed:
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

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 broken. You can  
still use

/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.


Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
temporarily in the Terminal would allow you to now type ls or  
touch in the Terminal, however:




Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
with receipt files, so it was unable to operate with the broken
coreutils in PATH.


Note that the user's PATH is not used by MacPorts, so this will still  
fail until you also change the PATH that MacPorts uses while running,  
which is set in the variable binpath in the file /opt/local/etc/ 
macports/macports.conf


You could change the binpath so that /bin and /usr/bin precede /opt/ 
local/bin. Then MacPorts will use the system's file manipulation  
utilities (ln, touch, etc.) you will hopefully be able to deactivate  
the old gettext and activate the new one, at which point your  
coreutils versions of ln and touch will work again and you can (and  
should) revert binpath in macports.conf and PATH in .profile  
or .bash_profile to what they were.


Then, you should probably uninstall coreutils +with_default_names  
because it's probably not good to override those default Mac OS X  
utilities.


We could consider removing the +with_default_names capability from  
the coreutils port.


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, gzip, bzip2, etc, to avoid the occasional problem  
with the MacPorts versions of those utilities, e.g. the thread error  
apache2 from macports 1.70 earlier today:


http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
013335.html



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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 the ls command above).

 It is trying to use /opt/local/bin/ls which is broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily in
 the Terminal would allow you to now type ls or touch in the Terminal,
 however:


 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Note that the user's PATH is not used by MacPorts, so this will still fail
 until you also change the PATH that MacPorts uses while running, which is
 set in the variable binpath in the file
 /opt/local/etc/macports/macports.conf

 You could change the binpath so that /bin and /usr/bin precede
 /opt/local/bin. Then MacPorts will use the system's file manipulation
 utilities (ln, touch, etc.) you will hopefully be able to deactivate the old
 gettext and activate the new one, at which point your coreutils versions of
 ln and touch will work again and you can (and should) revert binpath in
 macports.conf and PATH in .profile or .bash_profile to what they were.

 Then, you should probably uninstall coreutils +with_default_names because
 it's probably not good to override those default Mac OS X utilities.

 We could consider removing the +with_default_names capability from the
 coreutils port.

 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, gzip,
 bzip2, etc, to avoid the occasional problem with the MacPorts versions of
 those utilities, e.g. the thread error apache2 from macports 1.70 earlier
 today:

 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html




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 by one to (hopefully) restore my system back to 'normal'?

Thanks!
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

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 evidenced  
by the

attempt at the ls command above).


It is trying to use /opt/local/bin/ls which is broken. You can  
still use

/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
 sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.


Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
temporarily in
the Terminal would allow you to now type ls or touch in the  
Terminal,

however:



Now to fix the gettext issue, please try if this works now:
 sudo port deactivate gettext
 sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to  
work

with receipt files, so it was unable to operate with the broken
coreutils in PATH.


Note that the user's PATH is not used by MacPorts, so this will  
still fail
until you also change the PATH that MacPorts uses while running,  
which is

set in the variable binpath in the file
/opt/local/etc/macports/macports.conf

You could change the binpath so that /bin and /usr/bin precede
/opt/local/bin. Then MacPorts will use the system's file manipulation
utilities (ln, touch, etc.) you will hopefully be able to  
deactivate the old
gettext and activate the new one, at which point your coreutils  
versions of
ln and touch will work again and you can (and should) revert  
binpath in
macports.conf and PATH in .profile or .bash_profile to what they  
were.


Then, you should probably uninstall coreutils +with_default_names  
because

it's probably not good to override those default Mac OS X utilities.

We could consider removing the +with_default_names capability from  
the

coreutils port.

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, gzip,
bzip2, etc, to avoid the occasional problem with the MacPorts  
versions of
those utilities, e.g. the thread error apache2 from macports  
1.70 earlier

today:

http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
013335.html


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 by one to (hopefully) restore my system back to 'normal'?


I'm not certain, as I haven't encountered this problem before.

But my suggestion is exactly as I outlined above.

1. Edit /opt/local/etc/macports/macports.conf and change this line:

#binpath		/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/ 
sbin:/usr/X11R6/bin


Remove the hash at the beginning and change the order so that it reads:

binpath		/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/ 
sbin:/usr/X11R6/bin


2. Deactivate your old gettext:

sudo port deactivate gettext @0.17_3

3. Activate your new gettext:

sudo port activate gettext @0.17_4

4. Uninstall coreutils because it is not a good idea to override the  
default Mac OS X file utilities:


sudo port uninstall coreutils

5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
line back the way it was before, including the order of the paths and  
the hash at the beginning of the line.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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 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 broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily
 in
 the Terminal would allow you to now type ls or touch in the Terminal,
 however:


 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Note that the user's PATH is not used by MacPorts, so this will still
 fail
 until you also change the PATH that MacPorts uses while running, which is
 set in the variable binpath in the file
 /opt/local/etc/macports/macports.conf

 You could change the binpath so that /bin and /usr/bin precede
 /opt/local/bin. Then MacPorts will use the system's file manipulation
 utilities (ln, touch, etc.) you will hopefully be able to deactivate the
 old
 gettext and activate the new one, at which point your coreutils versions
 of
 ln and touch will work again and you can (and should) revert binpath in
 macports.conf and PATH in .profile or .bash_profile to what they were.

 Then, you should probably uninstall coreutils +with_default_names because
 it's probably not good to override those default Mac OS X utilities.

 We could consider removing the +with_default_names capability from the
 coreutils port.

 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,
 gzip,
 bzip2, etc, to avoid the occasional problem with the MacPorts versions of
 those utilities, e.g. the thread error apache2 from macports 1.70
 earlier
 today:


 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html

 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 by one to (hopefully) restore my system back to 'normal'?

 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath
  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath
 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line back
 the way it was before, including the order of the paths and the hash at the
 beginning of the line.





OK, when I get to the point of activating the later version of
gettext, it's not installed:

tbook:~ who$ sudo port deactivate gettext @0.17_3
---  Deactivating gettext @0.17_3
tbook:~ who$ sudo port activate gettext @0.17_4
Error: port activate failed: Registry error: gettext 0.17_4 not
registered as installed.

What should I do at this point to install this version correctly?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt


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 by one to (hopefully) restore my system back to 'normal'?


I meant to say earlier, but don't feel that you're bothering us:  
you've clearly found a problem and we need to first get you out of it  
and then figure out how to not make it affect others. Sorry this  
happened; I know it's not a pleasant experience, especially when  
you're just trying to get used to MacPorts. It's not usually like  
this. :)




I'm not certain, as I haven't encountered this problem before.

But my suggestion is exactly as I outlined above.

1. Edit /opt/local/etc/macports/macports.conf and change this line:

#binpath
 /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/ 
X11R6/bin


Remove the hash at the beginning and change the order so that it  
reads:


binpath
/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/ 
X11R6/bin


2. Deactivate your old gettext:

sudo port deactivate gettext @0.17_3

3. Activate your new gettext:

sudo port activate gettext @0.17_4

4. Uninstall coreutils because it is not a good idea to override  
the default

Mac OS X file utilities:

sudo port uninstall coreutils

5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
line back
the way it was before, including the order of the paths and the  
hash at the

beginning of the line.


OK, when I get to the point of activating the later version of
gettext, it's not installed:

tbook:~ who$ sudo port deactivate gettext @0.17_3
---  Deactivating gettext @0.17_3
tbook:~ who$ sudo port activate gettext @0.17_4
Error: port activate failed: Registry error: gettext 0.17_4 not
registered as installed.

What should I do at this point to install this version correctly?



Try:

sudo port install gettext

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt


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, the shell should now look for  
ls in other paths, and find it in /bin.


You must have it set up differently What does which ls say?  
What does alias | grep ls say?


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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
 mess my system up more.  Would you please outline the steps I should
 take one by one to (hopefully) restore my system back to 'normal'?

 I meant to say earlier, but don't feel that you're bothering us: you've
 clearly found a problem and we need to first get you out of it and then
 figure out how to not make it affect others. Sorry this happened; I know
 it's not a pleasant experience, especially when you're just trying to get
 used to MacPorts. It's not usually like this. :)


 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath

  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath

 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the
 default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
 back
 the way it was before, including the order of the paths and the hash at
 the
 beginning of the line.

 OK, when I get to the point of activating the later version of
 gettext, it's not installed:

 tbook:~ who$ sudo port deactivate gettext @0.17_3
 ---  Deactivating gettext @0.17_3
 tbook:~ who$ sudo port activate gettext @0.17_4
 Error: port activate failed: Registry error: gettext 0.17_4 not
 registered as installed.

 What should I do at this point to install this version correctly?


 Try:

 sudo port install gettext



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
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

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 X11/xorg-related  
changes lately, and I haven't tried them myself yet, so good luck!


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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: /opt/local/bin/ls: No such file or directory

 Since /opt/local/bin/ls doesn't exist, the shell should now look for ls in
 other paths, and find it in /bin.

 You must have it set up differently What does which ls say? What does
 alias | grep ls say?



It's working now, once I started another shell.

Thanks.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
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
 mess my system up more.  Would you please outline the steps I should
 take one by one to (hopefully) restore my system back to 'normal'?

 I meant to say earlier, but don't feel that you're bothering us: you've
 clearly found a problem and we need to first get you out of it and then
 figure out how to not make it affect others. Sorry this happened; I know
 it's not a pleasant experience, especially when you're just trying to get
 used to MacPorts. It's not usually like this. :)


 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath

  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath

 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the
 default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
 back
 the way it was before, including the order of the paths and the hash at
 the
 beginning of the line.

 OK, when I get to the point of activating the later version of
 gettext, it's not installed:

 tbook:~ who$ sudo port deactivate gettext @0.17_3
 ---  Deactivating gettext @0.17_3
 tbook:~ who$ sudo port activate gettext @0.17_4
 Error: port activate failed: Registry error: gettext 0.17_4 not
 registered as installed.

 What should I do at this point to install this version correctly?


 Try:

 sudo port install gettext



Thanks...that worked.  Should I now try to update with 'sudo port
upgrade outdated'?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: error apache2 from macports 1.70

2009-01-18 Thread Jason Hirsh


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

[Bluefish:/opt/local] jason% sudo port -d extract apache2

[...]

DEBUG: setting option extract.cmd to /opt/local/bin/bzip2
---  Extracting apache2
DEBUG: Executing org.macports.extract (apache2)
---  Extracting httpd-2.2.11.tar.bz2
DEBUG: setting option extract.args to /opt/local/var/macports/
distfiles/apache2/httpd-2.2.11.tar.bz2
DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'
DEBUG: Assembled command: 'cd /opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_www_apache2/work  /opt/local/bin/ 
bzip2

-dc /opt/local/var/macports/distfiles/apache2/httpd-2.2.11.tar.bz2 |
/usr/bin/gnutar --no-same-owner -xf -'
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)?

Odd though that it continued on after that as it should have failed  
at this

point instead of continuing.

Bryan



presuming wrong type  howdoI correct

[...]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: error apache2 from macports 1.70

2009-01-18 Thread Ryan Schmidt

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

a PowerPC to Intel)?


presuming wrong type  howdoI correct




sudo port -nf upgrade bzip2

That will cause bzip2 to be rebuilt.

But if you copied this MacPorts installation from another machine,  
it's likely most or all of your other ports are also affected by this  
problem and you should do the same for all of them. But you would  
have to do it in the right order. It may be easier to uninstall all  
ports first, then install again what you need, which will do it in  
the right order for you.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Bryan Blackburn
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, gzip, bzip2, etc, to avoid the occasional problem with the 
 MacPorts versions of those utilities, e.g. the thread error apache2 from 
 macports 1.70 earlier today:

For some tools (eg, rm) which are definitely guaranteed to be
system-installed and acceptable, that makes sense.  For others, there's
#15868:

http://trac.macports.org/ticket/15868

So using the system-installed version (svn in that case) would make things
worse...

Bryan



 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: upgrading VIM errors

2009-01-18 Thread Bryan Blackburn
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, and was not planning to run:  
 sudo python_select python26.

 It is not necessary to run sudo python_select python26 unless you want 
 to be able to type python and have it run python26. Any port that 
 depends on python26 (or any other python) should function correctly 
 without using python_select. Perhaps the message printed by the python 
 ports could be worded differently, so that it is not implied that running 
 python_select is necessary.

There could be some ports which do in fact need a version selected as the
Current version setting for the framework
(${prefix}/Library/Frameworks/Python.framework/Version/Current and the
symlinks in just Python.framework/) are used when linking to it.

Thought I believe it's been suggested before that the first python port
installed should probably be automatically python_select'd...

Bryan

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Error building nspr during Gnome-Control Center install

2009-01-18 Thread Mark
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 
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_nspr/work/nspr-4.7.3/mozilla/nsprpub 
 make all  returned error 2
Command output: /usr/include/mach/processor_info.h:99: error: syntax 
error before 'cpu_type_t'
/usr/include/mach/processor_info.h:104: error: syntax error before '}' 
token

In file included from /usr/include/mach-o/dyld.h:31,
 from prlink.c:85:
/usr/include/mach-o/loader.h:56: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:62: error: syntax error before '}' token
/usr/include/mach-o/loader.h:74: error: syntax error before 'cpu_type_t'
/usr/include/mach-o/loader.h:81: error: syntax error before '}' token
prlink.c: In function 'pr_LoadMachDyldModule':
prlink.c:613: warning: 'NSCreateObjectFileImageFromFile' is deprecated 
(declared at /usr/include/mach-o/dyld.h:145)
prlink.c:615: warning: 'NSLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:161)
prlink.c:621: warning: 'NSDestroyObjectFileImage' is deprecated 
(declared at /usr/include/mach-o/dyld.h:147)
prlink.c:623: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)

prlink.c: In function 'pr_LoadViaDyld':
prlink.c:775: warning: 'NSAddImage' is deprecated (declared at 
/usr/include/mach-o/dyld.h:230)
prlink.c:782: warning: 'NSLinkEditError' is deprecated (declared at 
/usr/include/mach-o/dyld.h:217)

prlink.c: In function 'PR_UnloadLibrary':
prlink.c:1289: warning: 'NSUnLinkModule' is deprecated (declared at 
/usr/include/mach-o/dyld.h:169)
prlink.c:1305: warning: 'CloseConnection' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:382)

prlink.c: In function 'pr_FindSymbolInLib':
prlink.c:1418: warning: 'c2pstrcpy' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/TextUtils.h:578)
prlink.c:1420: warning: 'FindSymbol' is deprecated (declared at 
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CodeFragments.h:401)
prlink.c:1433: warning: 'NSLookupSymbolInImage' is deprecated 
(declared at /usr/include/mach-o/dyld.h:182)
prlink.c:1437: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)
prlink.c:1461: warning: 'NSLookupSymbolInModule' is deprecated 
(declared at /usr/include/mach-o/dyld.h:181)
prlink.c:1463: warning: 'NSAddressOfSymbol' is deprecated (declared at 
/usr/include/mach-o/dyld.h:188)

make[3]: *** [prlink.o] Error 1
make[2]: *** [export] Error 2
make[1]: *** [export] Error 2
make: *** [export] Error 2

Error: The following dependencies failed to build: 
evolution-data-server nspr nss sqlite3 gnome-desktop gnome-themes 
gtk-engines2 py25-gnome py25-gtk py25-cairo py25-numpy fftw-3 
py25-nose py25-setuptools py25-zlib py25-gobject py25-orbit 
gnome-menus gnome-panel libgweather librsvg libcroco libwnck 
startup-notification gnome-settings-daemon gst-plugins-good aalib flac 
libogg gst-plugins-base cdparanoia gstreamer flex gzip liboil 
libtheora libvorbis libcaca libcdio libcddb libdv libshout2 speex 
taglib wavpack libgnomekbd libxklavier libcanberra metacity nautilus 
eel libexif

Error: Status 1 encountered during processing.


- Mark

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users