<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Greets,<br><br>> Date: Tue, 28 Oct 2008 16:01:40 +0000<br>> From: zarniwhoop<br>> To: clfs-dev@<br>> Subject: Re: [Clfs-dev] CBLFS - transcode-1.0.5<br>> <br>> On Mon, Oct 27, 2008 at 10:40:12PM -0400, Joe Ciccone wrote:<br>> > db m wrote:<br>> > > Greetings,<br>> > ><br>> > > Instructions for building transcode-1.0.5 include reference to 2 patches ;<br>> > ><br>> > > http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-bigdir-1.patch<br>> > > http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-lzo2-1.patch<br>> > ><br>> > > These patches do not exist --- previous versions (for transcode-1.0.4)<br>> > > are sitting<br>> > > in the repo instead ; these still apply fine to transcode-1.0.5<br>> > ><br>> > > Rather than edit this page and make versioning information appear<br>> > > disjointed,<br>> > > can someone with access to the patches repo please check this and perhaps<br>> > > change filenames as appropriate? If not, let me know and I'll edit the<br>> > > wiki page.<br>> > ><br>> > Blame the last person that made the edit. Chances are the patches will<br>> > work with the new version, without looking at what they do and at the<br>> > code I couldn't tell you.<br>><br>> To throw a spanner in the works, I built a pure64 x86_64 a month<br>> ago, but using gcc-4.2.4 [ that was a diversion to see if my evince<br>> problems had gone ]. Transcode-1.0.6 built without _any_ patches<br>> (although I did have to make some seds because of the recent ffmpeg<br>> snapshot I used) - details buried within my somewhat long notes<br>> http://www.linuxfromscratch.org/~ken/new-desktop-late-2008-first-attempt.gz<br>><br>Seems like we use the same toolbox -- I've been looking at transcode-1.0.6 too ;)<br>Going by changelogs and other tidbits on the transcoding website, releases<br>previous to 1.0.6 were source compatible with both lzo/lzo2 (dependant on<br>configure time switches), but as of 1.0.6 lzo2 (only?) is now the way to go. Hence,<br>the lzo2 patch is no longer needed for 1.0.6 at all, but I've still to investigate the<br>'bigdir-1' patch to see whether it's still applicable. I'll get to that over the next <br>couple of days. Thanks for the link to your notes, I'll check those later as well...<br>...and yes, you need seds to get around ffmpeg ongoing changes.<br><br> > > > Also, I did notice transcode-1.0.5 compiles fine *without* the<br>> > > '--disable-nuv' switch<br>> <br>> I needed this on 1.0.6, otherwise the build craps out in nuv/.<br>> What architecture/size are you building ?<br><br>clfs-1.1.0_x86_64 multilib, iirc it was a 64bit build<br><br>> <br>> This is one of those av packages where things mostly have to be<br>> specified, so I'll mention my configure used<br>> ./configure --prefix=/usr --enable-freetype2 --enable-ogg \<br>> --enable-vorbis --enable-a52 --enable-theora --enable-libxml2 \<br>> --disable-nuv<br>> <br>> As I mentioned in my notes, this isn't something I've ever found<br>> time to use, so there might still be issues with my build.<br>> <br>> ¢en<br>> -- <br><br>Okay...thanks for all of this. Ability to handle nuppelvideo is not going<br>to affect too many people - mythtv is the only app I regularly use which<br>defaultly transcodes to .nuv (and it uses it's own fork of transcode to do<br>so), but I'm still checking this lot out. As time permits, I think I'll fix my gaze<br>on transcode-1.0.6 and make sure (test) that the build is all sane. If it all<br>checks out, I'll update the wiki as appropriate. <br><br><br>Regards,<br><br>Don<br><br><br /><hr /> <a href='' target='_new'></a></body>
</html>