Bug in faad 2.2.6.1 ports-Makefile
Hi, the Makefile has a bug. It does not compile in current. You have to delete the item LDFLAGS="-L${LOCALBASE}/lib" in the CONFIGURE_ENV variable. If you don't, the linker find an old library. your, Jan
Re: Bug in faad 2.2.6.1 ports-Makefile
On Fri, Jan 16, 2009 at 08:01:47PM +0100, Jan Klemkow wrote: > Hi, > > the Makefile has a bug. > It does not compile in current. > You have to delete the item > > LDFLAGS="-L${LOCALBASE}/lib" > > in the CONFIGURE_ENV variable. > If you don't, the linker find an old library. >From your description it looks like problem with libtool not with the Makefile. If this is libtool problem this is classic issue, and you should just uninstall old faad package, then compile the new one. -- best regards q#
Re: Bug in faad 2.2.6.1 ports-Makefile
Mikolaj Kucharski wrote: On Fri, Jan 16, 2009 at 08:01:47PM +0100, Jan Klemkow wrote: Hi, the Makefile has a bug. It does not compile in current. You have to delete the item LDFLAGS="-L${LOCALBASE}/lib" in the CONFIGURE_ENV variable. If you don't, the linker find an old library. From your description it looks like problem with libtool not with the Makefile. If this is libtool problem this is classic issue, and you should just uninstall old faad package, then compile the new one. That is possible. I don't have experience to know this, but your analyze make more sense than mine. :-) thanks
Re: Bug in faad 2.2.6.1 ports-Makefile
Mikolaj Kucharski wrote: On Fri, Jan 16, 2009 at 08:01:47PM +0100, Jan Klemkow wrote: Hi, the Makefile has a bug. It does not compile in current. You have to delete the item LDFLAGS="-L${LOCALBASE}/lib" in the CONFIGURE_ENV variable. If you don't, the linker find an old library. From your description it looks like problem with libtool not with the Makefile. If this is libtool problem this is classic issue, and you should just uninstall old faad package, then compile the new one. That is possible. I don't have the experience to know this, but your analyze make more sense than mine. :-) thanks