#60 Can not run make

closed-works-for-me
Sean Morrison
3
2010-09-29
2010-08-10
ZhenHua Lin
No

Hello everyone, I download the source for 7.16.8 for my IA32 machine. However, when I try to run make, OS gave me this feed back
"make: *** No targets specified and no makefile found. Stop."
When I look into the directory, I did not find the file named "make" like other sources. Hence, I want to ask how I can get solve this problem.

Regard

Discussion

  • Sean Morrison
    Sean Morrison
    2010-08-12

    It sounds like you're not very familiar with the command line, so you're going to have to be very specific about what command you ran and what was printed back to you. "make" is not a file, it's a program that will run and build the BRL-CAD sources. It's not something that will be in our source directory, it's installed elsewhere on your system.

    That said, you apparently ran make but the configure step failed. Please provide a *complete* transcript of your terminal session so we can figure out what went wrong. You can save the terminal transcript to a file and attach it to this tracker item as an attachment.

    Cheers!
    Sean

     
  • Sean Morrison
    Sean Morrison
    2010-08-12

    • assigned_to: nobody --> brlcad
    • priority: 5 --> 3
    • status: open --> pending-works-for-me
     
  • ZhenHua Lin
    ZhenHua Lin
    2010-08-16

    Hi, thanks for the reply

    There are too much information from the terminal session. I can not pull all of them out. But the configure fail at step 6, compiler check

    checking if compiler and linker recognize -pipe... yes
    checking if compiler and linker recognize -fno-strict-aliasing... yes
    checking if compiler and linker recognize -fno-common... yes
    checking if compiler and linker recognize -fexceptions... yes
    checking if compiler recognizes -ftemplate-depth-50... yes
    checking if linker recognizes -Wl,-search_paths_first -Wnewline-eof... no
    checking if compiler and linker recognize -ggdb3... yes
    checking if compiler and linker recognize -D_FORTIFY_SOURCE=2... yes
    checking if compiler and linker recognize -w... yes
    checking if compiler and linker recognize -w... yes
    checking if compiler and linker recognize -w -pedantic -W -Wall -Werror -Wno-long-long... yes
    checking single-precision floating point tolerance... 1.08420217248550443401e-19
    checking double-precision floating point tolerance... 1.08420217248550443401e-19
    checking whether floats conform to IEEE 754... no
    checking whether doubles conform to IEEE 754... no
    configure: }}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}
    configure: WARNING: The floating point implementation does not seem to be IEEE 754
    configure: WARNING: compliant. The behavior of htond and htonf may be incorrect.
    configure: {{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{{
    checking for an ANSI C-conforming const... yes
    checking for inline... inline
    checking for working volatile... yes
    checking whether byte ordering is bigendian... no
    checking size of int... 4
    checking size of long... 4
    checking size of long long... 8
    checking size of void *... 4
    checking gcc compiler and flags for sanity... yes
    checking g++ compiler and flags for sanity... no
    configure: }}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}
    configure: error: *** compiler cannot create working executables, check config.log ***

    I think I got IEEE 754 and g++ installed, but it does not recolonize those compilers

    Regard
    Z. L

     
  • ZhenHua Lin
    ZhenHua Lin
    2010-08-16

    • status: pending-works-for-me --> open-works-for-me
     
  • Sean Morrison
    Sean Morrison
    2010-08-16

    • status: open-works-for-me --> pending-works-for-me
     
  • Sean Morrison
    Sean Morrison
    2010-08-16

    You're failing the g++ sanity test, so something basic is missing. Attach your config.log file to this tracker and I can see why. Otherwise, try deleting your cache files:

    rm -rf *cache*

    And run configure again.

     
    • status: pending-works-for-me --> closed-works-for-me
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).