yum groupinstall "Development Tools"

or

yum install gcc gcc-c++ kernel-devel

You are going about installing ffmpeg the wrong way .. make would not work because you are not in the right directory

Easy way for installation add new repo at /etc/yum.repos.d

nano -w /etc/yum.repos.d/dag.repo

Inset

[dag]
name=Dag RPM Repository for Red Hat Enterprise Linux
baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag
gpgcheck=1
enabled=1

Then Install

yum install ffmpeg ffmpeg-devel

its as easy as that ... to install ffmpeg-php

wget /path/to/this/file/ffmpeg-php-0.5.2.1.tbz2

tar -xjf ffmpeg-0.5.2.1.tbz2

phpize

./configure
make
make install  

Can you see where you use make ??? After extracting the compressed file

Lastly PHP.INI

nano /etc/php.ini

[ffmpeg]
extension=ffmpeg.so

Sometimes you need to create new ffmpeg.ini file and php reads it automatically .. this depends on your confifuration

I hope this helps

Thanks

:)

What you describe is one of the ways, if a library you build does not ship with something like foo.pc.in for example.

The convention is that, if the Makefile (or the build system) allows for configuring library directory via an environment variable, then it's being used.

So as a first step, identify if a given Makefile has something like that. E.g. this example allows to do multilib build (e.g. x64_64 and i686) off the same spec file that has:

%make_install PREFIX=%{_prefix} INSTALL_LIB=%{buildroot}%{_libdir}

No patching required in this case.

A cmake-based project can be told to about the right library directory, like so:

%cmake .. -DCMAKE_INSTALL_PREFIX="%{_prefix}" \
  -DCMAKE_INSTALL_LIBDIR="%{_libdir}"

So as a last resort only, if the Makefile doesn't allow for any customization of the library directory, you would do the patching.

Although, this might get tedious to create such patches. So you can put sed to work in the %prep section.

You may be able to do:

PYTHON != which python2.7 || which python

This works in gnu make 4.1 and bmake 20160220-2+b1

But why bother? It's honestly probably less trouble to install gnu make and use it, or to write a configure script that generates the Makefile for you with PYTHON properly defined.