Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Salut ! ;)

 One last thing: it was not a migration, the computer came whith snow 
 leopard...

What's the output of:

strings /usr/bin/lipo | grep x86_64

Bonne journée !
Vincent
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 03:25, Anne Poupon wrote:

 sh-3.2# /usr/bin/lipo -info /usr/lib/libz.dylib
 Architectures in the fat file: /usr/lib/libz.dylib are: (cputype (16777223) 
 cpusubtype (3)) i386 ppc7400 

This confirms your lipo command is broken. Somehow, an older version of lipo 
than the one that shipped with Snow Leopard has been copied to /usr/bin/lipo. 
Replace it with a copy that came from Snow Leopard, either from your backups, 
or from the Mac OS X Snow Leopard DVD.



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


Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:16, Ryan Schmidt a écrit :

 On Jul 22, 2010, at 03:25, Anne Poupon wrote:
 
 sh-3.2# /usr/bin/lipo -info /usr/lib/libz.dylib
 Architectures in the fat file: /usr/lib/libz.dylib are: (cputype (16777223) 
 cpusubtype (3)) i386 ppc7400 
 
 This confirms your lipo command is broken. Somehow, an older version of lipo 
 than the one that shipped with Snow Leopard has been copied to /usr/bin/lipo. 
 Replace it with a copy that came from Snow Leopard, either from your backups, 
 or from the Mac OS X Snow Leopard DVD.

It would also be interesting to know what is the output of:

/usr/bin/lipo -info /usr/bin/lipo

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


Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
 strings /usr/bin/lipo | grep x86_64

  nothing...

 This confirms your lipo command is broken. Somehow, an older version of
lipo than the one that shipped with Snow Leopard has been copied to
/usr/bin/lipo. Replace it with a copy that came from Snow Leopard, either
from your backups, or from  the Mac OS X Snow Leopard DVD.

  I don't find any lipo on the DVD...

sh-3.2# /usr/bin/lipo -info /usr/bin/lipo
Non-fat file: /usr/bin/lipo is architecture: ppc

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


Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Re-

 sh-3.2# /usr/bin/lipo -info /usr/bin/lipo
 Non-fat file: /usr/bin/lipo is architecture: ppc

!!!
On what model are you working?

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


Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
3.06 GHz intel core 2 duo ...

On Thu, Jul 22, 2010 at 11:32 AM, Vincent Habchi vi...@macports.org wrote:

 Re-

  sh-3.2# /usr/bin/lipo -info /usr/bin/lipo
  Non-fat file: /usr/bin/lipo is architecture: ppc

 !!!
 On what model are you working?

 Vincent

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


Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:36, Anne Poupon a écrit :

 3.06 GHz intel core 2 duo ...

Somehow, this is all wrong. You should have a two-way Intel universal lipo:

PM: /usr/bin/lipo -info /usr/bin/lipo
Architectures in the fat file: /usr/bin/lipo are: x86_64 i386 

---

and Snow Leopard does not work with PPC, so you should not have any PPC 
binaries. 

What is the output of: uname -a?

Vincent

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


Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
sh-3.2# uname -a
Darwin iMac-de-Pauline-Gloaguen.local 10.4.0 Darwin Kernel Version 10.4.0:
Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386

On Thu, Jul 22, 2010 at 11:42 AM, Vincent Habchi vi...@macports.org wrote:

 Le 22 juil. 2010 à 11:36, Anne Poupon a écrit :

  3.06 GHz intel core 2 duo ...

 Somehow, this is all wrong. You should have a two-way Intel universal lipo:

 PM: /usr/bin/lipo -info /usr/bin/lipo
 Architectures in the fat file: /usr/bin/lipo are: x86_64 i386

 ---

 and Snow Leopard does not work with PPC, so you should not have any PPC
 binaries.

 What is the output of: uname -a?

 Vincent


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


Re: cputype problem on snow leopard

2010-07-22 Thread Vincent Habchi
Le 22 juil. 2010 à 11:53, Anne Poupon a écrit :

 sh-3.2# uname -a
 Darwin iMac-de-Pauline-Gloaguen.local 10.4.0 Darwin Kernel Version 10.4.0: 
 Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386

Well, beats me (comme disent les Anglais) ;)

Somehow your binaries are messed up (SL n'aime pas les bretonnes ? :)). Have 
you tried lipo on some other /usr/bin/ binaries? Just to figure out if this 
flaw is limited to lipo or general.

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


Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt
On Jul 22, 2010, at 04:42, Vincent Habchi wrote:

 Le 22 juil. 2010 à 11:36, Anne Poupon a écrit :
 
 3.06 GHz intel core 2 duo ...
 
 Somehow, this is all wrong. You should have a two-way Intel universal lipo:
 
 PM: /usr/bin/lipo -info /usr/bin/lipo
 Architectures in the fat file: /usr/bin/lipo are: x86_64 i386 
 
 ---
 
 and Snow Leopard does not work with PPC, so you should not have any PPC 
 binaries. 

Yes, we've already established that her lipo is not appropriate for her 
operating system. Somehow her lipo has been replaced with an earlier version, 
as also happened for the reporter of #24825. It's not particularly interesting 
to know how this happened; she just needs to copy a correct version of lipo 
back in place.

Anne, sorry, you're right, lipo is not directly available on the Mac OS X Snow 
Leopard DVD as I had initially thought. It's in the BSD.pkg installation 
package, though, which on my Snow Leopard DVD is in 
/System/Installation/Packages. It might be easiest to get it out of that 
package using Pacifist, then copy it into /usr/bin replacing the wrong one 
that's there.


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


Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
Ok, I'll try that !

On Thu, Jul 22, 2010 at 12:06 PM, Ryan Schmidt ryandes...@macports.orgwrote:

 On Jul 22, 2010, at 04:42, Vincent Habchi wrote:

  Le 22 juil. 2010 à 11:36, Anne Poupon a écrit :
 
  3.06 GHz intel core 2 duo ...
 
  Somehow, this is all wrong. You should have a two-way Intel universal
 lipo:
 
  PM: /usr/bin/lipo -info /usr/bin/lipo
  Architectures in the fat file: /usr/bin/lipo are: x86_64 i386
 
  ---
 
  and Snow Leopard does not work with PPC, so you should not have any PPC
 binaries.

 Yes, we've already established that her lipo is not appropriate for her
 operating system. Somehow her lipo has been replaced with an earlier
 version, as also happened for the reporter of #24825. It's not particularly
 interesting to know how this happened; she just needs to copy a correct
 version of lipo back in place.

 Anne, sorry, you're right, lipo is not directly available on the Mac OS X
 Snow Leopard DVD as I had initially thought. It's in the BSD.pkg
 installation package, though, which on my Snow Leopard DVD is in
 /System/Installation/Packages. It might be easiest to get it out of that
 package using Pacifist, then copy it into /usr/bin replacing the wrong one
 that's there.



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


Re: cputype problem on snow leopard

2010-07-22 Thread Anne Poupon
Thanks ! It's working now. I have now the right answer from lipo, and I was
able to install gettext (I suppose the others will install as well).

I still can't understand why lipo was not working... I took it again from
the same DVD and now it's working. Strange...

Anyway, thanks very much for your precious help, I must admit this was way
above my head...

Anne

On Thu, Jul 22, 2010 at 12:06 PM, Ryan Schmidt ryandes...@macports.orgwrote:

 On Jul 22, 2010, at 04:42, Vincent Habchi wrote:

  Le 22 juil. 2010 à 11:36, Anne Poupon a écrit :
 
  3.06 GHz intel core 2 duo ...
 
  Somehow, this is all wrong. You should have a two-way Intel universal
 lipo:
 
  PM: /usr/bin/lipo -info /usr/bin/lipo
  Architectures in the fat file: /usr/bin/lipo are: x86_64 i386
 
  ---
 
  and Snow Leopard does not work with PPC, so you should not have any PPC
 binaries.

 Yes, we've already established that her lipo is not appropriate for her
 operating system. Somehow her lipo has been replaced with an earlier
 version, as also happened for the reporter of #24825. It's not particularly
 interesting to know how this happened; she just needs to copy a correct
 version of lipo back in place.

 Anne, sorry, you're right, lipo is not directly available on the Mac OS X
 Snow Leopard DVD as I had initially thought. It's in the BSD.pkg
 installation package, though, which on my Snow Leopard DVD is in
 /System/Installation/Packages. It might be easiest to get it out of that
 package using Pacifist, then copy it into /usr/bin replacing the wrong one
 that's there.



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


Re: cputype problem on snow leopard

2010-07-22 Thread Ryan Schmidt

On Jul 22, 2010, at 07:09, Anne Poupon wrote:

 I still can't understand why lipo was not working... I took it again from the 
 same DVD and now it's working. Strange...

My only guess is that some installer of some software out on the Internet, that 
you downloaded and installed, contained an ancient copy of lipo and overwrote 
the one on your system. If you have any recollection what that software might 
have been, maybe we can locate it again, and inform its distributor that their 
distribution is problematic. But your immediate problem is at least solved for 
now.


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


Re: cputype problem on snow leopard

2010-07-20 Thread Daniel J. Luke
On Jul 20, 2010, at 11:26 AM, Anne Poupon wrote:
   I'm trying to install postgresql on snow leopard, and it looks like I have 
 a cputype problem...

did you just upgrade to Snow Leopard?

If so, did you follow the migration instructions? 
(http://trac.macports.org/wiki/Migration)

 :error:configure File /opt/local/lib/libiconv.dylib contains unexpected 
 architecture cputype.

what does `file /opt/local/lib/libiconv.dylib` say?

   When I try to launch postgresql I get:
 
 dyld: Library not loaded: /usr/local/pgsql/lib/libpq.5.
 dylib
   Referenced from: /usr/local/bin/psql
   Reason: no suitable image found.  Did find:
 /usr/local/pgsql/lib/libpq.5.dylib: mach-o, but wrong architecture
 Trace/BPT trap

stuff in /usr/local can interfere with macports, you should probably move 
/usr/local aside (say to /usr/off) while you build stuff with Macports or 
remove it if you can.

--
Daniel J. Luke  
 
++  
  
| * dl...@geeklair.net * |  

| *-- http://www.geeklair.net -* |  

++  
  
|   Opinions expressed are mine and do not necessarily   |  

|  reflect the opinions of my employer.  |  

++



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


Re: cputype problem on snow leopard

2010-07-20 Thread Ryan Schmidt
On Jul 20, 2010, at 10:26, Anne Poupon wrote:

   I'm trying to install postgresql on snow leopard, and it looks like I have 
 a cputype problem...
 
   The macports log file says:
 version:1
 :debug:main Executing org.macports.main (gettext)
 :debug:main Skipping completed org.macports.fetch (gettext)
 :debug:main Skipping completed org.macports.checksum (gettext)
 :debug:main Skipping completed org.macports.extract (gettext)
 :debug:main Skipping completed org.macports.patch (gettext)
 :msg:main ---  Configuring gettext
 :debug:main Using compiler 'Mac OS X gcc 4.2'
 :debug:configure configure phase started at Tue Jul 20 15:12:19 CEST 2010
 :debug:configure Executing proc-pre-org.macports.
 configure-configure-0
 :error:configure File /opt/local/lib/libiconv.dylib contains unexpected 
 architecture cputype.
 :error:configure This may be a bug in the archcheck portgroup.
 :error:configure Target org.macports.configure returned: unexpected 
 architecture
 :debug:configure Backtrace: unexpected architecture
 while executing
 $pre $targetname
 :info:configure Warning: the following items did not execute (for gettext): 
 org.macports.activate org.macports.configure org.macports.build 
 org.macports.destroot org.macports.install
 :notice:configure Log for gettext is at: 
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_gettext/main.log
 
   When I try to launch postgresql I get:
 
 dyld: Library not loaded: /usr/local/pgsql/lib/libpq.5.
 dylib
   Referenced from: /usr/local/bin/psql
   Reason: no suitable image found.  Did find:
 /usr/local/pgsql/lib/libpq.5.dylib: mach-o, but wrong architecture
 Trace/BPT trap
 
 From the various mailing lists and forum it looks like the problem comes from 
 lipo, which says:
 sh-3.2# lipo -info /opt/local/lib/libform.dylib 
 Non-fat file: /opt/local/lib/libform.dylib is architecture: cputype 16777223 
 cpusubtype 3
 
 If I have understood what I read, lipo should answer x86_64. Question is, how 
 do I get it to give the right answer ?

First, remove /usr/local/bin/psql and anything else in 
/usr/local/{bin,etc,include,lib,libexec,man,sbin,share,var}; these things 
interfere with software built using MacPorts.

Second, indeed it sounds like your lipo doesn't understand the x86_64 
architecture. It sounds a lot like this ticket

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

in which the end result was that the user had apparently somehow replaced 
/usr/bin/lipo with an older version. Please check whether that's the case for 
you as well: run

/usr/bin/lipo -info /usr/lib/libz.dylib

This should say that the file contains the architectures x86_64 i386 ppc7400. 
But if it still mentions cputype 16777223 cpusubtype 3 instead of x86_64, 
then please replace /usr/bin/lipo with a good copy from your backups or from 
your Mac OS X installation media.

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