I tried to compile the sane-backends from source but getting the following messages after running make, to configure I ran ./configure --enable-avahi BACKENDS='canon genesys test'
make[1]: Leaving directory `/home/.../sane-backends/po'
Making all in testsuite
make[1]: Entering directory `/home/.../sane-backends/testsuite'
Making all in sanei
make[2]: Entering directory `/home/.../sane-backends/testsuite/sanei'
run 'make check' to run tests
make[2]: Leaving directory `/home/.../sane-backends/testsuite/sanei'
Making all in tools
make[2]: Entering directory `/home/.../sane-backends/testsuite/tools'
Use 'make check' to run the tests.
run 'make check' to run tests
make[2]: Leaving directory `/home/..../sane-backends/testsuite/tools'
make[2]: Entering directory `/home/.../sane-backends/testsuite'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory `/home/..../sane-backends/testsuite'
Use 'make test' to run the tests.
make[1]: Leaving directory `/home/.../sane-backends/testsuite'
make[1]: Entering directory `/home/.../sane-backends'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/home/.../sane-backends'
whats wrong with all-am???
Okay, I got it, make says what it does, if it has nothing to do, it just says "nothing to do", thanks to all.
Related
I am using the command make for compiling source codes. However, the command always issue this error
Makefile:10: Makefile_compiler_HOSTNAME: No such file or directory
make: *** No rule to make target `Makefile_compiler_HOSTNAME'. Stop.
where HOSTNAME is the hostname of my computer. It seems like make is defaulted to search for the file Makefile_compiler_HOSTNAME before the file Makefile.
Is there any way to set the default behaviour of make back?
I am trying to compile the kernel android-x86 ( ics-x86 branches )
I followed this tutorial(1) , but I also paid attention to those link(2)
(1) https://groups.google.com/forum/#!topic/android-x86/x5aBNnK4Ols
(2) http://www.android-x86.org/documents/customizekernel
when I enter the terminal with this command (1)
$ make -C kernel O=/work/config/.config xconfig
I get this :
make: Entering directory '/home/base3/work/a_source/kernel'
/bin/sh: 1: cd: can't cd to /work/config/.config
Makefile:121: * output directory "/work/config/.config" does not exist. Stop.
make: Leaving directory '/home/base3/work/a_source/kernel'**
If I do (2)
$ make -C kernel O=$OUT/obj/kernel ARCH=x86 menuconfig
I get :
make: Entering directory '/home/base3/work/a_source/kernel'
/bin/sh: 1: cd: can't cd to /home/base3/work/a_source/out/target/product/generic_x86/obj/kernel
Makefile:121: * output directory "/home/base3/work/a_source/out/target/product/generic_x86/obj/kernel" does not exist. Stop.
make: Leaving directory '/home/base3/work/a_source/kernel'**
I am in Debian jessie x86-64 , and I want to compile the android kernel to install on a notebook . Android (ics-x86) does not recognize my sata hdd ( SIS chipset )
please do not tell me to use another version of android
I would be very grateful for any hint that would make me go ahead
thanks
I can get past this phase using ubuntu 14.04 lts. Using debian jessie, I did not get it, because it made several errors
I used the command in ubuntu:
$Make -C kernel O=$OUT/obj/kernel ARCH=x86 xconfig
I'm working a class assignment from machine learning course. We are given a hmm.tar file which contains c++ implementation of hidden markov models.
In the read me file the following was given.
To compile and test the program,
1) extract the code:
tar -xf hmm.tar
2) compile the programs:
make all
at the second step the output from the terminal is make: *** No rule to make target 'all'. Stop
I'm using windows10 OS and running cygwin terminal.
Please help me to sort this problem out. Here's the
Makefile
I'm guessing the tar file has files inside a subdirectory. You probably just need to make sure you're in the directory that has the Makefile, and then run make:
tar -xf hmm.tar
cd __somewhere_
make all
to help you know where the Makefile is, you could use:
tar tf hmm.tar | grep -i makefile
Since cygwin returns make: *** No rule to make target 'all'. Stop, it seems that make is installed correctly.
As such, it has to be two other things:
Either the make file inside the.tar is missing, or
there are syntactical errors present in the make file
In attempt to build sip from source packages, I have the infinite loop on a building step. I run make.exe and it takes the following steps unitl I press Ctrl+Brake:
cd sipgen
make
make[1]: Entering directory `C:/sip'
cd sipgen
make
make[2]: Entering directory `C:/sip'
cd sipgen
make
make[3]: Entering directory `C:/sip'
cd sipgen
make
make[4]: Entering directory `C:/sip'
...........................................
cd sipgen
make
make[n]: Entering directory `C:/sip'
^C
Makefile in root directory contains code below:
all:
cd sipgen
$(MAKE)
#cd ..
cd siplib
$(MAKE)
#cd ..
install:
cd sipgen
$(MAKE) install
#cd ..
cd siplib
$(MAKE) install
#cd ..
#if not exist C:\Python34\Lib\site-packages mkdir C:\Python34\Lib\site-packages
copy /y sipconfig.py C:\Python34\Lib\site-packages\sipconfig.py
copy /y C:\sip\sipdistutils.py C:\Python34\Lib\site-packages\sipdistutils.py
clean:
cd sipgen
$(MAKE) clean
#cd ..
cd siplib
$(MAKE) clean
#cd ..
Do you know the reasons?
Can I solve this issue, or it impossible on Windows?
PS. Sorry for my awful English
I just copy the answer of another question
If you use python configure.py, the generated Makefiles are actually nmake makefiles. nmake is Microsoft's equivalent to make. You can run it by invoking nmake in a Visual Studio command prompt, if you have that installed.
For building with mingw, you have to indicate that you want to use that particular platform when creating the makefiles, as follows:
python configure.py --platform win32-g++
After that, invoking make works fine.
https://stackoverflow.com/a/16051239
If you use the PyQt windows installer the sip package will be installed too!
I have a working makefile that builds with mingw32. Now i renamed that makefile to Makefile.w32 (source -> http://pastie.org/319964)
Now i have a Makefile with the following. The problem is, it does not build my source
all:
make mingw32
clean:
#echo "causes an infinite loop -> make mingw32 clean"
mingw32:
#echo "yeahhhhhhhhh"
make Makefile.w32
mingw32-clean:
#echo "mingw clean"
make Makefile.w32 clean
result:
> "make"
make mingw32
make[1]: Entering directory `/c/nightly/test'
yeahhhhhhhhh
make Makefile.w32
make[2]: Entering directory `/c/nightly/test'
make[2]: Nothing to be done for `Makefile.w32'.
make[2]: Leaving directory `/c/nightly/test'
make[1]: Leaving directory `/c/nightly/test'
It seems to me it doesn't like Makefile.w32 extension. I dont understand why it isn't building. It;s obviously getting to my "make Makefile.w32" line.
"make Makefile.w32" is looking for a target named Makefile.w32, not a make file by that name. To run make and tell it to read the make file "Makefile.w32", use the -f switch:
make -f Makefile.w32
Edit: Incidentally, why do you launch a separate instance of make in the "all" target, if all you want is for "all" to depend on the "mingw32" target in the same make file? It'd be better, IMHO, to declare it as a dependent target instead:
all: mingw32
Likewise with "clean" and "mingw32-clean":
clean: mingw32-clean
You can use cmake to generate makefiles. It should work on most platforms.