[Subject Prev][Subject Next][Thread Prev][Thread Next][Date Index][Thread Index]

[hts-users:02444] Re: HTS patch problem


Hi,

are you sure this is the good version of HTK? 3.4.1 and 3.4(.0) both exists. The good one for HTS 2.1 is HTK 3.4 (.0)

Regards,
Sebastien

Le 15/04/2010 05:36, Po-Sen Huang a écrit :
Hi 
My OS is  
cat /proc/version:
Linux version 2.6.18-128.1.14.el5 (mockbuild@xxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Jun 17 06:38:05 EDT 2009

lsb_release -a
LSB Version:    :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: CentOS
Description:    CentOS release 5.3 (Final)
Release:        5.3
Codename:       Final

I did follow INSTALL and README step by step; however, I fail in the "patch -p1 -d . < HTS-2.1_for_HTK-3.4.patch" step.

Thanks

Sincerely,
Po-Sen

On Wed, Apr 14, 2010 at 10:23 PM, Keiichiro Oura <uratec@xxxxxxxxxxxxxxx> wrote:
Hi

What is your OS?
Anyway, read INSTALL and README in HTS-2.1_for_HTK-3.4.tar.bz2 carefully.

Regards,
Keiichiro Oura

2010/4/15 Po-Sen Huang <huang.person@xxxxxxxxx>:
> help
>
>
> Hi
> I want to ask a question, which has been discussed in archives. I have
> problem in install HTS 2.1 patch with HTK 3.4 on linux workstation.
> From archive, I cannot solve 5.1 errors.
>
> 1. Download and install cygwin
> 2. re-run the cygwin install. it will propose a list of program to install,
> I think you should at least select make, gcc and sox if they are not already
> installed.
> 3. download htk-3.4 (and hdecode) *for linux* (not windows) and HTS-2.1 (and
> hts-demo in case you want the demo)
> 4. unzip htk and hts in some cygwin folder (e.g. : open windows explorer and
> unzip them in c:\cygwin\home\mohamed)
> 5. open cygwin environment (it's a linux-like command line). Normally it
> will open with /home/mohamed as its current folder (type "pwd" to check).
> Then follow the step from hts install instruction (patch htk + ./configure +
> make + make install + the make for hdecode (the exact command-line for
> hdecode is given once the first "make" succeeds)).
> 5.1. in case the HTS patch to htk returns some errors, you will have to
> apply manually the part of the patch that didn't work (usually, it's just a
> few line to change in one or two files). This is generally due to windows.
> 5.2. in case the ./configure doesn't work, it's usually due to some missing
> component : return to step 2 and install the missing component
> 6. ...
> 7. enjoy !
>
> There are a lot of failed when I patch the HTS patch
> part of them:
>  #21 FAILED at 4339.
> Hunk #22 succeeded at 5155 with fuzz 2 (offset 557 lines).
> Hunk #23 FAILED at 5409.
> Hunk #24 FAILED at 5518.
> Hunk #25 FAILED at 5559.
> Hunk #26 succeeded at 5294 with fuzz 2.
> Hunk #27 FAILED at 5303.
> Hunk #28 FAILED at 5319.
> Hunk #29 FAILED at 5346.
> Hunk #30 FAILED at 5654.
> Hunk #31 FAILED at 6506.
> Hunk #32 FAILED at 6571.
> Hunk #33 succeeded at 7280 with fuzz 1 (offset 561 lines).
> Hunk #34 FAILED at 7303.
> Hunk #35 succeeded at 6816 (offset 10 lines).
> Hunk #36 succeeded at 7421 (offset 561 lines).
> Hunk #37 FAILED at 7872.
> Hunk #38 FAILED at 7927.
> Hunk #39 FAILED at 8134.
> Hunk #40 FAILED at 8153.
> Hunk #41 FAILED at 8164.
> 34 out of 41 hunks FAILED -- saving rejects to file configure.rej
> patching file configure.ac
> Hunk #1 FAILED at 20.
> Hunk #3 FAILED at 185.
> Hunk #4 succeeded at 256 (offset 10 lines).
> Hunk #6 succeeded at 350 (offset 10 lines).
> 2 out of 6 hunks FAILED -- saving rejects to file configure.ac.rej
> When I open one of the rejects file, I cannot figure out what's the problem
> (not CR/ CR/LF problems)
> For example, in configure.rej, :
>     $ $0 $@
> --- 1028,1034 ----
>   This file contains any messages produced by compilers while
>   running configure, to aid debugging if configure makes a mistake.
> + It was created by HTS $as_me 2.1, which was
>   generated by GNU Autoconf 2.59.  Invocation command line was
>     $ $0 $@
> ***************
> *** 1327,1332 ****
>
>
>   echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5
>   echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6
>   set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y,:./+-,___p_,'`
> --- 1366,1376 ----
>
>
> +
> +
> +
> +
> + # Checks for programs.
>   echo "$as_me:$LINENO: checking whether ${MAKE-make} sets \$(MAKE)" >&5
>   echo $ECHO_N "checking whether ${MAKE-make} sets \$(MAKE)... $ECHO_C" >&6
>   set dummy ${MAKE-make}; ac_make=`echo "$2" | sed 'y,:./+-,___p_,'`
> ***************
> *** 1869,1970 ****
> Thank you for your help
> Po-Sen Huang
> huang.person@xxxxxxxxx
>
>
> --


References
[hts-users:02441] HTS patch problem, Po-Sen Huang
[hts-users:02442] Re: HTS patch problem, Keiichiro Oura
[hts-users:02443] Re: HTS patch problem, Po-Sen Huang