Bad CPU type in executable

[Dennis C]

Greetings;

Am in the process of making the switch from dual-boot PCs including FreeBSD, so kind of new to this, but am now running Snow Leopard and one of the first MacPorts I installed was psycopg2 and was able to run the python2.6 and successfully import the aforementioned module, but now the following's happening:

DCSs-Mac-mini:bin DCSWest$ python2.6

-bash: /opt/local/bin/python2.6: Bad CPU type in executable

So not quite sure what happened in between, but wondering if it wasn't something with the following attempt to update software:

DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate

Password:

--->  Updating the ports tree

--->  Updating MacPorts base sources using rsync

MacPorts base version 1.8.1 installed,

MacPorts base version 1.8.1 downloaded.

--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run

  port upgrade outdated

DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated

--->  Computing dependencies for dbus

--->  Configuring dbus

Error: Target org.macports.configure returned: autoreconf failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.16" && autoreconf --install " returned error 126

Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl: bad interpreter: Bad CPU type in executable

Error: Unable to upgrade port: 1

Thanks,

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

[Ryan Schmidt-24]

On Oct 27, 2009, at 18:56, Dennis C wrote:

> Am in the process of making the switch from dual-boot PCs including  
> FreeBSD, so kind of new to this, but am now running Snow Leopard and  
> one of the first MacPorts I installed was psycopg2 and was able to  
> run the python2.6 and successfully import the aforementioned module,  
> but now the following's happening:
>
> DCSs-Mac-mini:bin DCSWest$ python2.6
> -bash: /opt/local/bin/python2.6: Bad CPU type in executable
>
>
> So not quite sure what happened in between, but wondering if it  
> wasn't something with the following attempt to update software:
>
> DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate
> Password:
> --->  Updating the ports tree
> --->  Updating MacPorts base sources using rsync
> MacPorts base version 1.8.1 installed,
> MacPorts base version 1.8.1 downloaded.
> --->  MacPorts base is already the latest version
>
> The ports tree has been updated. To upgrade your installed ports,  
> you should run
>   port upgrade outdated
>
> DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated
> --->  Computing dependencies for dbus
> --->  Configuring dbus
> Error: Target org.macports.configure returned: autoreconf failure:  
> shell command " cd "/opt/local/var/macports/build/
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus
> /work/dbus-1.2.16" && autoreconf --install " returned error 126
> Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl:  
> bad interpreter: Bad CPU type in executable
>
> Error: Unable to upgrade port: 1

What kind of computer is this? I'm wondering if you have a 32-bit or  
64-bit processor. All but the very first Macs have 64-bit processors.

What is the architecture of, say, /opt/local/bin/perl? Use "lipo -
info /opt/local/bin/perl" to find out.

Did you recently upgrade to Snow Leopard -- or did you recently  
migrate your MacPorts installation from a different Mac -- and if so,  
did you uninstall and reinstall all ports? See the Migration page for  
more instructions:

http://trac.macports.org/wiki/Migration

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

[Ryan Schmidt-24]

On Oct 27, 2009, at 22:32, Ryan Schmidt wrote:

> What kind of computer is this? I'm wondering if you have a 32-bit or  
> 64-bit processor. All but the very first Macs have 64-bit processors.

Um, what I was trying to say here was all Intel Macs except for the  
very first Intel Macs have 64-bit processors.

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

[Dennis C]

It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to the prior message, since I forgot to include the list, am reasonably assured that I downloaded the Snow Leopard "dmg" which I thought can only be for Intel like the OS itself and the ported programs did run at first, but how can I maybe confirm it?

On Tue, Oct 27, 2009 at 8:38 PM, Ryan Schmidt <ryandesign@...> wrote:

On Oct 27, 2009, at 22:32, Ryan Schmidt wrote:

What kind of computer is this? I'm wondering if you have a 32-bit or 64-bit processor. All but the very first Macs have 64-bit processors.

Um, what I was trying to say here was all Intel Macs except for the very first Intel Macs have 64-bit processors.

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

[Dennis C]

Sorry I missed this part of the thread, but I'll check the Perl architecture as soon as I get back to the machine and I did purchase a Snow Leopard upgrade, but I just did a "clean install" and then followed suit with the other software such as some MacPorts too which did run for a while, before "something happened..."

On Tue, Oct 27, 2009 at 8:32 PM, Ryan Schmidt <ryandesign@...> wrote:

On Oct 27, 2009, at 18:56, Dennis C wrote:

Am in the process of making the switch from dual-boot PCs including FreeBSD, so kind of new to this, but am now running Snow Leopard and one of the first MacPorts I installed was psycopg2 and was able to run the python2.6 and successfully import the aforementioned module, but now the following's happening:

DCSs-Mac-mini:bin DCSWest$ python2.6
-bash: /opt/local/bin/python2.6: Bad CPU type in executable


So not quite sure what happened in between, but wondering if it wasn't something with the following attempt to update software:

DCSs-Mac-mini:~ DCSWest$ sudo port selfupdate
Password:
--->  Updating the ports tree
--->  Updating MacPorts base sources using rsync
MacPorts base version 1.8.1 installed,
MacPorts base version 1.8.1 downloaded.
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
 port upgrade outdated

DCSs-Mac-mini:~ DCSWest$ sudo port upgrade outdated
--->  Computing dependencies for dbus
--->  Configuring dbus
Error: Target org.macports.configure returned: autoreconf failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_dbus/work/dbus-1.2.16" && autoreconf --install " returned error 126
Command output: sh: /opt/local/bin/autoreconf: /opt/local/bin/perl: bad interpreter: Bad CPU type in executable

Error: Unable to upgrade port: 1

What kind of computer is this? I'm wondering if you have a 32-bit or 64-bit processor. All but the very first Macs have 64-bit processors.

What is the architecture of, say, /opt/local/bin/perl? Use "lipo -info /opt/local/bin/perl" to find out.

Did you recently upgrade to Snow Leopard -- or did you recently migrate your MacPorts installation from a different Mac -- and if so, did you uninstall and reinstall all ports? See the Migration page for more instructions:

http://trac.macports.org/wiki/Migration

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

[Ryan Schmidt-24]

On Oct 28, 2009, at 09:41, Dennis C wrote:

> Sorry I missed this part of the thread, but I'll check the Perl  
> architecture as soon as I get back to the machine and I did purchase  
> a Snow Leopard upgrade, but I just did a "clean install" and then  
> followed suit with the other software such as some MacPorts too  
> which did run for a while, before "something happened..."

It might help to know what that "something" was. Because if you did a  
clean install, and (this is important) did not migrate your MacPorts  
installation to this machine from somewhere else, but instead  
installed MacPorts fresh using the MacPorts Snow Leopard dmg, as you  
said, then all your software should have been built on this machine on  
Snow Leopard, so it should all be the correct CPU architecture.
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ryan Schmidt-24]

On Oct 28, 2009, at 09:31, Dennis C wrote:

> It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to  
> the prior message, since I forgot to include the list, am reasonably  
> assured that I downloaded the Snow Leopard "dmg" which I thought can  
> only be for Intel like the OS itself and the ported programs did run  
> at first, but how can I maybe confirm it?

The three MacPorts 1.8.1 disk image installers will check the OS  
version is correct before allowing you to proceed. So if you were able  
to install MacPorts on Snow Leopard using it, then that is  
confirmation that you downloaded the Snow Leopard version.

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

[Dennis C]

The only other thing I can think of is that I tried and failed installing from source a program called "Qtstalker" and so maybe that did "who knows what..."  Sorry I forgot to mention it, but thought the error message could be obvious enough anyway...  Thanks for your help though and maybe I'll just have to reinstall everything and hope that Qtstalker or something similar shows up in MacPorts soon because that's what's still keeping me tied to a PC, using that software to manage some market trading...

On Wed, Oct 28, 2009 at 3:30 PM, Ryan Schmidt <ryandesign@...> wrote:

On Oct 28, 2009, at 09:31, Dennis C wrote:

It's a Mini Mac with an Intel Core 2 Duo CPU and also in response to the prior message, since I forgot to include the list, am reasonably assured that I downloaded the Snow Leopard "dmg" which I thought can only be for Intel like the OS itself and the ported programs did run at first, but how can I maybe confirm it?

The three MacPorts 1.8.1 disk image installers will check the OS version is correct before allowing you to proceed. So if you were able to install MacPorts on Snow Leopard using it, then that is confirmation that you downloaded the Snow Leopard version.

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

[Ryan Schmidt-24]

On Oct 28, 2009, at 19:18, Dennis C wrote:

> The only other thing I can think of is that I tried and failed  
> installing from source a program called "Qtstalker" and so maybe  
> that did "who knows what..."  Sorry I forgot to mention it, but  
> thought the error message could be obvious enough anyway...  Thanks  
> for your help though and maybe I'll just have to reinstall everything

Before you do, if you can provide the information I requested earlier  
about the architectures your installed software has, maybe that will  
clue us in about what happened. Try using both "lipo -info /opt/local/
bin/perl" and "file /opt/local/bin/perl" to try to find out why your  
perl is not satisfactory to your Mac.

> and hope that Qtstalker or something similar shows up in MacPorts  
> soon because that's what's still keeping me tied to a PC, using that  
> software to manage some market trading...

You could file a port request ticket in the issue tracker. I looked  
into qtstalker briefly just now, and didn't get very far, because it  
requires qt3 (is not compatible with qt4), whereas qt3 is not  
compatible with Snow Leopard (see #21459). Then again, I can't get the  
current qt4 to build on Snow Leopard either; there are tickets for  
this as well. Qt is an unimaginably huge piece of library, which  
probably means it has a bazillion things that could go wrong. To get  
qtstalker in MacPorts, you should either work with the authors of qt  
to get qt3 working properly on Snow Leopard, or work with the authors  
of qtstalker to get it working with qt4 and work with the authors of  
qt to get qt4 working properly in MacPorts. In the mean time, someone  
who still uses Leopard could work on the portfile. (I don't have  
Leopard with me at the moment.)



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

[Dennis C]

Cannot believe it!  I just realized that the Apple store where I had this Mini Mac in for repair apparently replaced the board with a Core Duo CPU instead of the Core 2 Duo CPU I took it in with!  Not exactly sure why only the MacPorts programs crashed and not any of the Quartz ones, but at least it explains the immediate problem...

I did also start a discussion on the Qtstalker mailing list and the development version's based on Qt4 where someone even has it all running on their Mac albeit on Tiger, so it may be totally doable once we hopefully resolve this Qt4 on Snow Leopard issue...

On Wed, Oct 28, 2009 at 7:29 PM, Ryan Schmidt <ryandesign@...> wrote:

On Oct 28, 2009, at 19:18, Dennis C wrote:

The only other thing I can think of is that I tried and failed installing from source a program called "Qtstalker" and so maybe that did "who knows what..."  Sorry I forgot to mention it, but thought the error message could be obvious enough anyway...  Thanks for your help though and maybe I'll just have to reinstall everything

Before you do, if you can provide the information I requested earlier about the architectures your installed software has, maybe that will clue us in about what happened. Try using both "lipo -info /opt/local/bin/perl" and "file /opt/local/bin/perl" to try to find out why your perl is not satisfactory to your Mac.

and hope that Qtstalker or something similar shows up in MacPorts soon because that's what's still keeping me tied to a PC, using that software to manage some market trading...

You could file a port request ticket in the issue tracker. I looked into qtstalker briefly just now, and didn't get very far, because it requires qt3 (is not compatible with qt4), whereas qt3 is not compatible with Snow Leopard (see #21459). Then again, I can't get the current qt4 to build on Snow Leopard either; there are tickets for this as well. Qt is an unimaginably huge piece of library, which probably means it has a bazillion things that could go wrong. To get qtstalker in MacPorts, you should either work with the authors of qt to get qt3 working properly on Snow Leopard, or work with the authors of qtstalker to get it working with qt4 and work with the authors of qt to get qt4 working properly in MacPorts. In the mean time, someone who still uses Leopard could work on the portfile. (I don't have Leopard with me at the moment.)

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

[Dennis C]

Just a follow-up to let you know that getting the Core 2 Duo CPU back in this mini Mac seems to have definitely cleared up everything including a development version of Qtstalker now running based on Qt4 which did also seem to build fine for me through MacPorts on Snow Leopard, since you mentioned about tickets for this...  Thanks again for all your help!!!

You could file a port request ticket in the issue tracker. I looked into qtstalker briefly just now, and didn't get very far, because it requires qt3 (is not compatible with qt4), whereas qt3 is not compatible with Snow Leopard (see #21459). Then again, I can't get the current qt4 to build on Snow Leopard either; there are tickets for this as well. Qt is an unimaginably huge piece of library, which probably means it has a bazillion things that could go wrong. To get qtstalker in MacPorts, you should either work with the authors of qt to get qt3 working properly on Snow Leopard, or work with the authors of qtstalker to get it working with qt4 and work with the authors of qt to get qt4 working properly in MacPorts. In the mean time, someone who still uses Leopard could work on the portfile. (I don't have Leopard with me at the moment.)

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