MacPorts 1.8.1 has been released

[Joshua Root-8]

The MacPorts Project is pleased to announce the release of version
1.8.1. This is a bugfix release with small changes only. The list of
changes is as follows:

    - Installer error messages now display properly even from the Snow
      Leopard MacPorts dmg.

    - 'fetch.type svn' no longer requires the installation of the
      subversion port as of Snow Leopard.

    - Updated manpages and 'port help' output

    - Fixed syncing using the daily tarball.

    - Fixed 'port load'

    - Improved error message when an expression on the command line does
      not match any ports

    - Stopped recording the completion of the install phase in the
      statefile, which led to errors if the port was uninstalled but the
      work dir was not cleaned, and the port was then installed again.

    - Fixed a bug where if an element in the MacPorts directory prefix
      was a symlink, it could be deleted when uninstalling a port.

If you already have MacPorts installed, the preferred method for
updating is to run:

  sudo port selfupdate

For new installs, there are also package installers in disk images
available for 10.4, 10.5, and 10.6 (all universal builds, the first two
i386/ppc and the latter i386/x86_64) at [1]. The source is also
available as tarballs compressed with gzip or bzip2, or from the
subversion tag [2].

Detached PGP signatures for the DMGs and source tarballs have been made
with my key, which is available on the keyservers and my MacPorts wiki
page [3], the fingerprint being:

0xB70C8867DCDBFF26: B6D0 0D4B 209D 03FF 2BCE  B77F B70C 8867 DCDB FF26

Josh
(on behalf of the MacPorts Port Managers)

[1] <http://www.macports.org/install.php>
[2] <http://svn.macports.org/repository/macports/tags/release_1_8_1/>
[3] <http://trac.macports.org/wiki/jmr>
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Joe Schnide]

Morning,

I have had problems with macports and Snow Leopard. I was able to
resolve those issues on an MBP Intel 10.6 by uninstalling macports
completely and installing MacPorts-1.8.0-10.6-SnowLeopard. I was
able to install most of the ports I had under 10.5.x. I have since
upgraded to 10.6.1.

I attempted the same thing with an Intel iMac 10.6.1. I removed
macports completely and am having problems installing macports.
If I use the 1.8.0 dmg, I get the error:
MacPorts-1.8.0 can't be installed on this computer.
The specified message could not be found for the index 16.

I then tried to install with the 1.8.1 dmg and get the error:
MacPorts-1.8.1 can't be installed on this computer.
This package is meant to be installed on Mac OS X 10.6

I made certain there is nothing in /opt except a cisco directory
that has some VPN items.

Is there something I missed or further information that needs
to be provided? Is there a workaround to get macports installed
on 10.6.1?

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

[Ryan Schmidt-24]

On Sep 29, 2009, at 06:27, Joe Schnide wrote:

> I have had problems with macports and Snow Leopard. I was able to
> resolve those issues on an MBP Intel 10.6 by uninstalling macports
> completely and installing MacPorts-1.8.0-10.6-SnowLeopard. I was
> able to install most of the ports I had under 10.5.x. I have since
> upgraded to 10.6.1.
>
> I attempted the same thing with an Intel iMac 10.6.1. I removed
> macports completely and am having problems installing macports.
> If I use the 1.8.0 dmg, I get the error:
> MacPorts-1.8.0 can't be installed on this computer.
> The specified message could not be found for the index 16.

"The specified message could not be found" is one of the problems we  
fixed in 1.8.1.


> I then tried to install with the 1.8.1 dmg and get the error:
> MacPorts-1.8.1 can't be installed on this computer.
> This package is meant to be installed on Mac OS X 10.6

The installer doesn't seem to think you're running Mac OS X 10.6 on  
this computer. What is the output of "uname -a" and "sw_vers"?

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

[Joe Schnide]

At 6:30 AM -0500 9/29/09, Ryan Schmidt wrote:

>On Sep 29, 2009, at 06:27, Joe Schnide wrote:
>
>>I have had problems with macports and Snow Leopard. I was able to
>>resolve those issues on an MBP Intel 10.6 by uninstalling macports
>>completely and installing MacPorts-1.8.0-10.6-SnowLeopard. I was
>>able to install most of the ports I had under 10.5.x. I have since
>>upgraded to 10.6.1.
>>
>>I attempted the same thing with an Intel iMac 10.6.1. I removed
>>macports completely and am having problems installing macports.
>>If I use the 1.8.0 dmg, I get the error:
>>MacPorts-1.8.0 can't be installed on this computer.
>>The specified message could not be found for the index 16.
>
>"The specified message could not be found" is one of the problems we
>fixed in 1.8.1.
>
>>I then tried to install with the 1.8.1 dmg and get the error:
>>MacPorts-1.8.1 can't be installed on this computer.
>>This package is meant to be installed on Mac OS X 10.6
>
>The installer doesn't seem to think you're running Mac OS X 10.6 on
>this computer. What is the output of "uname -a" and "sw_vers"?

schnide-iMac:~ root# sw_vers
ProductName: Mac OS X
ProductVersion: 10.6.1
BuildVersion: 10B504
schnide-iMac:~ root# uname -a
schnide-iMac:~ root# which uname
/usr/bin/uname
schnide-iMac:~ root#

uname does not return any information.

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

[Ryan Schmidt-24]

On Sep 29, 2009, at 07:17, Joe Schnide wrote:

> At 6:30 AM -0500 9/29/09, Ryan Schmidt wrote:
>
>> The installer doesn't seem to think you're running Mac OS X 10.6 on  
>> this computer. What is the output of "uname -a" and "sw_vers"?
>
> schnide-iMac:~ root# sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.6.1
> BuildVersion: 10B504
> schnide-iMac:~ root# uname -a
> schnide-iMac:~ root# which uname
> /usr/bin/uname
> schnide-iMac:~ root#
>
> uname does not return any information.

Ok, you're running 10.6, but your uname command is broken. MacPorts  
uses uname (specifically "uname -r") in the installer script to check  
that your OS version is correct.

uname is important not just for MacPorts itself but for probably most  
software you'd want to install using MacPorts, so you will need to  
figure out why your uname command is broken, and fix it.


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

[Mike Savory-2]

SImilar issue here

$ uname -a
Darwin Shiney.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31  
22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6.1
BuildVersion: 10B504

Any idea where to start looking?

Mike


On Sep 29, 2009, at 5:24 AM, Ryan Schmidt wrote:
> Ok, you're running 10.6, but your uname command is broken. MacPorts  
> uses uname (specifically "uname -r") in the installer script to  
> check that your OS version is correct.
>
> uname is important not just for MacPorts itself but for probably  
> most software you'd want to install using MacPorts, so you will need  
> to figure out why your uname command is broken, and fix it.

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

[Damien Clauzel-2]

Le 29 sept. 2009 à 19:01, Savory Michael a écrit :

> $ uname -a
> Darwin Shiney.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31  
> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
> $ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.6.1
> BuildVersion: 10B504
Same here :

$ uname -a
Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31  
22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6.1
BuildVersion: 10B504

I did a clean install and not an upgrade from Léopard.

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

[Harald Hanche-Olsen]

+ Damien Clauzel <Damien@...>:

> Same here :
>
> $ uname -a
> Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386

What is wrong with that? On Leopard, I see

; uname -a
Darwin mach 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
; sw_vers
ProductName:    Mac OS X
ProductVersion: 10.5.8
BuildVersion:   9L30

The numbers given by uname is the kernel version, NOT the OS version.

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

[Mike Savory-2]

You are of corse perfectly correct, I withdraw my concern

On Sep 29, 2009, at 12:12 PM, Harald Hanche-Olsen wrote:
>> $ uname -a
>> Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> The numbers given by uname is the kernel version, NOT the OS version.

However I am still left unable to install 1.8.1 with the following  
error message...

DEBUG: Rebuilding and reinstalling MacPorts if needed
MacPorts base version 1.8.1 downloaded.
--->  MacPorts base is outdated, installing new version 1.8.1
DEBUG: can't read "tcl_platform(user)": no such variable
     while executing
"string equal $tcl_platform(user) $owner"
     (procedure "macports::selfupdate" line 63)
     invoked from within
"macports::selfupdate [array get global_options]"
Error: /opt/local/bin/port: port selfupdate failed: can't read  
"tcl_platform(user)": no such variable

This is on a normal (non user privs) clean install when Snow Leopard  
was released.
Any ideas?


Regards

Mike

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

[Bryan Blackburn-4]

On Tue, Sep 29, 2009 at 12:21:00PM -0700, Savory Michael said:

> You are of corse perfectly correct, I withdraw my concern
>
> On Sep 29, 2009, at 12:12 PM, Harald Hanche-Olsen wrote:
> >>$ uname -a
> >>Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> >The numbers given by uname is the kernel version, NOT the OS version.
>
> However I am still left unable to install 1.8.1 with the following
> error message...
>
> DEBUG: Rebuilding and reinstalling MacPorts if needed
> MacPorts base version 1.8.1 downloaded.
> --->  MacPorts base is outdated, installing new version 1.8.1
> DEBUG: can't read "tcl_platform(user)": no such variable
>     while executing
> "string equal $tcl_platform(user) $owner"
>     (procedure "macports::selfupdate" line 63)
>     invoked from within
> "macports::selfupdate [array get global_options]"
> Error: /opt/local/bin/port: port selfupdate failed: can't read
> "tcl_platform(user)": no such variable

That's really odd, tcl_platform is a standard Tcl variable, so unless
something is really wrong with your Tcl install, that shouldn't happen.

What is the result of

$ ls -l /usr/bin/tclsh*

Bryan


>
> This is on a normal (non user privs) clean install when Snow Leopard
> was released.
> Any ideas?
>
>
> Regards
>
> Mike
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ralph Pass]

Like several other people I have had trouble with updating to 1.8.1 on
Snow Leopard.

On my Mac Pro (about 19 months old), I updated to Snow Leopard and then
1.8.0 and things worked.  I then did a sudo port selfupdate and it
worked.  A sudo port upgrade outdated also worked.
On a new (3 month old) Macbook Pro, I updated to Snow Leopard and then
1.8.0 and things worked.  However, it failed when I did a sudo port
selfupdate:




 sudo port selfupdate
dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable image
found.  Did find:
    /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong architecture
    while executing
"load /Library/Tcl/macports1.0/MacPorts.dylib"
    ("package ifneeded macports 1.0" script)
    invoked from within
"package require macports"
    (file "/opt/local/bin/port" line 39)


Note that for
uname -a     gives:
Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386

sw_vers      gives:
ProductName:    Mac OS X
ProductVersion:    10.6.1
BuildVersion:    10B504

So I am bit perplexed and looking for guidance.

Thanks,
Ralph Pass



Joshua Root wrote:

> The MacPorts Project is pleased to announce the release of version
> 1.8.1. This is a bugfix release with small changes only. The list of
> changes is as follows:
>
>     - Installer error messages now display properly even from the Snow
>       Leopard MacPorts dmg.
>
>     - 'fetch.type svn' no longer requires the installation of the
>       subversion port as of Snow Leopard.
>
>     - Updated manpages and 'port help' output
>
>     - Fixed syncing using the daily tarball.
>
>     - Fixed 'port load'
>
>     - Improved error message when an expression on the command line does
>       not match any ports
>
>     - Stopped recording the completion of the install phase in the
>       statefile, which led to errors if the port was uninstalled but the
>       work dir was not cleaned, and the port was then installed again.
>
>     - Fixed a bug where if an element in the MacPorts directory prefix
>       was a symlink, it could be deleted when uninstalling a port.
>
> If you already have MacPorts installed, the preferred method for
> updating is to run:
>
>   sudo port selfupdate
>
> For new installs, there are also package installers in disk images
> available for 10.4, 10.5, and 10.6 (all universal builds, the first two
> i386/ppc and the latter i386/x86_64) at [1]. The source is also
> available as tarballs compressed with gzip or bzip2, or from the
> subversion tag [2].
>
> Detached PGP signatures for the DMGs and source tarballs have been made
> with my key, which is available on the keyservers and my MacPorts wiki
> page [3], the fingerprint being:
>
> 0xB70C8867DCDBFF26: B6D0 0D4B 209D 03FF 2BCE  B77F B70C 8867 DCDB FF26
>
> Josh
> (on behalf of the MacPorts Port Managers)
>
> [1] <http://www.macports.org/install.php>
> [2] <http://svn.macports.org/repository/macports/tags/release_1_8_1/>
> [3] <http://trac.macports.org/wiki/jmr>
> _______________________________________________
> macports-users mailing list
> macports-users@...
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>  

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

[Joshua Root-8]

On 2009-9-30 05:21, Savory Michael wrote:

> You are of corse perfectly correct, I withdraw my concern
>
> On Sep 29, 2009, at 12:12 PM, Harald Hanche-Olsen wrote:
>>> $ uname -a
>>> Darwin arda.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
>> The numbers given by uname is the kernel version, NOT the OS version.
>
> However I am still left unable to install 1.8.1 with the following error
> message...
>
> DEBUG: Rebuilding and reinstalling MacPorts if needed
> MacPorts base version 1.8.1 downloaded.
> --->  MacPorts base is outdated, installing new version 1.8.1
> DEBUG: can't read "tcl_platform(user)": no such variable
>     while executing
> "string equal $tcl_platform(user) $owner"
>     (procedure "macports::selfupdate" line 63)
>     invoked from within
> "macports::selfupdate [array get global_options]"
> Error: /opt/local/bin/port: port selfupdate failed: can't read
> "tcl_platform(user)": no such variable
>
> This is on a normal (non user privs) clean install when Snow Leopard was
> released.
> Any ideas?

Are you sure you have the final release of 1.8.0 installed and not the
beta? There was a problem like this but it was fixed.

If it is the beta then it's probably easiest to just install 1.8.1 from
the dmg.

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

[Ralph Pass]

More information:

doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that on
the system that works, the architecture is x86_64 and on the one that
does not work, the architecture is i386.  Both cases the gcc is
gcc-4.2.  Further the dates on the Macports.dylib file is the time of
the sudo port selfupdate.


So why did the selfupdate use architecture i386 (and I know that Snow
Leopard now defaults to x87_64 rather than i386)?



Ralph Pass

Ralph Pass wrote:

> Like several other people I have had trouble with updating to 1.8.1 on
> Snow Leopard.
>
> On my Mac Pro (about 19 months old), I updated to Snow Leopard and
> then 1.8.0 and things worked.  I then did a sudo port selfupdate and
> it worked.  A sudo port upgrade outdated also worked.
> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and then
> 1.8.0 and things worked.  However, it failed when I did a sudo port
> selfupdate:
>
>
>
>
> sudo port selfupdate
> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable image
> found.  Did find:
>    /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
> architecture
>    while executing
> "load /Library/Tcl/macports1.0/MacPorts.dylib"
>    ("package ifneeded macports 1.0" script)
>    invoked from within
> "package require macports"
>    (file "/opt/local/bin/port" line 39)
>
>
> Note that for
> uname -a     gives:
> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
>
> sw_vers      gives:
> ProductName:    Mac OS X
> ProductVersion:    10.6.1
> BuildVersion:    10B504
>
> So I am bit perplexed and looking for guidance.
>
> Thanks,
> Ralph Pass
>
>
>
> Joshua Root wrote:
>> The MacPorts Project is pleased to announce the release of version
>> 1.8.1. This is a bugfix release with small changes only. The list of
>> changes is as follows:
>>
>>     - Installer error messages now display properly even from the Snow
>>       Leopard MacPorts dmg.
>>
>>     - 'fetch.type svn' no longer requires the installation of the
>>       subversion port as of Snow Leopard.
>>
>>     - Updated manpages and 'port help' output
>>
>>     - Fixed syncing using the daily tarball.
>>
>>     - Fixed 'port load'
>>
>>     - Improved error message when an expression on the command line does
>>       not match any ports
>>
>>     - Stopped recording the completion of the install phase in the
>>       statefile, which led to errors if the port was uninstalled but the
>>       work dir was not cleaned, and the port was then installed again.
>>
>>     - Fixed a bug where if an element in the MacPorts directory prefix
>>       was a symlink, it could be deleted when uninstalling a port.
>>
>> If you already have MacPorts installed, the preferred method for
>> updating is to run:
>>
>>   sudo port selfupdate
>>
>> For new installs, there are also package installers in disk images
>> available for 10.4, 10.5, and 10.6 (all universal builds, the first two
>> i386/ppc and the latter i386/x86_64) at [1]. The source is also
>> available as tarballs compressed with gzip or bzip2, or from the
>> subversion tag [2].
>>
>> Detached PGP signatures for the DMGs and source tarballs have been made
>> with my key, which is available on the keyservers and my MacPorts wiki
>> page [3], the fingerprint being:
>>
>> 0xB70C8867DCDBFF26: B6D0 0D4B 209D 03FF 2BCE  B77F B70C 8867 DCDB FF26
>>
>> Josh
>> (on behalf of the MacPorts Port Managers)
>>
>> [1] <http://www.macports.org/install.php>
>> [2] <http://svn.macports.org/repository/macports/tags/release_1_8_1/>
>> [3] <http://trac.macports.org/wiki/jmr>
>> _______________________________________________
>> macports-users mailing list
>> macports-users@...
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>>  
> _______________________________________________
> macports-users mailing list
> macports-users@...
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

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

[Mark Hattam]

On 29 Sep 2009, at 21:47, Ralph Pass wrote:

> More information:
>
> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that  
> on the system that works, the architecture is x86_64 and on the one  
> that does not work, the architecture is i386.  Both cases the gcc is  
> gcc-4.2.  Further the dates on the Macports.dylib file is the time  
> of the sudo port selfupdate.
>
> So why did the selfupdate use architecture i386 (and I know that  
> Snow Leopard now defaults to x87_64 rather than i386)?
>
> Ralph Pass
>
> Ralph Pass wrote:
>> Like several other people I have had trouble with updating to 1.8.1  
>> on Snow Leopard.
>>
>> On my Mac Pro (about 19 months old), I updated to Snow Leopard and  
>> then 1.8.0 and things worked.  I then did a sudo port selfupdate  
>> and it worked.  A sudo port upgrade outdated also worked.
>> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and  
>> then 1.8.0 and things worked.  However, it failed when I did a sudo  
>> port selfupdate:
>>
>> sudo port selfupdate
>> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable  
>> image found.  Did find:
>>   /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong  
>> architecture
>>   while executing
>> "load /Library/Tcl/macports1.0/MacPorts.dylib"
>>   ("package ifneeded macports 1.0" script)
>>   invoked from within
>> "package require macports"
>>   (file "/opt/local/bin/port" line 39)
>>
>> Note that for
>> uname -a     gives:
>> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31  
>> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
>>
>> sw_vers      gives:
>> ProductName:    Mac OS X
>> ProductVersion:    10.6.1
>> BuildVersion:    10B504
>>
>> So I am bit perplexed and looking for guidance.
>>
>> Thanks,
>> Ralph Pass

On my year old 3 GHz iMac, I did a self-update last night from a .dmg  
installed 1.8 to 1.8.1 which went successfully as far as I can tell.

iMac:~ mark$ uname -r
10.0.0

iMac:~ mark$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.6.1
BuildVersion: 10B504

(and after spelling Library correctly)

iMac:~ mark$ lipo -info /Library/Tcl/macports1.0/Macports.dylib
Non-fat file: /Library/Tcl/macports1.0/Macports.dylib is architecture:  
x86_64

iMac:~ mark$ which gcc
/usr/bin/gcc

iMac:~ mark$ gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There  
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR  
PURPOSE.

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

[Bryan Blackburn-4]

On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said:

> More information:
>
> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that
> on the system that works, the architecture is x86_64 and on the one
> that does not work, the architecture is i386.  Both cases the gcc is
> gcc-4.2.  Further the dates on the Macports.dylib file is the time of
> the sudo port selfupdate.
>
>
> So why did the selfupdate use architecture i386 (and I know that Snow
> Leopard now defaults to x87_64 rather than i386)?

That's definitely the question, as it shouldn't be doing that.  It shouldn't
be what you have for build_arch in macports.conf as I tried that, and
MacPorts.dylib was still x86_64 after a selfupdate.

What is the result from the following commands?

$ ls -l /usr/bin/gcc*
$ port installed "gcc*"

Also, did you run selfupdate from the shell, or where you in port's
interactive mode?

Bryan

>
>
>
> Ralph Pass
>
> Ralph Pass wrote:
> >Like several other people I have had trouble with updating to 1.8.1
> >on Snow Leopard.
> >
> >On my Mac Pro (about 19 months old), I updated to Snow Leopard and
> >then 1.8.0 and things worked.  I then did a sudo port selfupdate
> >and it worked.  A sudo port upgrade outdated also worked.
> >On a new (3 month old) Macbook Pro, I updated to Snow Leopard and
> >then 1.8.0 and things worked.  However, it failed when I did a sudo
> >port selfupdate:
> >
> >
> >
> >
> >sudo port selfupdate
> >dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable
> >image found.  Did find:
> >   /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
> >architecture
> >   while executing
> >"load /Library/Tcl/macports1.0/MacPorts.dylib"
> >   ("package ifneeded macports 1.0" script)
> >   invoked from within
> >"package require macports"
> >   (file "/opt/local/bin/port" line 39)
> >
> >
> >Note that for
> >uname -a     gives:
> >Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> >22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
> >
> >sw_vers      gives:
> >ProductName:    Mac OS X
> >ProductVersion:    10.6.1
> >BuildVersion:    10B504
> >
> >So I am bit perplexed and looking for guidance.
> >
> >Thanks,
> >Ralph Pass

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

[Bryan Blackburn-4]

On Tue, Sep 29, 2009 at 01:10:49PM -0700, Savory Michael said:
> On Sep 29, 2009, at 12:35 PM, Bryan Blackburn wrote:
[...]

> >That's really odd, tcl_platform is a standard Tcl variable, so unless
> >something is really wrong with your Tcl install, that shouldn't
> >happen.
> >
> >What is the result of
> >
> >$ ls -l /usr/bin/tclsh*
> >
> >Bryan
>
> $ ls -l /usr/bin/tclsh*
> lrwxr-xr-x  1 root  wheel   8 Aug 29 00:18 /usr/bin/tclsh -> tclsh8.5
> lrwxr-xr-x  1 root  wheel  67 Aug 29 00:18 /usr/bin/tclsh8.4 ->
> ../../System/Library/Frameworks/Tcl.framework/Versions/8.4/tclsh8.4
> lrwxr-xr-x  1 root  wheel  67 Aug 29 00:18 /usr/bin/tclsh8.5 ->
> ../../System/Library/Frameworks/Tcl.framework/Versions/8.5/tclsh8.5

That looks right; definitely heed Josh's message about a possible
trunk-based install (check the date of /opt/local/bin/port) in case that is
the issue..

Also, don't forget to reply to the list as well.

Bryan

>
>
> >>
> >>This is on a normal (non user privs) clean install when Snow Leopard
> >>was released.
> >>Any ideas?
> >>
> >>
> >>Regards
> >>
> >>Mike

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

[Bryan Blackburn-4]

On Tue, Sep 29, 2009 at 05:34:49PM -0400, Ralph Pass said:

> I did it from the shell (I did not know that ports had an interactive mode!)
>
> ls -l /usr/bin/gcc*  ----->
> lrwxr-xr-x  1 root  wheel       7 Sep  8 12:56 /usr/bin/gcc -> gcc-4.2
> -rwxr-xr-x  1 root  wheel   97392 May 18 13:27 /usr/bin/gcc-4.0
> -rwxr-xr-x  1 root  wheel  166128 May 18 14:13 /usr/bin/gcc-4.2
>
>
> port installed "gcc*"    ------->  None of the specified ports are
> installed.

Okay, so no funky symlinks for gcc in /usr and no gcc ports installed which
could be compiling wrong.

Just to make sure, 'which gcc' does return '/usr/bin/gcc' right?  Other than
that, I'm out of ideas at the moment.

Also, don't forget to send to the list instead of just me...

Bryan

>
>
> You did not ask but I have:
> .
> .
> .# CPU architecture to compile for. Defaults to i386 or ppc on Mac OS X 10.5
> # and earlier, depending on the CPU type detected at runtime. On Mac
> OS X 10.6
> # the default is x86_64 if the CPU supports it, i386 otherwise.
> #build_arch                     i386
> .
> .
> .
> # machine architectures
> universal_archs         x86_64 i386
>
> in the macports.config file.
>
>
> Ralph Pass
>
>
>
> Bryan Blackburn wrote:
> >On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said:
> >>More information:
> >>
> >>doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that
> >>on the system that works, the architecture is x86_64 and on the one
> >>that does not work, the architecture is i386.  Both cases the gcc is
> >>gcc-4.2.  Further the dates on the Macports.dylib file is the time of
> >>the sudo port selfupdate.
> >>
> >>
> >>So why did the selfupdate use architecture i386 (and I know that Snow
> >>Leopard now defaults to x87_64 rather than i386)?
> >
> >That's definitely the question, as it shouldn't be doing that.  It shouldn't
> >be what you have for build_arch in macports.conf as I tried that, and
> >MacPorts.dylib was still x86_64 after a selfupdate.
> >
> >What is the result from the following commands?
> >
> >$ ls -l /usr/bin/gcc*
> >$ port installed "gcc*"
> >
> >Also, did you run selfupdate from the shell, or where you in port's
> >interactive mode?
> >
> >Bryan
> >
> >
> >>
> >>Ralph Pass
> >>
> >>Ralph Pass wrote:
> >>>Like several other people I have had trouble with updating to 1.8.1
> >>>on Snow Leopard.
> >>>
> >>>On my Mac Pro (about 19 months old), I updated to Snow Leopard and
> >>>then 1.8.0 and things worked.  I then did a sudo port selfupdate
> >>>and it worked.  A sudo port upgrade outdated also worked.
> >>>On a new (3 month old) Macbook Pro, I updated to Snow Leopard and
> >>>then 1.8.0 and things worked.  However, it failed when I did a sudo
> >>>port selfupdate:
> >>>
> >>>
> >>>
> >>>
> >>>sudo port selfupdate
> >>>dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable
> >>>image found.  Did find:
> >>>  /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
> >>>architecture
> >>>  while executing
> >>>"load /Library/Tcl/macports1.0/MacPorts.dylib"
> >>>  ("package ifneeded macports 1.0" script)
> >>>  invoked from within
> >>>"package require macports"
> >>>  (file "/opt/local/bin/port" line 39)
> >>>
> >>>
> >>>Note that for
> >>>uname -a     gives:
> >>>Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
> >>>22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
> >>>
> >>>sw_vers      gives:
> >>>ProductName:    Mac OS X
> >>>ProductVersion:    10.6.1
> >>>BuildVersion:    10B504
> >>>
> >>>So I am bit perplexed and looking for guidance.
> >>>
> >>>Thanks,
> >>>Ralph Pass
> >[...]

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

[Ralph Pass]

Yes, which gcc does return /usr/bin/gcc

Ralph Pass




Bryan Blackburn wrote:

> On Tue, Sep 29, 2009 at 05:34:49PM -0400, Ralph Pass said:
>  
>> I did it from the shell (I did not know that ports had an interactive mode!)
>>
>> ls -l /usr/bin/gcc*  ----->
>> lrwxr-xr-x  1 root  wheel       7 Sep  8 12:56 /usr/bin/gcc -> gcc-4.2
>> -rwxr-xr-x  1 root  wheel   97392 May 18 13:27 /usr/bin/gcc-4.0
>> -rwxr-xr-x  1 root  wheel  166128 May 18 14:13 /usr/bin/gcc-4.2
>>
>>
>> port installed "gcc*"    ------->  None of the specified ports are
>> installed.
>>    
>
> Okay, so no funky symlinks for gcc in /usr and no gcc ports installed which
> could be compiling wrong.
>
> Just to make sure, 'which gcc' does return '/usr/bin/gcc' right?  Other than
> that, I'm out of ideas at the moment.
>
> Also, don't forget to send to the list instead of just me...
>
> Bryan
>
>
>  
>> You did not ask but I have:
>> .
>> .
>> .# CPU architecture to compile for. Defaults to i386 or ppc on Mac OS X 10.5
>> # and earlier, depending on the CPU type detected at runtime. On Mac
>> OS X 10.6
>> # the default is x86_64 if the CPU supports it, i386 otherwise.
>> #build_arch                     i386
>> .
>> .
>> .
>> # machine architectures
>> universal_archs         x86_64 i386
>>
>> in the macports.config file.
>>
>>
>> Ralph Pass
>>
>>
>>
>> Bryan Blackburn wrote:
>>    
>>> On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said:
>>>      
>>>> More information:
>>>>
>>>> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that
>>>> on the system that works, the architecture is x86_64 and on the one
>>>> that does not work, the architecture is i386.  Both cases the gcc is
>>>> gcc-4.2.  Further the dates on the Macports.dylib file is the time of
>>>> the sudo port selfupdate.
>>>>
>>>>
>>>> So why did the selfupdate use architecture i386 (and I know that Snow
>>>> Leopard now defaults to x87_64 rather than i386)?
>>>>        
>>> That's definitely the question, as it shouldn't be doing that.  It shouldn't
>>> be what you have for build_arch in macports.conf as I tried that, and
>>> MacPorts.dylib was still x86_64 after a selfupdate.
>>>
>>> What is the result from the following commands?
>>>
>>> $ ls -l /usr/bin/gcc*
>>> $ port installed "gcc*"
>>>
>>> Also, did you run selfupdate from the shell, or where you in port's
>>> interactive mode?
>>>
>>> Bryan
>>>
>>>
>>>      
>>>> Ralph Pass
>>>>
>>>> Ralph Pass wrote:
>>>>        
>>>>> Like several other people I have had trouble with updating to 1.8.1
>>>>> on Snow Leopard.
>>>>>
>>>>> On my Mac Pro (about 19 months old), I updated to Snow Leopard and
>>>>> then 1.8.0 and things worked.  I then did a sudo port selfupdate
>>>>> and it worked.  A sudo port upgrade outdated also worked.
>>>>> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and
>>>>> then 1.8.0 and things worked.  However, it failed when I did a sudo
>>>>> port selfupdate:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> sudo port selfupdate
>>>>> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable
>>>>> image found.  Did find:
>>>>>  /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
>>>>> architecture
>>>>>  while executing
>>>>> "load /Library/Tcl/macports1.0/MacPorts.dylib"
>>>>>  ("package ifneeded macports 1.0" script)
>>>>>  invoked from within
>>>>> "package require macports"
>>>>>  (file "/opt/local/bin/port" line 39)
>>>>>
>>>>>
>>>>> Note that for
>>>>> uname -a     gives:
>>>>> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
>>>>> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
>>>>>
>>>>> sw_vers      gives:
>>>>> ProductName:    Mac OS X
>>>>> ProductVersion:    10.6.1
>>>>> BuildVersion:    10B504
>>>>>
>>>>> So I am bit perplexed and looking for guidance.
>>>>>
>>>>> Thanks,
>>>>> Ralph Pass
>>>>>          
>>> [...]
>>>      
> _______________________________________________
> macports-users mailing list
> macports-users@...
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>  

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

[Ralph Pass]

I have now done a sudo port selfupdate on two more Macs running Snow
Leopard:  One a Macbook Pro that is about 30 months old and an iMac that
was purchased a month ago.   Both times it worked and the sudo port
update outdated did as well.

The only problem machine was a Macbook Pro purchased four months ago.

I guess the only solution is to remove Macports and reinstall.

Ralph Pass


Bryan Blackburn wrote:

> On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said:
>  
>> More information:
>>
>> doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that
>> on the system that works, the architecture is x86_64 and on the one
>> that does not work, the architecture is i386.  Both cases the gcc is
>> gcc-4.2.  Further the dates on the Macports.dylib file is the time of
>> the sudo port selfupdate.
>>
>>
>> So why did the selfupdate use architecture i386 (and I know that Snow
>> Leopard now defaults to x87_64 rather than i386)?
>>    
>
> That's definitely the question, as it shouldn't be doing that.  It shouldn't
> be what you have for build_arch in macports.conf as I tried that, and
> MacPorts.dylib was still x86_64 after a selfupdate.
>
> What is the result from the following commands?
>
> $ ls -l /usr/bin/gcc*
> $ port installed "gcc*"
>
> Also, did you run selfupdate from the shell, or where you in port's
> interactive mode?
>
> Bryan
>
>
>  
>>
>> Ralph Pass
>>
>> Ralph Pass wrote:
>>    
>>> Like several other people I have had trouble with updating to 1.8.1
>>> on Snow Leopard.
>>>
>>> On my Mac Pro (about 19 months old), I updated to Snow Leopard and
>>> then 1.8.0 and things worked.  I then did a sudo port selfupdate
>>> and it worked.  A sudo port upgrade outdated also worked.
>>> On a new (3 month old) Macbook Pro, I updated to Snow Leopard and
>>> then 1.8.0 and things worked.  However, it failed when I did a sudo
>>> port selfupdate:
>>>
>>>
>>>
>>>
>>> sudo port selfupdate
>>> dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable
>>> image found.  Did find:
>>>   /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong
>>> architecture
>>>   while executing
>>> "load /Library/Tcl/macports1.0/MacPorts.dylib"
>>>   ("package ifneeded macports 1.0" script)
>>>   invoked from within
>>> "package require macports"
>>>   (file "/opt/local/bin/port" line 39)
>>>
>>>
>>> Note that for
>>> uname -a     gives:
>>> Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31
>>> 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386
>>>
>>> sw_vers      gives:
>>> ProductName:    Mac OS X
>>> ProductVersion:    10.6.1
>>> BuildVersion:    10B504
>>>
>>> So I am bit perplexed and looking for guidance.
>>>
>>> Thanks,
>>> Ralph Pass
>>>      
> [...]
> _______________________________________________
> macports-users mailing list
> macports-users@...
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
>  

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

[Joshua Root-8]

On 2009-10-10 11:47, Ralph Pass wrote:
> I have now done a sudo port selfupdate on two more Macs running Snow
> Leopard:  One a Macbook Pro that is about 30 months old and an iMac that
> was purchased a month ago.   Both times it worked and the sudo port
> update outdated did as well.
>
> The only problem machine was a Macbook Pro purchased four months ago.
>
> I guess the only solution is to remove Macports and reinstall.

Or install 1.8.1 from the dmg.

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