./configure with --enable-mp3lame on Freebsd
I am getting: ERROR: LAME not found I have built and installed Lame already. It is present in /usr/local/lib But somehow the ./configure script is not recognizing it. I would otherwise have used the default Port version of ffmpeg, but I am under the impression that it is much outdated. Thank you, Shark
So no taker on this question? On Dec 23, 2006, at 2:31 PM, Shark Fin Soup wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/ local/lib
But somehow the ./configure script is not recognizing it.
I would otherwise have used the default Port version of ffmpeg, but I am under the impression that it is much outdated.
Thank you,
Shark _______________________________________________ ffmpeg-user mailing list ffmpeg-user at mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Shark Fin Soup wrote:
So no taker on this question?
On Dec 23, 2006, at 2:31 PM, Shark Fin Soup wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
I would otherwise have used the default Port version of ffmpeg, but I am under the impression that it is much outdated.
If that is so, upgrade to latest svn before anything else. Old versions are not supported here.
Thank you,
Shark
-- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
Shark Fin Soup wrote:
So no taker on this question?
On Dec 23, 2006, at 2:31 PM, Shark Fin Soup wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
I would guess configure checks for the header file(s) too. But since most of the relevant info is missing (where you got lame, how you installed it, the configure command, and its output) its only a guess...
I would otherwise have used the default Port version of ffmpeg, but I am under the impression that it is much outdated.
Sorry, I had missed the 'would' and yelled 'upgrade'. Still, you should *not* use old versions.
Thank you,
Shark
-- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
On Sat, 23 Dec 2006 14:31:06 +0700, Shark Fin Soup <shark.fin.soup at mac.com> wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
Does config.err in ffpeg's source tree not give any indication? If LAME is installed correctly (the libraries *AND* the headers) then there's no reason why ffmpeg shouldn't pick it up. -- G. Stewart - godwin.stewart at gmail.com There's no place like ~
From config.err it says: /tmp/ffmpeg-conf--91873-.c:1:23: lame/lame.h: No such file or directory ERROR: LAME not found I have lame.h inside /usr/local/include/lame however. So the ./configure script is not looking for lame.h in the correct place. I tried the exact same thing on Mac OS X, but it's giving me no problem. On Jan 3, 2007, at 5:27 PM, Godwin Stewart wrote:
On Sat, 23 Dec 2006 14:31:06 +0700, Shark Fin Soup <shark.fin.soup at mac.com> wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
Does config.err in ffpeg's source tree not give any indication? If LAME is installed correctly (the libraries *AND* the headers) then there's no reason why ffmpeg shouldn't pick it up.
-- G. Stewart - godwin.stewart at gmail.com
There's no place like ~ _______________________________________________ ffmpeg-user mailing list ffmpeg-user at mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
Shark Fin Soup wrote: Please dont top-post!
From config.err it says:
/tmp/ffmpeg-conf--91873-.c:1:23: lame/lame.h: No such file or directory ERROR: LAME not found
I have lame.h inside /usr/local/include/lame however.
Which, for gcc, is not a standard place for includes. Try configure --extra-cflags=-I/usr/local/include
So the ./configure script is not looking for lame.h in the correct place.
I tried the exact same thing on Mac OS X, but it's giving me no problem.
On Jan 3, 2007, at 5:27 PM, Godwin Stewart wrote:
On Sat, 23 Dec 2006 14:31:06 +0700, Shark Fin Soup <shark.fin.soup at mac.com> wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
Does config.err in ffpeg's source tree not give any indication? If LAME is installed correctly (the libraries *AND* the headers) then there's no reason why ffmpeg shouldn't pick it up.
Greetings, -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux at mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.com/
On Thu, 04 Jan 2007 11:43:49 +0100, Michel Bardiaux <mbardiaux at mediaxim.be> wrote:
I have lame.h inside /usr/local/include/lame however.
Which, for gcc, is not a standard place for includes. Try
It is for Linux, but not for FreeBSD that the OP is using.
configure --extra-cflags=-I/usr/local/include
And: --extra-ldflags=-L/usr/local/lib -- G. Stewart - godwin.stewart at gmail.com Maintainer's Motto: If we can't fix it, it ain't broke.
I forgot to mention that I am using the latest SVN for this purpose. On Jan 3, 2007, at 5:27 PM, Godwin Stewart wrote:
On Sat, 23 Dec 2006 14:31:06 +0700, Shark Fin Soup <shark.fin.soup at mac.com> wrote:
I am getting: ERROR: LAME not found
I have built and installed Lame already. It is present in /usr/local/lib
But somehow the ./configure script is not recognizing it.
Does config.err in ffpeg's source tree not give any indication? If LAME is installed correctly (the libraries *AND* the headers) then there's no reason why ffmpeg shouldn't pick it up.
-- G. Stewart - godwin.stewart at gmail.com
There's no place like ~ _______________________________________________ ffmpeg-user mailing list ffmpeg-user at mplayerhq.hu http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-user
participants (3)
-
godwin.stewart＠gmail.com -
mbardiaux＠mediaxim.be -
shark.fin.soup＠mac.com