thorsten wrote these words on 10/26/05 07:58 CST:
Simon Scheiwiller wrote:
the configure script for transcode 0.6.14 looks for the lzo headers in
/usr/include. when i pass the option --with-lzo-includes=/usr/include/lzo,
it looks for the headers in /usr/include/lzo/include.
is there a patch for
Thus spoke Declan Moriarty:
Have you tried copying them all back into /usr/include with this bodge?
cd /usr/include
ln -s ./ lzo
That _should_ make /usr/include = /usr/include/lzo and everyone is
happy.
I'm not sure that works. I installed Transcode 1.0.1 now, and the config
there finds
On 10/25/05, Simon Scheiwiller [EMAIL PROTECTED] wrote:
the configure script for transcode 0.6.14 looks for the lzo headers in
/usr/include. when i pass the option --with-lzo-includes=/usr/include/lzo,
it looks for the headers in /usr/include/lzo/include.
is there a patch for transcode for
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Changing the defaults may not work however. The problem is because
I believe Transcode wants LZO-1 and the OP has LZO-2 installed.
Sometimes, just getting configure to see the changes isn't enough.
There is a reason the LZO maintainer uses
Thus spoke Dan Nicholson:
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Changing the defaults may not work however. The problem is because
I believe Transcode wants LZO-1 and the OP has LZO-2 installed.
Sometimes, just getting configure to see the changes isn't enough.
There is a
Dan Nicholson wrote these words on 10/25/05 17:28 CST:
Ahh. I've never used LZO or even knew there were multiple versions of
it.
I ran into this last time I installed Transcode. Another alternative
for the OP is to install the most recent version of Transcode. They
are up to 1.0.1 as of now.
On 10/25/05, Randy McMurchy [EMAIL PROTECTED] wrote:
Dan Nicholson wrote these words on 10/25/05 17:28 CST:
I ran into this last time I installed Transcode. Another alternative
for the OP is to install the most recent version of Transcode. They
are up to 1.0.1 as of now. You can find it at:
