Install of RC on SuSE 10.1

Discussion in 'Parallels Workstation for Windows and Linux' started by pentastarch, Sep 20, 2006.

  1. pentastarch

    pentastarch Bit poster

    Messages:
    2
    I have been unable to install parallels on my SuSE 10.1 box. It is a core 2 duo running x86-64 SMP kernel. the error file is enclosed below.

    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets ${MAKE}... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for gcc... gcc
    checking for C compiler default output... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking for g++... no
    checking for c++... no
    checking for gpp... no
    checking for aCC... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl... no
    checking for FCC... no
    checking for KCC... no
    checking for RCC... no
    checking for xlC_r... no
    checking for xlC... no
    checking whether we are using the GNU C++ compiler... no
    checking whether g++ accepts -g... no
    checking dependency style of g++... none
    checking whether make sets ${MAKE}... (cached) yes
    checking build system type... x86_64-suse-linux
    checking host system type... x86_64-suse-linux
    checking for ld used by GCC... /usr/x86_64-suse-linux/bin/ld
    checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
    checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependant libraries... pass_all
    checking command to parse /usr/bin/nm -B output... ok
    checking how to run the C preprocessor... gcc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for ranlib... ranlib
    checking for strip... strip
    checking for objdir... .libs
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking if gcc supports -c -o file.lo... yes
    checking if gcc supports -fno-rtti -fno-exceptions... yes
    checking whether the linker (/usr/x86_64-suse-linux/bin/ld) supports shared libraries... yes
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking whether -lc should be explicitly linked in... no
    creating libtool
    checking for gcc option to accept ANSI C... none needed
    checking for inline... inline
    checking Check for primary OS type... Linux
    checking Linux kernel version... 2.6.x
    checking kernel sources... ok (/lib/modules/2.6.16.21-0.21-smp/source)
    checking abnormal 2.4.20 remap_page_range... remap_page_range not need vma struct
    checking freezing kthreads patch... no
    checking scheduling problems... schedule has sleep calculations
    checking mmu_cr4_features address... cat: /proc/ksyms: No such file or directory
    cat: /lib/modules/2.6.16.21-0.21-smp/build/System.map: No such file or directory
    cat: /boot/System.map.2.6.16.21-0.21-smp: No such file or directory
    cat: /usr/src/linux/System.map: No such file or directory
    Not found VT-x can't work
    checking for x86 platform... configure: error: x86 platform is not supported

    I have been reading the forums and there is a thread saying I have to patch the Kernel. Is this the only way to get it installed on SuSE 10.1 or have others succeeded without this step? Any help gratefully accepted.

    Nick
     
  2. Ryan Ware

    Ryan Ware Bit poster

    Messages:
    7
    I'm wondering if this might be an x86-64 vs. x86 issue. I have it installed in SuSE 10.1 and had no problem with the install. However, I did this on a plain 32-bit system. In addition, one thing that might have made a difference is that in /usr/src/linux I have done a make cloneconfig and make scripts.
     
  3. dglock2

    dglock2 Hunter

    Messages:
    107
    Code:
    checking dependency style of gcc... gcc3
    checking for g++... no
    checking for c++... no
    checking for gpp... no
    checking for aCC... no
    checking for CC... no
    checking for cxx... no
    checking for cc++... no
    checking for cl... no
    checking for FCC... no
    checking for KCC... no
    checking for RCC... no
    checking for xlC_r... no
    checking for xlC... no
    checking whether we are using the GNU C++ compiler... no
    

    Your problem is you don't have a compiler installed, as the error message states. Install it through yast and you will be fine.

    don
     
  4. David Corrales

    David Corrales Hunter

    Messages:
    189
    You're talking about the c++ compiler. He does have a C compiler (gcc) installed.
     
  5. pentastarch

    pentastarch Bit poster

    Messages:
    2
    It is not the compiler. I have installed gcc c++ andd I still get the a similar error report.

    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for gawk... gawk
    checking whether make sets ${MAKE}... yes
    checking whether to enable maintainer-specific portions of Makefiles... no
    checking for gcc... gcc
    checking for C compiler default output... a.out
    checking whether the C compiler works... yes
    checking whether we are cross compiling... no
    checking for suffix of executables...
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for style of include used by make... GNU
    checking dependency style of gcc... gcc3
    checking for g++... g++
    checking whether we are using the GNU C++ compiler... yes
    checking whether g++ accepts -g... yes
    checking dependency style of g++... gcc3
    checking whether make sets ${MAKE}... (cached) yes
    checking build system type... x86_64-suse-linux
    checking host system type... x86_64-suse-linux
    checking for ld used by GCC... /usr/x86_64-suse-linux/bin/ld
    checking if the linker (/usr/x86_64-suse-linux/bin/ld) is GNU ld... yes
    checking for /usr/x86_64-suse-linux/bin/ld option to reload object files... -r
    checking for BSD-compatible nm... /usr/bin/nm -B
    checking whether ln -s works... yes
    checking how to recognise dependant libraries... pass_all
    checking command to parse /usr/bin/nm -B output... ok
    checking how to run the C preprocessor... gcc -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking dlfcn.h usability... yes
    checking dlfcn.h presence... yes
    checking for dlfcn.h... yes
    checking for ranlib... ranlib
    checking for strip... strip
    checking for objdir... .libs
    checking for gcc option to produce PIC... -fPIC
    checking if gcc PIC flag -fPIC works... yes
    checking if gcc static flag -static works... yes
    checking if gcc supports -c -o file.o... yes
    checking if gcc supports -c -o file.lo... yes
    checking if gcc supports -fno-rtti -fno-exceptions... yes
    checking whether the linker (/usr/x86_64-suse-linux/bin/ld) supports shared libraries... yes
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking whether -lc should be explicitly linked in... no
    creating libtool
    checking for gcc option to accept ANSI C... none needed
    checking for inline... inline
    checking Check for primary OS type... Linux
    checking Linux kernel version... 2.6.x
    checking kernel sources... ok (/lib/modules/2.6.16.21-0.21-smp/source)
    checking abnormal 2.4.20 remap_page_range... remap_page_range not need vma struct
    checking freezing kthreads patch... no
    checking scheduling problems... schedule has sleep calculations
    checking mmu_cr4_features address... cat: /proc/ksyms: No such file or directory
    cat: /lib/modules/2.6.16.21-0.21-smp/build/System.map: No such file or directory
    cat: /boot/System.map.2.6.16.21-0.21-smp: No such file or directory
    cat: /usr/src/linux/System.map: No such file or directory
    Not found VT-x can't work
    checking for x86 platform... configure: error: x86 platform is not supported


    The last bit of the log appears to be the relevant bit. I wounder if the "checking freezing kthreads patch" is the kernal patch needed for successful installation, any ideas?

    Nick
     
  6. constant

    constant Forum Maven

    Messages:
    1,010
    .
    pentastarch,

    You are using an smp kernel. This will not work with Parallels.
    .
     
  7. ms @ parallels

    ms @ parallels Parallels Team

    Messages:
    87
    Problem is in the x86_64 arch.

    checking for x86 platform... configure: error: x86 platform is not supported

    This message mean: x86_64 platform is not supported.

    Thank you, we will fix this typo.

    PS: SMP Kernels are supported by Parallels.
     
  8. constant

    constant Forum Maven

    Messages:
    1,010
    .
    Sorry.
    .
     

Share This Page