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

Yeah I noticed that too....I suspect it's because I just copied over the Ogre framework from the disk image instead of compliling from sources. This is the method suggested in the wiki but maybe it doesnt work on Snow leopard. I'll try to compile from source in a couple of days but I have to work on  some other stuff now.  Meanwhile, has anyone had any success getting Cturtle + nav_view/rviz working on snow leopard?  ~Deepak Josh Faust <jfaust@willowgarage.com>Sent by: ros-users-bounces@code.ros.org09/09/2010 09:18 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  Somehow "-arch i386" is getting inserted into your link line:/usr/bin/c++   -I/opt/local/include/wx-2.8 -O2 -g -dynamiclib -headerpad_max_install_names -F/Users/Deepak/ros/stacks/visualization_common/ogre/ogre/lib -framework Ogre -framework Carbon -dylib_file /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib -Wl,-rpath,/Users/Deepak/ros/stacks/visualization_common/ogre/ogre/lib -Wl,-rpath,/Users/Deepak/ros/ros/core/rosconsole/lib -Wl,-rpath,/Users/Deepak/ros/ros/core/roslib/lib -Wl,-rpath,/Users/Deepak/ros/ros/core/roslib/lib -Wl,-rpath,/Users/Deepak/ros/ros/tools/rospack/lib -pthread -o ../lib/libogre_tools.dylib -install_name /Users/Deepak/ros/stacks/visualization_common/ogre_tools/lib/libogre_tools.dylib CMakeFiles/ogre_tools.dir/src/ogre_tools/initialization.o CMakeFiles/ogre_tools.dir/src/ogre_tools/point_cloud.o CMakeFiles/ogre_tools.dir/src/ogre_tools/object.o CMakeFiles/ogre_tools.dir/src/ogre_tools/shape.o CMakeFiles/ogre_tools.dir/src/ogre_tools/grid.o CMakeFiles/ogre_tools.dir/src/ogre_tools/arrow.o CMakeFiles/ogre_tools.dir/src/ogre_tools/axes.o CMakeFiles/ogre_tools.dir/src/ogre_tools/billboard_line.o CMakeFiles/ogre_tools.dir/src/ogre_tools/camera_base.o CMakeFiles/ogre_tools.dir/src/ogre_tools/fps_camera.o CMakeFiles/ogre_tools.dir/src/ogre_tools/orbit_camera.o CMakeFiles/ogre_tools.dir/src/ogre_tools/ortho_camera.o CMakeFiles/ogre_tools.dir/src/ogre_tools/movable_text.o CMakeFiles/ogre_tools.dir/src/ogre_tools/wx_ogre_render_window.o CMakeFiles/ogre_tools.dir/src/ogre_tools/orthographic.o CMakeFiles/ogre_tools.dir/src/ogre_tools/stl_loader.o -L/Users/Deepak/ros/ros/core/rosconsole/lib -L/Users/Deepak/ros/ros/core/roslib/lib -L/Users/Deepak/ros/ros/tools/rospack/lib -L/Users/Deepak/ros/ros/3rdparty/gtest/gtest/lib -lrosconsole -lboost_thread-mt -llog4cxx -lroslib -lrospack -lrosstack -L/opt/local/lib -L/opt/local/lib -arch i386 -L/opt/local/lib -framework IOKit -framework Carbon -framework Cocoa -framework System -framework QuickTime -framework OpenGL -framework AGL -lwx_macu-2.8 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lpangoft2-1.0 -lgio-2.0 -lXext -lXfixes -lcairo -lpixman-1 -lpng12 -lXrender -lX11 -lXau -lXdmcp -lpango-1.0 -lm -lfontconfig -lexpat -lfreetype -lz -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lintl -liconv -framework OpenGL -framework AGLI'm not sure where that would be coming from unfortunately -- not sure what else to tell you, but if you can find out where that's coming from you've probably found the source of your problem.JoshOn Thu, Sep 9, 2010 at 8:20 PM,  <DRamachandran@hra.com> wrote:Josh,the output from make is attached.  ~DeepakJosh Faust <jfaust@willowgarage.com>Sent by: ros-users-bounces@code.ros.org09/09/2010 07:15 PMPlease respond toros-users@code.ros.orgTo   ros-users@code.ros.orgcc   bcc   Deepak Ramachandran/HRA/ASC/HONDASubject   Re: [ros-users] ogre_tools broken on CTurtle/Snow leopard  Well, according to these warnings you're getting:ld: warning: in CMakeFiles/bin/stl_to_mesh.dir/src/stl_to_mesh/stl_to_mesh.o, file was built for unsupported file format which is not the architecture being linked (i386)ld: warning: in /Users/Deepak/ros/ros/core/rosconsole/lib/librosconsole.dylib, file was built for unsupported file format which is not the architecture being linked (i386)ld: warning: in /opt/local/lib/libboost_thread-mt.dylib, file was built for unsupported file format which is not the architecture being linked (i386)*something* is attempting to link as i386, even though those files were compiled for x86_64.  I don't know why that would be.  Can you paste the output from:roscd ogre_toolsmake cleanVERBOSE=1 make?JoshOn Thu, Sep 9, 2010 at 6:44 PM,  <DRamachandran@hra.com> wrote: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_64So it looks like that isn't the problem?~DeepakJosh Faust <jfaust@willowgarage.com>Sent by: ros-users-bounces@code.ros.org09/09/2010 04:59 PMPlease respond toros-users@code.ros.orgTo   ros-users@code.ros.orgcc   bcc   Deepak Ramachandran/HRA/ASC/HONDASubject   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_______________________________________________ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users_______________________________________________ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users_______________________________________________ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users_______________________________________________ros-users mailing listros-users@code.ros.orghttps://code.ros.org/mailman/listinfo/ros-users