Make no targets specified and no makefile found stop ошибка

I have a make file that contains this code: all: main.o Etudiant.o gcc -lobjc -o program main.o Etudiant.o main.o:main.m Etudiant.h gcc -c main.m Etudiant.o:Etudiant.m Etudiant.h gcc -c

I have a make file that contains this code:

all: main.o Etudiant.o
    gcc -lobjc -o program main.o Etudiant.o
main.o:main.m Etudiant.h
    gcc -c main.m
Etudiant.o:Etudiant.m Etudiant.h
    gcc -c Etudiant.m

When I write this in the shell command:

$make

I got this:

make: **** No targets specified and no makefile found. Stop.

How do I fix this?

Matthew Frederick's user avatar

asked Feb 10, 2011 at 20:44

Malloc's user avatar

9

Mmm… makefiles. Whee.

All that whitespace at the beginning of the line. That has to be tabs. Or Make will barf up a really obscure error. Make sure those are tabs and try again.


See the button on the left side of the keyboard labeled «tab». Delete the spaces and hit that once to insert a tab character.


Try make all. IIRC (been a few years since I’ve had to muck with makefiles) most makes will default to all, but maybe yours isn’t.

Extension doesn’t matter.


Holy Heck! We are all Extra Dense(@bbum mostly so)!

«no Makefile found» means… well.. that Make didn’t even see the makefile. The suggestions to rename the Makefile.m to Makefile are correct. As well, the whole tab vs. whitespace thing is certainly pertinent.

answered Feb 10, 2011 at 20:56

bbum's user avatar

bbumbbum

162k23 gold badges271 silver badges359 bronze badges

8

and no makefile found

If you just type make with no arguments or make all, make will look for a file called Makefile in the current directory. If it’s not there, you get the error you saw. make will not look in subdirectories for Makefile nor will it accept a file called Makefile.m.

answered Feb 11, 2011 at 9:28

JeremyP's user avatar

JeremyPJeremyP

83.4k15 gold badges124 silver badges161 bronze badges

1

In my case, the my makefile had the name MakeFile, changing it to Makefile worked

answered Apr 2, 2022 at 13:08

Namya LG's user avatar

1

Re:
$ Make
Make: * No targets specified and no makefile found. Stop.

I just had this error and found that the Makefile extension (none) had been converted to .bat somewhere along the line.

answered Feb 13, 2014 at 2:32

vJack's user avatar

Just spent a few insanely frustrating moments with this error. My mistake was not all that subtle: I titled the makefile MakeFile not Makefile, so even using the -f Makefile command (forcing the makefile name) still resulted in not-found, because it was MakeFile, not Makefile.

answered Feb 25, 2015 at 22:27

A Questioner's user avatar

In short while I run the make command it says:

nir@nir:~/Downloads/xf86-video-intel-2.17.0$ make
make: *** No targets specified and no makefile found.  Stop.

I looked inside the folder-xf86-video-intel-2.17.0 and there is a file named «Makefile.in»
it supposed to be a in file, right?

αғsнιη's user avatar

αғsнιη

34.6k39 gold badges126 silver badges189 bronze badges

asked Feb 11, 2012 at 16:52

yinon's user avatar

That happens because there is no file named Makefile in that directory. To create that Makefile, you need to execute

$ ./configure

The configure script determines if your system has all the dependencies necessary to compile the application. If a dependency is not found, the configure will fail and the Makefile’s will not be created. To solve that, you must install all the dependencies needed by the application.

The application xf86-video-intel seems to be provided by the xserver-xorg-video-intel package, and its dependencies may be easily installed by running

$ sudo apt-get build-dep xserver-xorg-video-intel

For more information, you might want to read the README or INSTALL files.

answered Feb 11, 2012 at 17:34

Ian Liu Rodrigues's user avatar

1

Just remember that in order for the ./configure file to run you made need a compiler. So do something like sudo apt-get install gcc. then run ./configure again and should work

Mitch's user avatar

Mitch

105k23 gold badges206 silver badges265 bronze badges

answered Aug 8, 2012 at 19:26

DJH's user avatar

DJHDJH

511 silver badge1 bronze badge

2

The make command looks for a file called «Makefile», no extension, not «Makefile.in». Since the file is not found, make does not know what to do, and stops. (The error message is cryptic because in some rare cases, make can guess what to do without an actual Makefile.)

Read the instructions on how to compile your program. It’s likely that you are required to run ./configure, first. This script will create «Makefile» based on your setup and «Makefile.in».

You can temporarily disable the Hebrew locale when looking for help online, just run

LC_ALL=C make

This will give you English messages.

answered Feb 11, 2012 at 17:07

Jan's user avatar

JanJan

3,5434 gold badges33 silver badges44 bronze badges

3

Dont worry..
There are only some packages need to be intalled..
type «sudo synaptic» in terminal and enter..
in search box type «qt4-qmake» and mark for installation.
then same as above search» libqt4-dev» and «libxml2-dev» and do the same mark for installation simultaneously..
then apply without check the download option.
here it is….
Then go to cd netanim directory and type «make clean» and enter,
if it does not work type «qmake NetAnim.pro» and enter, it takes couple of seconds.
then type «make» and enter…
Here its done, it will take less then a minute.
Now in netanim directory type «./NetAnim» and enter.

Here you will see animation interface.
Good luck

answered Oct 2, 2017 at 7:48

Sk Talib's user avatar

0

make sure you have installed this file or

sudo apt install libc6-dev

Now, you need to configure the installation file

./configure
make && make install

answered Jan 22, 2021 at 10:11

MD SHAYON's user avatar

MD SHAYONMD SHAYON

2653 silver badges3 bronze badges

Step 1: Install the Required Dependencies

First, launch the Terminal and run the commands below to install the required dependencies and libraries.

sudo apt install autoconf automake libpcre3-dev libnl-3-dev libsqlite3-dev libssl-dev ethtool build-essential g++ libnl-genl-3-dev libgcrypt20-dev libtool python3-distutils

sudo apt install -y pkg-config

Step 2: Compile and Install

Now, run the commands below (one by one in order) to compile the source code and install Your Repo on your system.
[Before this enter you directory ex: cd folder_name]

sudo autoreconf -i

sudo ./configure --with-experimental --with-ext-scripts

sudo make

sudo make install

I hope this time problem will be solved.

answered Apr 28, 2022 at 11:49

Md Shoriful Islam's user avatar

Whether you’re working with Ubuntu, Debian or Red Hat, you might see an error that reads make: *** No targets specified and no makefile found. Stop. Since this is a general issue related to GNU Make as a whole, you might see it on countless Unix implementations. It means that there isn’t a file called makefile or Makefile in your current working directory. Fortunately, that’s an easy error to fix.

Method 1: Finding a Makefile in the Current Directory

You may wish to try running the make command one more time in the current directory to see if the same error gets thrown at you. This is especially important if you’ve opened a new terminal window and already tried to locate the right directory or if you’ve used the cd command since the last time that you tried to run GNU make.

Assuming that it does, try running the ls or dir command to see what files are in your current directory. You might not be in the right part of the directory tree. If you notice that you see directories that belong in your root / directory or your home ~ directory, then you’ll want to run the cd command to position yourself in the right place to run the make command.

There’s a chance you might find yourself even further afield from where you’re expected to be. In our example, we tried running make from the /var/crash directory and found it didn’t work at all. It can’t be expected to run from here, as the only files in this particular location are from unrelated crash reports.

More than likely, you’re going to want to run your make command from a directory that’s located somewhere inside of your home directory. For instance, if you were building the latest version of GNU nano from source then you’d probably have a directory located at ~/nano-2.9.6 that you could cd to and then run make again. You might want to try running ls once more before you try to make to ensure that there’s a makefile located within the directory for you to build from.

Keep in mind that you’ll need to have configured the installation first. The configure command creates the perfect environment for the GNU compiler to flourish.  If you’re not finding a makefile even in the correct project directory, then run ./configure while you’re still inside of it followed by the make command. If this compiles correctly, then you can install your project with sudo make install, but remember that you don’t want to build anything as root so you’ll never want to run sudo make or anything else outside of installation.

Method 2: Specifying a Custom Makefile

Assuming that fixed the issue, there’s nothing more you need to do. However, there are two special use cases to consider if the previous method didn’t correct your problem. These both involve writing your own makefile for a project that you’ve been configuring by hand.

You can specify a  custom makefile that’s called something other than literally makefile by using the -f option. For instance, if you had a backup makefile called makefile.bak then you might specify it by running make -f makefile.bak from the command line. You may replace makefile.bak with any file name at all and you could include the -i option if you wanted to ignore errors in a custom or outdated makefile while the compiler is running. This usually isn’t recommended, since you’ll probably want to edit your makefile if there’s anything wrong with it.

The other very closely related use case involves a situation where case sensitivity is an issue. The following are all separate files in the Unix way of doing business:

  • Makefile
  • makefile
  • makeFile
  • MakeFile
  • MakefilE

Custom configured programs might not be able to recognize a makefile with odd capitalization. If you’ve handwritten it for a coding project you’re working on, then you’ll probably want to rename it makefile though you could use the -i option to ensure that GNU make is capable of finding it. Remember that if you’ve written everything correctly, then you can still run ./configure from your own project to force it to generate the right environment and avoid this problem, to begin with.

Photo of Kevin Arrows

Kevin Arrows

Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.

I have a problem installing package dionaea.

After I type this:

./configure --with-lcfg-include=/opt/dionaea/include/ 
--with-lcfg-lib=/opt/dionaea/lib/ 
--with-python=/opt/dionaea/bin/python3.1 
--with-cython-dir=/usr/bin 
--with-udns-include=/opt/dionaea/include/ 
--with-udns-lib=/opt/dionaea/lib/ 
--with-emu-include=/opt/dionaea/include/ 
--with-emu-lib=/opt/dionaea/lib/ 
--with-gc-include=/usr/include/gc 
--with-ev-include=/opt/dionaea/include 
--with-ev-lib=/opt/dionaea/lib 
--with-nl-include=/opt/dionaea/include 
--with-nl-lib=/opt/dionaea/lib/ 
--with-curl-config=/opt/dionaea/bin/ 
--with-pcap-include=/opt/dionaea/include 
--with-pcap-lib=/opt/dionaea/lib/ 
--with-glib=/opt/dionaea

and the next step is:

#make

An error message appears:
make: *** No targets specified and no makefile found. Stop.

My directory is /usr/local/src

jjrv's user avatar

jjrv

4,2012 gold badges40 silver badges53 bronze badges

asked Jan 19, 2013 at 9:27

Nani's user avatar

7

make takes a makefile as input. Makefile usually is named makefile or Makefile. The configure command should generate a makefile, so that make could be in turn executed. Check if a makefile has been generated under your working directory.

houbysoft's user avatar

houbysoft

32k24 gold badges98 silver badges154 bronze badges

answered Jan 19, 2013 at 9:33

TieDad's user avatar

TieDadTieDad

8,7714 gold badges32 silver badges57 bronze badges

11

running ./configure should solve your problem.

answered Sep 11, 2014 at 15:41

Meir's user avatar

MeirMeir

1431 silver badge5 bronze badges

2

I got the same error and i fixed it by looking at the solution from this site:

http://trac.macports.org/ticket/40476.

SO did you got any error after running ‘./configure’ ? Maybe something about lacking tclConfig.sh.
If so, instead of running ‘./configure’, you have to search for the tclConfigure.sh first and then put it in the command, in my case, its located in /usr/lib/. And then run:
./configure —-with-tcl=/usr/lib —with-tclinclude=/usr/include

answered May 8, 2014 at 12:08

Phong Nguyen's user avatar

./configure command should generate a makefile, named makefile or Makefile. if in the directory there is no this file, you should check whether the configure command execute success.

in my case, I configure the apr-util:

./configure --prefix=/usr/local/apr-util --with-apr=/usr/local/apr/bin/apr-1-config

because the --with-apr=/usr/local/apr/bin/apr-1-config, the apr did not install yet, so there configure fail, there did not generate the apr‘s /usr/local/apr/bin/apr-1-config.

So I install the apr, then configure the apr-util, it works.

answered Jun 27, 2018 at 3:16

aircraft's user avatar

aircraftaircraft

23.1k24 gold badges87 silver badges161 bronze badges

You had to have something like this:

"configure: error: "Error: libcrypto required."

after your ./configure runs. So you need to resolve noticed dependencies first and then try ./configure once more time and then run make !

Rence's user avatar

Rence

2,8352 gold badges23 silver badges39 bronze badges

answered Oct 19, 2018 at 0:37

Fedulov Oleg's user avatar

I recently ran into this problem while trying to do a manual install of texane’s open-source STLink utility on Ubuntu. The solution was, oddly enough,

make clean
make

Paul Roub's user avatar

Paul Roub

36.2k27 gold badges82 silver badges90 bronze badges

answered Aug 23, 2019 at 18:29

mdhansen's user avatar

mdhansenmdhansen

3843 silver badges16 bronze badges

If after ./configure Makefile.in and Makefile.am are generated and make fail (by showing this following make: *** No targets specified and no makefile found. Stop.) so there is something not configured well, to solve it, first run «autoconf» commande to solve wrong configuration then re-run «./configure» commande and finally «make»

answered Mar 8, 2018 at 12:38

Ben667's user avatar

Delete your source tree that was gunzipped or gzipped and extracted to folder and reextract again. Supply your options again

./configure --with-option=/path/etc ...

Then if all libs are present, your make should succeed.

answered Jan 6, 2020 at 2:41

Vijay Kumar Kanta's user avatar

This may happen if there is any read and write permission denial to the user. Like C:WindowsSystem32 have restricted access and you are cloned and trying to make from such restricted directory.

answered Feb 28, 2020 at 20:33

Kokul Jose's user avatar

Kokul JoseKokul Jose

1,2261 gold badge14 silver badges26 bronze badges

If you create Makefile in the VSCode, your makefile doesnt run. I don’t know the cause of this issue. Maybe the configuration of the file is not added to system. But I solved this way. delete created makefile, then go to project directory and right click mouse later create a file and named Makefile. After fill the Makefile and run it. It will work.

answered Apr 12, 2020 at 15:55

Deniz Babat's user avatar

Try

make clean
./configure --with-option=/path/etc
make && make install

answered Jan 22, 2021 at 10:12

MD SHAYON's user avatar

I think that it can mean that ./configure command failed for some reason, in my case it was due to a missing package. So i have used my OS package manager to install required package (autoconf and autoconf-archive in my case), then it worked.

answered May 31, 2021 at 13:00

16851556's user avatar

1685155616851556

2293 silver badges11 bronze badges

first time try

make clean
make

if these didn’t solve your issue you have to install build packages.

debian base

 apt-get install build-essential libgtk-3-dev

For RHEL/CentOS

sudo yum install gcc glibc glibc-common gd gd-devel -y

answered Feb 28, 2022 at 7:57

hassanzadeh.sd's user avatar

hassanzadeh.sdhassanzadeh.sd

2,8731 gold badge15 silver badges26 bronze badges

Step 1: Install the Required Dependencies

First, launch the Terminal and run the commands below to install the required dependencies and libraries.

sudo apt install autoconf automake libpcre3-dev libnl-3-dev libsqlite3-dev libssl-dev ethtool build-essential g++ libnl-genl-3-dev libgcrypt20-dev libtool python3-distutils

sudo apt install -y pkg-config

Step 2: Compile and Install

Now, run the commands below (one by one in order) to compile the source code and install Your Repo on your system.
[Before this enter you directory ex: cd folder_name]

sudo autoreconf -i

sudo ./configure --with-experimental --with-ext-scripts

sudo make

sudo make install

I hope this time problem will be solved.

answered Apr 28, 2022 at 11:42

Md Shoriful Islam's user avatar

You need to check the output of the configure command.
Mine contained this error:

configure: error: in `/home/ubuntu/build/php-8.0.19':
configure: error: The pkg-config script could not be found or is too old.  Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Then I googled the error and solved it.

answered Jun 7, 2022 at 9:03

Black's user avatar

BlackBlack

17k36 gold badges150 silver badges256 bronze badges

Before running «make» you need to configure your build using «CMake»
Try:
cmake .

answered Jul 12, 2022 at 8:02

Noob's user avatar

NoobNoob

631 silver badge8 bronze badges

Creating Makefile in the VScode did not worked for me. So, delete the make file created in the VS code, go to the project directory and create file add all the commands in it and name it as Makefile and save. Then try to execute it in VS code. It will work. Don’t know why it doesn’t work with VS code.

answered Feb 1 at 5:23

SURAJ ABDAR's user avatar

Unpack the source from a working directory and cd into the file directory as root. Use the commands ./configure then make and make install

answered Feb 12, 2017 at 12:34

Paul's user avatar

1

I have a problem installing package dionaea.

After I type this:

./configure --with-lcfg-include=/opt/dionaea/include/ 
--with-lcfg-lib=/opt/dionaea/lib/ 
--with-python=/opt/dionaea/bin/python3.1 
--with-cython-dir=/usr/bin 
--with-udns-include=/opt/dionaea/include/ 
--with-udns-lib=/opt/dionaea/lib/ 
--with-emu-include=/opt/dionaea/include/ 
--with-emu-lib=/opt/dionaea/lib/ 
--with-gc-include=/usr/include/gc 
--with-ev-include=/opt/dionaea/include 
--with-ev-lib=/opt/dionaea/lib 
--with-nl-include=/opt/dionaea/include 
--with-nl-lib=/opt/dionaea/lib/ 
--with-curl-config=/opt/dionaea/bin/ 
--with-pcap-include=/opt/dionaea/include 
--with-pcap-lib=/opt/dionaea/lib/ 
--with-glib=/opt/dionaea

and the next step is:

#make

An error message appears:
make: *** No targets specified and no makefile found. Stop.

My directory is /usr/local/src

jjrv's user avatar

jjrv

4,2012 gold badges40 silver badges53 bronze badges

asked Jan 19, 2013 at 9:27

Nani's user avatar

7

make takes a makefile as input. Makefile usually is named makefile or Makefile. The configure command should generate a makefile, so that make could be in turn executed. Check if a makefile has been generated under your working directory.

houbysoft's user avatar

houbysoft

32k24 gold badges98 silver badges154 bronze badges

answered Jan 19, 2013 at 9:33

TieDad's user avatar

TieDadTieDad

8,7714 gold badges32 silver badges57 bronze badges

11

running ./configure should solve your problem.

answered Sep 11, 2014 at 15:41

Meir's user avatar

MeirMeir

1431 silver badge5 bronze badges

2

I got the same error and i fixed it by looking at the solution from this site:

http://trac.macports.org/ticket/40476.

SO did you got any error after running ‘./configure’ ? Maybe something about lacking tclConfig.sh.
If so, instead of running ‘./configure’, you have to search for the tclConfigure.sh first and then put it in the command, in my case, its located in /usr/lib/. And then run:
./configure —-with-tcl=/usr/lib —with-tclinclude=/usr/include

answered May 8, 2014 at 12:08

Phong Nguyen's user avatar

./configure command should generate a makefile, named makefile or Makefile. if in the directory there is no this file, you should check whether the configure command execute success.

in my case, I configure the apr-util:

./configure --prefix=/usr/local/apr-util --with-apr=/usr/local/apr/bin/apr-1-config

because the --with-apr=/usr/local/apr/bin/apr-1-config, the apr did not install yet, so there configure fail, there did not generate the apr‘s /usr/local/apr/bin/apr-1-config.

So I install the apr, then configure the apr-util, it works.

answered Jun 27, 2018 at 3:16

aircraft's user avatar

aircraftaircraft

23.1k24 gold badges87 silver badges161 bronze badges

You had to have something like this:

"configure: error: "Error: libcrypto required."

after your ./configure runs. So you need to resolve noticed dependencies first and then try ./configure once more time and then run make !

Rence's user avatar

Rence

2,8352 gold badges23 silver badges39 bronze badges

answered Oct 19, 2018 at 0:37

Fedulov Oleg's user avatar

I recently ran into this problem while trying to do a manual install of texane’s open-source STLink utility on Ubuntu. The solution was, oddly enough,

make clean
make

Paul Roub's user avatar

Paul Roub

36.2k27 gold badges82 silver badges90 bronze badges

answered Aug 23, 2019 at 18:29

mdhansen's user avatar

mdhansenmdhansen

3843 silver badges16 bronze badges

If after ./configure Makefile.in and Makefile.am are generated and make fail (by showing this following make: *** No targets specified and no makefile found. Stop.) so there is something not configured well, to solve it, first run «autoconf» commande to solve wrong configuration then re-run «./configure» commande and finally «make»

answered Mar 8, 2018 at 12:38

Ben667's user avatar

Delete your source tree that was gunzipped or gzipped and extracted to folder and reextract again. Supply your options again

./configure --with-option=/path/etc ...

Then if all libs are present, your make should succeed.

answered Jan 6, 2020 at 2:41

Vijay Kumar Kanta's user avatar

This may happen if there is any read and write permission denial to the user. Like C:WindowsSystem32 have restricted access and you are cloned and trying to make from such restricted directory.

answered Feb 28, 2020 at 20:33

Kokul Jose's user avatar

Kokul JoseKokul Jose

1,2261 gold badge14 silver badges26 bronze badges

If you create Makefile in the VSCode, your makefile doesnt run. I don’t know the cause of this issue. Maybe the configuration of the file is not added to system. But I solved this way. delete created makefile, then go to project directory and right click mouse later create a file and named Makefile. After fill the Makefile and run it. It will work.

answered Apr 12, 2020 at 15:55

Deniz Babat's user avatar

Try

make clean
./configure --with-option=/path/etc
make && make install

answered Jan 22, 2021 at 10:12

MD SHAYON's user avatar

I think that it can mean that ./configure command failed for some reason, in my case it was due to a missing package. So i have used my OS package manager to install required package (autoconf and autoconf-archive in my case), then it worked.

answered May 31, 2021 at 13:00

16851556's user avatar

1685155616851556

2293 silver badges11 bronze badges

first time try

make clean
make

if these didn’t solve your issue you have to install build packages.

debian base

 apt-get install build-essential libgtk-3-dev

For RHEL/CentOS

sudo yum install gcc glibc glibc-common gd gd-devel -y

answered Feb 28, 2022 at 7:57

hassanzadeh.sd's user avatar

hassanzadeh.sdhassanzadeh.sd

2,8731 gold badge15 silver badges26 bronze badges

Step 1: Install the Required Dependencies

First, launch the Terminal and run the commands below to install the required dependencies and libraries.

sudo apt install autoconf automake libpcre3-dev libnl-3-dev libsqlite3-dev libssl-dev ethtool build-essential g++ libnl-genl-3-dev libgcrypt20-dev libtool python3-distutils

sudo apt install -y pkg-config

Step 2: Compile and Install

Now, run the commands below (one by one in order) to compile the source code and install Your Repo on your system.
[Before this enter you directory ex: cd folder_name]

sudo autoreconf -i

sudo ./configure --with-experimental --with-ext-scripts

sudo make

sudo make install

I hope this time problem will be solved.

answered Apr 28, 2022 at 11:42

Md Shoriful Islam's user avatar

You need to check the output of the configure command.
Mine contained this error:

configure: error: in `/home/ubuntu/build/php-8.0.19':
configure: error: The pkg-config script could not be found or is too old.  Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Then I googled the error and solved it.

answered Jun 7, 2022 at 9:03

Black's user avatar

BlackBlack

17k36 gold badges150 silver badges256 bronze badges

Before running «make» you need to configure your build using «CMake»
Try:
cmake .

answered Jul 12, 2022 at 8:02

Noob's user avatar

NoobNoob

631 silver badge8 bronze badges

Creating Makefile in the VScode did not worked for me. So, delete the make file created in the VS code, go to the project directory and create file add all the commands in it and name it as Makefile and save. Then try to execute it in VS code. It will work. Don’t know why it doesn’t work with VS code.

answered Feb 1 at 5:23

SURAJ ABDAR's user avatar

Unpack the source from a working directory and cd into the file directory as root. Use the commands ./configure then make and make install

answered Feb 12, 2017 at 12:34

Paul's user avatar

1

ИМХО DVD с дистрибом — реально рулит ;-)

2eduard_pustobaev: Продолжим?
Я установил из SDL_mixer-1.2.7.tar.gz SDL_mixer:
———————————————————————-
Libraries have been installed in:
/usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR’
flag during linking and do at least one of the following:
— add LIBDIR to the `LD_LIBRARY_PATH’ environment variable
during execution
— add LIBDIR to the `LD_RUN_PATH’ environment variable
during linking
— use the `-Wl,—rpath -Wl,LIBDIR’ linker flag
— have your system administrator add LIBDIR to `/etc/ld.so.conf’

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
———————————————————————-
c0mputer:/home/user/Desktop/SDL_mixer-1.2.7 #

но make так и не проходит в openmortal-0.6

In file included from Audio.cpp:10:
State.h:13:23: error: SDL_mixer.h: No such file or directory
Audio.cpp:19: error: ‘Mix_Chunk’ was not declared in this scope
Audio.cpp:19: error: template argument 2 is invalid
Audio.cpp:19: error: template argument 4 is invalid
Audio.cpp:19: error: invalid type in declaration before ‘;’ token
Audio.cpp:20: error: ‘Mix_Music’ was not declared in this scope
Audio.cpp:20: error: template argument 2 is invalid
Audio.cpp:20: error: template argument 4 is invalid
Audio.cpp:20: error: invalid type in declaration before ‘;’ token
Audio.cpp:21: error: ‘SampleMap’ is not a class or namespace
Audio.cpp:21: error: expected initializer before ‘SampleMapIterator’
Audio.cpp:22: error: ‘MusicMap’ is not a class or namespace
Audio.cpp:22: error: expected initializer before ‘MusicMapIterator’
Audio.cpp: In constructor ‘MszAudio::MszAudio()’:
Audio.cpp:50: error: ‘SDL_version’ was not declared in this scope
Audio.cpp:50: error: expected `;’ before ‘compile_version’
Audio.cpp:51: error: expected initializer before ‘*’ token
Audio.cpp:52: error: ‘compile_version’ was not declared in this scope
Audio.cpp:52: error: ‘MIX_VERSION’ was not declared in this scope
Audio.cpp:56: error: ‘link_version’ was not declared in this scope
Audio.cpp:56: error: ‘Mix_Linked_Version’ was not declared in this scope
Audio.cpp:59: error: ‘MIX_DEFAULT_FREQUENCY’ was not declared in this scope
Audio.cpp:59: error: ‘MIX_DEFAULT_FORMAT’ was not declared in this scope
Audio.cpp:60: error: ‘Mix_OpenAudio’ was not declared in this scope
Audio.cpp:62: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp:70: error: ‘Mix_AllocateChannels’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::LoadSample(const char*, const char*)’:
Audio.cpp:90: error: request for member ‘count’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp:96: error: ‘Mix_Chunk’ was not declared in this scope
Audio.cpp:96: error: ‘poSample’ was not declared in this scope
Audio.cpp:97: error: ‘Mix_LoadWAV’ was not declared in this scope
Audio.cpp:100: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp:104: error: no match for ‘operator[]’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples[sSampleName]’
Audio.cpp: In member function ‘void MszAudio::UnloadSample(const char*)’:
Audio.cpp:111: error: ‘SampleMapIterator’ was not declared in this scope
Audio.cpp:111: error: expected `;’ before ‘it’
Audio.cpp:112: error: request for member ‘end’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp:112: error: ‘it’ was not declared in this scope
Audio.cpp:118: error: ‘it’ was not declared in this scope
Audio.cpp:118: error: ‘Mix_FreeChunk’ was not declared in this scope
Audio.cpp:119: error: request for member ‘erase’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp: In member function ‘void MszAudio::PlaySample(const char*)’:
Audio.cpp:125: error: ‘Mix_Chunk’ was not declared in this scope
Audio.cpp:125: error: ‘poSample’ was not declared in this scope
Audio.cpp:126: error: ‘SampleMapIterator’ was not declared in this scope
Audio.cpp:126: error: expected `;’ before ‘it’
Audio.cpp:127: error: request for member ‘end’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp:127: error: ‘it’ was not declared in this scope
Audio.cpp:132: error: request for member ‘find’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp:133: error: request for member ‘end’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oSamples’, which is of non-class type ‘SampleMap’
Audio.cpp:140: error: ‘it’ was not declared in this scope
Audio.cpp:145: error: ‘Mix_VolumeChunk’ was not declared in this scope
Audio.cpp:148: error: ‘Mix_PlayChannel’ was not declared in this scope
Audio.cpp:150: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::PlayFile(const char*)’:
Audio.cpp:157: error: ‘Mix_Chunk’ was not declared in this scope
Audio.cpp:157: error: ‘poSample’ was not declared in this scope
Audio.cpp:158: error: ‘Mix_LoadWAV’ was not declared in this scope
Audio.cpp:161: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp:164: error: ‘Mix_PlayChannel’ was not declared in this scope
Audio.cpp:166: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp:168: error: ‘Mix_FreeChunk’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::LoadMusic(const char*, const char*)’:
Audio.cpp:181: error: request for member ‘count’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oMusics’, which is of non-class type ‘MusicMap’
Audio.cpp:187: error: ‘Mix_Music’ was not declared in this scope
Audio.cpp:187: error: ‘poMusic’ was not declared in this scope
Audio.cpp:188: error: ‘Mix_LoadMUS’ was not declared in this scope
Audio.cpp:191: error: ‘Mix_GetError’ was not declared in this scope
Audio.cpp:195: error: no match for ‘operator[]’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oMusics[sMusicName]’
Audio.cpp: In member function ‘void MszAudio::UnloadMusic(const char*)’:
Audio.cpp:201: error: ‘MusicMapIterator’ was not declared in this scope
Audio.cpp:201: error: expected `;’ before ‘it’
Audio.cpp:202: error: request for member ‘end’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oMusics’, which is of non-class type ‘MusicMap’
Audio.cpp:202: error: ‘it’ was not declared in this scope
Audio.cpp:208: error: ‘it’ was not declared in this scope
Audio.cpp:208: error: ‘Mix_FreeMusic’ was not declared in this scope
Audio.cpp:209: error: request for member ‘erase’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oMusics’, which is of non-class type ‘MusicMap’
Audio.cpp: In member function ‘void MszAudio::PlayMusic(const char*)’:
Audio.cpp:215: error: ‘MusicMapIterator’ was not declared in this scope
Audio.cpp:215: error: expected `;’ before ‘it’
Audio.cpp:216: error: request for member ‘end’ in ‘((MszAudio*)this)->MszAudio::m_poPriv->MszAudioPriv::m_oMusics’, which is of non-class type ‘MusicMap’
Audio.cpp:216: error: ‘it’ was not declared in this scope
Audio.cpp:224: error: ‘it’ was not declared in this scope
Audio.cpp:224: error: ‘Mix_FadeInMusic’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::FadeMusic(int)’:
Audio.cpp:230: error: ‘Mix_FadeOutMusic’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::SetMusicVolume(int)’:
Audio.cpp:236: error: ‘Mix_VolumeMusic’ was not declared in this scope
Audio.cpp: In member function ‘void MszAudio::StopMusic()’:
Audio.cpp:242: error: ‘Mix_HaltMusic’ was not declared in this scope
Audio.cpp: In member function ‘bool MszAudio::IsMusicPlaying()’:
Audio.cpp:248: error: ‘Mix_PlayingMusic’ was not declared in this scope
make[2]: *** [Audio.o] Error 1
make[2]: Leaving directory `/home/user/openmortal-0.6/src’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/openmortal-0.6′
make: *** [all-recursive-am] Error 2
user@c0mputer:~/openmortal-0.6>

и PPRacer-0.1 не собирается ;-( на make так же заваливается

phys_sim.o: In function `check_item_collection(player_data_t*, pp::Vec3d)’:
phys_sim.cpp:(.text+0x186c): undefined reference to `play_sound(char*, int)’
racing.o: In function `racing_loop(double)’:
racing.cpp:(.text+0x1194): undefined reference to `play_sound(char*, int)’
racing.cpp:(.text+0x11e0): undefined reference to `play_sound(char*, int)’
collect2: ld returned 1 exit status
make[3]: *** [ppracer] Error 1
make[3]: Leaving directory `/home/user/PPRacer-0.1/src’
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/user/PPRacer-0.1/src’
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/PPRacer-0.1′
make: *** [all] Error 2
c0mputer:/home/user/PPRacer-0.1 #

Понравилась статья? Поделить с друзьями:
  • Make no rule to make target install stop ошибка
  • Make modules error 2
  • Main impersonatewrapper cpp error wtsqueryusertoken error 1008
  • Main filter error failed to create video converter
  • Main file data integrity crc error