From: Henry F. M. <mo...@pa...> - 2005-10-10 16:42:23
|
Jonathan, Getting errors at make stage: /usr/bin/libtool: internal link edit command failed make[3]: *** [liboctaviz.dylib] Error 1 make[2]: *** [default_target] Error 2 make[1]: *** [default_target_Common] Error 2 make: *** [default_target] Error 2 Do I ignore and proceed with 'make install'? Henry N.B. Complete output after 'g' and then 'make': [~] -bash-2.05b 519$ cd /Users/hfm/Desktop/octaviz-0.4.0/ [~/Desktop/octaviz-0.4.0] -bash-2.05b 520$ ls CMakeCCompiler.cmake CMakeSystem.cmake Examples Imaging Rendering CMakeCXXCompiler.cmake CMakeTmp Filtering Makefile Scripts CMakeCache.txt COPYING Graphics Parallel Testing CMakeLists.txt CVS Hybrid Patented Wrapping CMakeOutput.log Common IO README cmake.check_cache [~/Desktop/octaviz-0.4.0] -bash-2.05b 521$ make Building dependencies. cmake.depends... -- Loading VTK CMake commands -- Loading VTK CMake commands - done cmake.depends is up-to-date /Users/hfm/Desktop/octaviz-0.4.0/Wrapping: building default_target Building dependencies. cmake.depends... Building object file vtkWrapOctave.o... Building object file vtkParse.tab.o... Building executable /Users/hfm/Desktop/octaviz-0.4.0/Wrapping/vtkWrapOctave... /Users/hfm/Desktop/octaviz-0.4.0/Common: building default_target Building dependencies. cmake.depends... Building object file octaviz.o... Building shared library liboctaviz.dylib... ld: warning multiple definitions of symbol _xerbla_ /usr/local/lib/octave-2.1.71/liboctinterp.dylib(single module) definition of _xerbla_ /usr/local/lib/octave-2.1.71/libcruft.dylib(single module) definition of _xerbla_ ld: octaviz.o illegal reference for -dynamic code (section difference reference from section (__TEXT,__eh_frame) relocation entry (12) to symbol: __ZN6Array2IdED0Ev defined in dylib: /usr/local/lib/octave-2.1.71/liboctave.dylib) ld: octaviz.o illegal reference for -dynamic code (section difference reference from section (__TEXT,__eh_frame) relocation entry (16) to symbol: __ZN6Array2IdED1Ev defined in dylib: /usr/local/lib/octave-2.1.71/liboctave.dylib) ld: octaviz.o illegal reference for -dynamic code (section difference reference from section (__TEXT,__eh_frame) relocation entry (124) to symbol: __ZN5ArrayISsEaSERKS0_ defined in dylib: /usr/local/lib/octave-2.1.71/liboctave.dylib) /usr/bin/libtool: internal link edit command failed make[3]: *** [liboctaviz.dylib] Error 1 make[2]: *** [default_target] Error 2 make[1]: *** [default_target_Common] Error 2 make: *** [default_target] Error 2 [~/Desktop/octaviz-0.4.0] -bash-2.05b 522$ ********************************************* on 10/9/05 8:36 PM, Jonathan Stickel at jjs...@sb... wrote: > Henry > > OK, this looks better now. The 'g' option doesn't appear until you > press 'c'. > > Jonathan > > > Henry F. Mollet wrote: >> Jonathan and Marius, >> That's what I tried following >> 1. Run ccmake in the directory where you want the object and executable >> files to be placed (build directory). If the source directory is not >> the same as this build directory, you have to specify it as an argument on >> the command line. >> But was getting nowhere with lot's of errors. >> >> Now, following your directions and running ccmake from within the sources >> directory I made progress: >> >> CMAKE_BUILD_TYPE * >> CMAKE_INSTALL_PREFIX */usr/local >> CXX_COMPILER_PCH *g++-3.4 >> EXECUTABLE_OUTPUT_PATH * >> LIBRARY_OUTPUT_PATH * >> OCTAVE_CONFIG */usr/local/bin/octave-config >> USE_PREC_HEADERS *OFF >> VTK_DIR */sw/lib/vtk >> CMAKE_BACKWARDS_COMPATIBILITY 1.8 >> >> >> CMAKE_BUILD_TYPE: Choose the type of build, options are: >> None(CMAKE_CXX_FLAGS or CMAKE_C_FLAGS used) Debug Release RelWithDebInfo >> MinSizeRel. >> Press [enter] to edit option >> CMake Version 1.8 - patch 3 >> Press [c] to configure >> Press [h] for help Press [q] to quit without generating >> Press [t] to toggle advanced mode (Currently Off) >> >> So this looks good as far as I can tell and the next step would be to press >> 'g' but there is *no* g option. I tried it anyway but nothing happened. I >> was not in Edit mode because h produced the help screen. So I used toggle >> to check advance mode and got: >> > <snip> >> >> >> on 10/9/05 4:33 PM, Jonathan Stickel at jjs...@sb... wrote: >> >> >>> Henry >>> >>> Basically, "ccmake ." (or "cmake .") is equivalent to "./configure >>> [options]". Instead of autogen tools, cmake tools are used. >>> >>> What is your trouble with "ccmake ." exactly? Just change your >>> directory in your shell to wherever you expanded the Octaviz source. >>> Then run >>> >>> $ ccmake . >>> >>> You should get a ascii text menu that displays various options, among >>> them the directory where vtk libs are detected (e.g. /usr/local/lib/vtk) >>> and the install parent directory (e.g. /usr). Press 'c' to configure >>> and 'g' to generate. If there are problems (e.g vtk libs can't be >>> found), then you will get errors. If you get errors, let us know what >>> they are and maybe we can help. >>> >>> Jonathan >>> >>> P.S. There is a "octaviz-help" list, but only 2 people are currently >>> subscribed (Henry and myself). This thread is on the octave help list >>> so that Henry can get Macintosh specific help, which I don't know much >>> about. >>> >>> >>> Henry F. Mollet wrote: >>> >>>> Marius, >>>> No configure script: >>>> [~] -bash-2.05b 507$ cd /Users/hfm/Desktop/octaviz-0.4.0/ >>>> [~/Desktop/octaviz-0.4.0] -bash-2.05b 508$ ./configure --help|less >>>> -bash: ./configure: No such file or directory >>>> [~/Desktop/octaviz-0.4.0] -bash-2.05b 509$ ls >>>> CMakeLists.txt CVS Examples Graphics IO >>>> Parallel README Scripts Wrapping >>>> COPYING Common Filtering Hybrid Imaging >>>> Patented Rendering Testing >>>> >>>> According to Octaviz website instructions for installation are: >>>> Octaviz has been developed for Linux with X-Window System and OpenGL but it >>>> should work on any platform that supports X and VTK. Octaviz should work >>>> under CygWin too but this port requires more testing. Any feedback >>>> regarding >>>> Octaviz in CygWin is welcome. >>>> >>>> You'll need octave 2.1.53 or later and VTK CVS to build octaviz. To compile >>>> octaviz, run "ccmake ." in the root directory of the source tree, then >>>> "make" and finally "make install". >>>> >>>> To build octaviz under CygWin: >>>> CUT, more complicated. >>>> >>>> I got stuck at run "ccmake ." >>>> Henry >>>> >>>> >>>> on 10/9/05 12:18 PM, Marius Schamschula at ma...@ph... wrote: >>>> >>>> >>>> >>>>> Henry, >>>>> >>>>> Does octaviz have a configure script? If so, cd into the untared >>>>> directory and run >>>>> >>>>> ./configure --help|less >>>>> >>>>> to see what variables and options can be set. You can either set the >>>>> environmental variables ahead of time, i.e. under bash something like >>>>> >>>>> CPPFLAGS=-I/some/strange/place/include >>>>> esport CPPFLAGS >>>>> >>>>> or when running configure, something like >>>>> >>>>> ./configure CPPFLAGS=-I/some/strange/place/include >>>>> >>>>> Note however: the second variant generally fails if any variable has >>>>> more than one argument. >>>>> >>>>> On Oct 9, 2005, at 1:23 PM, Henry F. Mollet wrote: >>>>> >>>>> >>>>> >>>>>> Marius, >>>>>> Thanks, but I don't think that I had a choice about where Fink is >>>>>> putting >>>>>> things or I would have installed Cmake and VTK in /usr/local/bin where >>>>>> octave-2.1.71 is located (instead of in /sw/bin). Using Fink I was >>>>>> able to >>>>>> install VTK quickly to find out what is was all about. >>>>>> >>>>>> Where is the 'fooling around' to be done? >>>>>> I.e. with >>>>>> CPPFLAGS=-I/some/strange/place/include \ and >>>>>> and >>>>>> LDFLAGS=-L/some/strange/place/lib >>>>>> (above copied from a google search for 'LDFLAGS' to find out what it >>>>>> is.) >>>>>> >>>>>> I have checked the CMakeLists.txt file in the untared octaviz-0.4.0 >>>>>> directory but could not find LDFLAGS nor CPPFLAGS. I surmise it may be >>>>>> way >>>>>> over my head to accomplish something that passes information to the >>>>>> assembler and linker during the build process. >>>>>> Henry >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> on 10/8/05 1:24 PM, Marius Schamschula at ma...@ph... >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Henry, >>>>>>> >>>>>>> Using finK, or for that DarwinPorts, cause your packages to be >>>>>>> installed outside of the normal search path (i.e. /sw for fink and >>>>>>> /opt/local for DP). There is a reason why I generally build things >>>>>>> into >>>>>>> /usr/local... >>>>>>> >>>>>>> You'll have to fool around with LDFLAGS and CPPFLAGS to point things >>>>>>> into the right direction. >>>>>>> >>>>>>> On Oct 8, 2005, at 3:03 PM, Henry F. Mollet wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> I checked SourceForge.net Project: octaviz and found nothing re >>>>>>>> octaviz >>>>>>>> installation on Mac. Hopefully I'll get a hint here what I should try >>>>>>>> next. >>>>>>>> >>>>>>>> Jonathan was correct: I was able to use Fink to install CMake1.8.3-1 >>>>>>>> and >>>>>>>> VTK-py23 4.4.0-5. Many examples/demos are working using: >>>>>>>> "vtk -f filename" or >>>>>>>> "python -i filename" at the shell prompt. >>>>>>>> So far so good. >>>>>>>> >>>>>>>> Now I tried to install octaviz-0.4.0 from source and it failed (see >>>>>>>> below) >>>>>>>> I've also tried to install in /usr/local/bin but it also failed >>>>>>>> (errors not >>>>>>>> included). >>>>>>>> Henry >>>>>>>> >>>>>>>> [/sw/bin] -bash-2.05b 523$ ccmake /users/hfm/Desktop/octaviz-0.4.0 >>>>>>>> >>>>>>>> CMake Error: Error in cmake code at >>>>>>>> /sw/share/CMake/Modules/CMakeDetermineSystem.cmake:71: >>>>>>>> FILE Internal CMake error when trying to open file: >>>>>>>> /sw/bin/CMakeOutput.log >>>>>>>> for writting. >>>>>>>> >>>>>>>> CMake Error: Could not open file for write in copy operatation >>>>>>>> /sw/bin/CMakeSystem.cmake.tmp >>>>>>>> >>>>>>>> CMake Error: Error in cmake code at >>>>>>>> /sw/share/CMake/Modules/CMakeDetermineCCompiler.cmake:54: >>>>>>>> FILE Internal CMake error when trying to open file: >>>>>>>> /sw/bin/CMakeOutput.log >>>>>>>> for writting. >>>>>>>> >>>>>>>> CMake Error: Could not open file for write in copy operatation >>>>>>>> /sw/bin/CMakeCCompiler.cmake.tmp >>>>>>>> >>>>>>>> CMake Error: Error in cmake code at >>>>>>>> /sw/share/CMake/Modules/CMakeDetermineCXXCompiler.cmake:47: >>>>>>>> FILE Internal CMake error when trying to open file: >>>>>>>> /sw/bin/CMakeOutput.log >>>>>>>> for writting. >>>>>>>> >>>>>>>> CMake Error: Could not open file for write in copy operatation >>>>>>>> /sw/bin/CMakeCXXCompiler.cmake.tmp >>>>>>>> >>>>>>>> CMake Error: Error in cmake code at >>>>>>>> /sw/share/CMake/Modules/CMakeTestCCompiler.cmake:8: >>>>>>>> FILE Internal CMake error when trying to open file: >>>>>>>> /sw/bin/CMakeTmp/testCCompiler.c for writting. >>>>>>>> >>>>>>>> CMake Error: Failed to create CMakeList file for >>>>>>>> /sw/bin/CMakeTmp/CMakeLists.txt >>>>>>>> >>>>>>>> CMake Error: Error in cmake code at >>>>>>>> /sw/share/CMake/Modules/CMakeTestCCompiler.cmake:16: >>>>>>>> FILE Internal CMake error when trying to open file: >>>>>>>> /sw/bin/CMakeError.log >>>>>>>> for writting. >>>>>>>> >>>>>>>> The C compiler "gcc" is not able to compile a simple test program. >>>>>>>> It fails with the following output: >>>>>>>> >>>>>>>> >>>>>>>> CMake will not be able to correctly generate this project. >>>>>>>> >>>>>>>> CMake Error: Unable to open cache file for save. >>>>>>>> /sw/bin/CMakeCache.txt >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> on 10/4/05 9:20 PM, Jonathan Stickel at jjs...@sb... >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Henry >>>>>>>>> >>>>>>>>> I do not work on a Mac, and so my help will be limited. I am also >>>>>>>>> the >>>>>>>>> only other subscriber to the octaviz list at the moment! You might >>>>>>>>> also >>>>>>>>> try the octaviz web forums (in the sourceforge site). >>>>>>>>> >>>>>>>>> I haven't tried anonymous cvs checkout in awhile, but it should work >>>>>>>>> according to the sourceforge instructions. You could also try the >>>>>>>>> last >>>>>>>>> release, octaviz-0.4. This you can download directly as a tarball. >>>>>>>>> >>>>>>>>> You will definitely need cmake and vtk (>vtk-4.4) to compile >>>>>>>>> octaviz. >>>>>>>>> I >>>>>>>>> do not know if you can get these through fink or not. If not, >>>>>>>>> install >>>>>>>>> them from source from the vtk website (vtk.org). >>>>>>>>> >>>>>>>>> HTH, >>>>>>>>> Jonathan >>>>>>>>> >>>>>>>>> >>>>>>>>> Henry F. Mollet wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>>>> From Octaviz website at >>>>>>>>>>> http://octaviz.sourceforge.net/index.php?page=build >>>>>>>>>> >>>>>>>>>> You'll need octave 2.1.53 or later and VTK CVS to build octaviz. To >>>>>>>>>> compile >>>>>>>>>> octaviz, run "ccmake ." in the root directory of the source tree, >>>>>>>>>> then >>>>>>>>>> "make" and finally "make install". >>>>>>>>>> >>>>>>>>>> [/Develop] -bash-2.05b 533$ cvs -d >>>>>>>>>> :pserver:ano...@pu...:/cvsroot/VTK login >>>>>>>>>> Logging in to >>>>>>>>>> :pserver:ano...@pu...:2401/cvsroot/VTK >>>>>>>>>> CVS password: >>>>>>>>>> PAM authenticate error: User not known to the underlying >>>>>>>>>> authentication >>>>>>>>>> module >>>>>>>>>> cvs login: authorization failed: server public.kitware.com rejected >>>>>>>>>> access >>>>>>>>>> to /cvsroot/VTK for user anonymous >>>>>>>>>> >>>>>>>>>> Password is supposed to be VTK but it does not work. I need help >>>>>>>>>> from >>>>>>>>>> somebody who installed octaviz on Mac OS 10.4.2. >>>>>>>>>> >>>>>>>>>> Also, it it not potentially problematic to create a directory >>>>>>>>>> "/Develop" >>>>>>>>>> when I already have a directory "/Developer"? >>>>>>>>>> >>>>>>>>>> Also, VTK requires Cmake. I'm not sure if I have it. >>>>>>>>>> [/Develop] -bash-2.05b 534$ locate CMake >>>>>>>>>> [/Develop] -bash-2.05b 535$ locate cmake >>>>>>>>>> /sw/fink/10.4-transitional/stable/main/finkinfo/devel/cmake.info >>>>>>>>>> /sw/fink/10.4-transitional/stable/main/finkinfo/devel/cmake.patch >>>>>>>>>> /sw/fink/10.4-transitional/unstable/main/finkinfo/devel/cmake.info >>>>>>>>>> /sw/fink/10.4-transitional/unstable/main/finkinfo/devel/cmake.patch >>>>>>>>>> /usr/X11R6/bin/ccmakedep >>>>>>>>>> /usr/X11R6/bin/gccmakedep >>>>>>>>>> /usr/X11R6/lib/X11/doc/html/ccmakedep.1.html >>>>>>>>>> /usr/X11R6/lib/X11/doc/html/gccmakedep.1.html >>>>>>>>>> /usr/X11R6/man/man1/ccmakedep.1 >>>>>>>>>> /usr/X11R6/man/man1/gccmakedep.1 >>>>>>>>>> [/Develop] -bash-2.05b 536$ >>>>>>>>>> >>>>>>>>>> Can somebody please help. >>>>>>>>>> Henry >>>>>>>>>> >>>>>>> >>>>>>> Marius >>>>>>> -- >>>>>>> Marius Schamschula, Alabama A & M University, Department of Physics >>>>>>> >>>>>>> The Center for Hydrology Soil Climatology and Remote Sensing >>>>>>> http://optics.physics.aamu.edu/ - http://www.physics.aamu.edu/ >>>>>>> http://wx.aamu.edu/ - http://www.aamu.edu/hscars/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------- >>>>>>> Octave is freely available under the terms of the GNU GPL. >>>>>>> >>>>>>> Octave's home on the web: http://www.octave.org >>>>>>> How to fund new projects: http://www.octave.org/funding.html >>>>>>> Subscription information: http://www.octave.org/archive.html >>>>>>> ------------------------------------------------------------- >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------- >>>>>> Octave is freely available under the terms of the GNU GPL. >>>>>> >>>>>> Octave's home on the web: http://www.octave.org >>>>>> How to fund new projects: http://www.octave.org/funding.html >>>>>> Subscription information: http://www.octave.org/archive.html >>>>>> ------------------------------------------------------------- >>>>>> >>>>>> >>>>> >>>>> Marius >>>>> -- >>>>> Marius Schamschula Webmaster >>>>> >>>>> The Huntsville Macintosh Users Group >>>>> www.hmug.org >>>>> >>>>> webmaster at hmug dot org marius at schamschula dot com >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> ------------------------------------------------------------- >>> Octave is freely available under the terms of the GNU GPL. >>> >>> Octave's home on the web: http://www.octave.org >>> How to fund new projects: http://www.octave.org/funding.html >>> Subscription information: http://www.octave.org/archive.html >>> ------------------------------------------------------------- >>> >> >> >> >> > > > > ------------------------------------------------------------- > Octave is freely available under the terms of the GNU GPL. > > Octave's home on the web: http://www.octave.org > How to fund new projects: http://www.octave.org/funding.html > Subscription information: http://www.octave.org/archive.html > ------------------------------------------------------------- > |