Re: [ros-users] ogre_tools broken on CTurtle/Snow leopard

Hi Josh,  The gcc binary file (/usr/bin/gcc-4.2) has not been touched since I first got this machine (May 10th).  I wrote a simple hello world program and compiled it. 'file' told me : a.out: Mach-O 64-bit executable x86_64 So it looks like that isn't the problem? ~Deepak  Josh Faust <jfaust@willowgarage.com>Sent by: ros-users-bounces@code.ros.org09/09/2010 04:59 PMPlease respond toros-users@code.ros.org To   ros-users@code.ros.org cc    bcc   Deepak Ramachandran/HRA/ASC/HONDA Subject   Re: [ros-users] ogre_tools broken on CTurtle/Snow leopard  $ gcc -v Using built-in specs.Target: i686-apple-darwin10Configured with: /var/tmp/gcc/gcc-5664~38/src/configure --disable-checking --enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib --build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- --host=x86_64-apple-darwin10 --target=i686-apple-darwin10 --with-gxx-include-dir=/include/c++/4.2.1Thread model: posixgcc version 4.2.1 (Apple Inc. build 5664)It looks like there's a mismatch somehow between compilers used for various parts of the build.  macports built x86_64 binaries, and some steps of ROS are as well, but then it's trying to link as x86.  The above output seems to imply that gcc itself will output x86 code -- you can test that by writing a simple program and then checking it with "file".Have you made changes to your developer tools recently that might cause something like this?Josh_______________________________________________ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users