Welcome new user! You can search existing questions and answers without registering, but please register to post new questions and receive answers. Note that due to large amounts of spam attempts, your first three posts will be manually moderated, so please be patient.
Because of un-manageable amounts of spam despite our use of CAPTCHAs, email authorization, and other tools, we have discontinued this forum (see the 700k+ registered users with validated email addresses at right?). Please email us any questions or post bug reports and feature requests on GitHub at https://github.com/jevois -- The content below remains available for future reference.
Welcome to JeVois Tech Zone, where you can ask questions and receive answers from other members of the community.

No rule to make target 'mrproper'

0 votes

I've completed the following sections from the install instructions without error:


EASY INSTALL OPTION

ADVANCED: Install necessary packages on your host computer

ADVANCED: Download JeVois source code

ADVANCED: Installing OpenCV 3.2.0 on a Linux host system

Compiling JeVois library and base apps

Compiling JeVois library and base apps for host computer


However, it fails in:

ADVANCED: Compiling the jevois-sdk from scratch

at 'make mrproper' with response:

make: *** No rule to make target 'mrproper'.  Stop.

I'm running Ubuntu 16.10 64-bit.  Any ideas what I could have missed?


Full disclosure - I did try (probably naively) section:

Compiling JeVois library and base apps for hardware platform

immediately after section:

EASY INSTALL OPTION

That failed (probably rightfully so) with the following output:


-- JEVOIS_LDEBUG_ENABLE: OFF
-- JEVOIS_TRACE_ENABLE: OFF
-- JEVOIS_USE_SYNC_LOG: OFF
-- JEVOIS_LOG_TO_FILE: OFF
-- HOST_IS_RPI3: OFF
-- JeVois version 1.0
-- JEVOIS_SRC_ROOT: /home/russ/jevois
-- JEVOIS_PLATFORM: ON
-- JEVOIS_VENDOR: JeVois
-- JEVOIS_MODULES_TO_BUILDROOT: OFF
-- Install prefix for executables: /home/russ/jevois/../jevois-sdk/out/sun8iw5p1/linux/common/buildroot/target/usr
-- Host path to jevois modules root: /home/russ/jevois/../jevois-sdk/out/sun8iw5p1/linux/common/buildroot/target/jevois
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:131 (project):
  The CMAKE_C_COMPILER:

    /home/russ/jevois/../jevois-sdk/out/sun8iw5p1/linux/common/buildroot/host/usr/bin/arm-buildroot-linux-gnueabihf-gcc

  is not a full path to an existing compiler tool.

  Tell CMake where to find the compiler by setting either the environment
  variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
  the compiler, or to the compiler name if it is in the PATH.


CMake Error at CMakeLists.txt:131 (project):
  The CMAKE_CXX_COMPILER:

    /home/russ/jevois/../jevois-sdk/out/sun8iw5p1/linux/common/buildroot/host/usr/bin/arm-buildroot-linux-gnueabihf-g++

  is not a full path to an existing compiler tool.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.


-- Configuring incomplete, errors occurred!
See also "/home/russ/jevois/pbuild/CMakeFiles/CMakeOutput.log".
See also "/home/russ/jevois/pbuild/CMakeFiles/CMakeError.log".

asked Apr 1, 2017 in Programmer Questions by franz (1,080 points)
edited Apr 15, 2017 by franz

1 Answer

+1 vote

mrproper is a deep cleanup target for either buildroot or the Linux kernel.

did you cd to buildroot or to linux-3.4 before you issued it? If so, just ignore the error and proceed with the next steps.

for the failure of compiling jevois, yes it fails because it does not find a cross-compiler. That one gets compiled as part of building the jevois-sdk, so you should try to complete the sdk steps first.

answered Apr 3, 2017 by JeVois (46,580 points)
That worked!  
It did take me a few minutes to realize what name I should enter to the prompt - "Enter device name for microSD card: ".  As mentioned in the install instructions in the "Flashing it all to microSD" section, it should be something like /dev/sdX.  On my system, it was /dev/sdb.
...