<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Greetings,<br><br>Instructions for building transcode-1.0.5 include reference to 2 patches ;<br><br><a href="http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-bigdir-1.patch" class="external free" title="http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-bigdir-1.patch" rel="nofollow">http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-bigdir-1.patch</a><br><a href="http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-lzo2-1.patch" class="external free" title="http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-lzo2-1.patch" rel="nofollow">http://svn.cross-lfs.org/svn/repos/patches/transcode/transcode-1.0.5-lzo2-1.patch</a><br><br>These patches do not exist --- previous versions (for transcode-1.0.4) 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 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 wiki page.<br><br>Also, I did notice transcode-1.0.5 compiles fine *without* the '--disable-nuv' switch<br>indicated....which maybe a hangover of previous transcode releases, or else be one<br>of those things related to exactly which gcc version people happen to be using. I first<br>plan to check the transcode binary on a couple of .nuv files to ensure it's all sane and<br>then go back and edit the wiki -- however, if someone is sure this is related to gcc<br>versions, please let me know ; it would change what I write in the wiki....<br><br>Regards,<br><br>Don<br> <br><br /><hr /> <a href='' target='_new'></a></body>
</html>