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

Bug#663916: New phonetisaurus package available

* Giulio Paci <giuliopaci@gmail.com>, 2012-10-21, 15:04:
What does --fst_field_separator exactly do? In my experiments it did not affect phonetisaurus-align in any way.
Unfortunately I do not know most of the options of this program. I asked upstream about this option.
Upstream replied that these flags are automatically added by openfst:
Some of them affect the behaviour of functions that are not used by phonetisaurus-align. However he does not know how to hide those inherited options (and I do not know as well) without rewriting all the flags parsing code.
Do you know how to hide them?

No idea, sorry.

Is it mandatory to identify "possibly useless" flags and to hide them?

I understand that removing/hiding unneeded option might be infeasible, but I would expect that these no-ops are documented as such in the manual page (or alternative: that they are not documented in the manpage at at all).

There are some warnings in the build log:
| /usr/bin/make  -C src CFLAGS="-g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" CXXFLAGS="-g -O2 -fPIE -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-fPIE -pie -Wl,-z,relro -Wl,-z,now"  THIRD_PARTIES_INCLUDE="-I3rdparty/utfcpp" -k clean
| make[1]: Entering directory `/build/phonetisaurus-DN3moq/phonetisaurus-0.6/src'
| rm ../phonetisaurus-g2p ../phonetisaurus-align ../phonetisaurus-arpa2fst *.o
| rm: cannot remove `../phonetisaurus-g2p': No such file or directory
| rm: cannot remove `../phonetisaurus-align': No such file or directory
| rm: cannot remove `../phonetisaurus-arpa2fst': No such file or directory
| rm: cannot remove `*.o': No such file or directory
| make[1]: *** [clean] Error 1
| make[1]: Leaving directory `/build/phonetisaurus-DN3moq/phonetisaurus-0.6/src'
| make: [makefile-clean] Error 2 (ignored)

The above indicates two problem:
1) Upstream "make clean" is not idempotent: it fails it there's nothing to clean. Replacing "rm" with "rm -f" should fix this issue. 2) cdbs doesn't ignore errors from "make clean". This was reported in #441020 over 5 years ago. (Sigh...)

There's a warning about debian/copyright_hints not being up-to-date.

There's also a few dozens of compiler warnings. Is upstream aware of them?

Jakub Wilk

Reply to: