Run the tests with -v and check that 'svn' prints output in English?
Glen Cooper wrote on Wed, Mar 23, 2011 at 20:45:13 -0700:
> Thanks Mark,
>
> Any idea why including them would cause certain tests to fail?
>
> I'm not sure how significant this is, but I get these messages during my
> build:
>
Thanks Mark,
Any idea why including them would cause certain tests to fail?
I'm not sure how significant this is, but I get these messages during my
build:
msgfmt.exe: de.spo: warning: Charset missing in header.
Message conversion to user's charset will not
work.
msg
Both features only enable the error messages and help to appear in non-English
languages.
Sent from my iPhone
On Mar 23, 2011, at 6:44 PM, Glen Cooper wrote:
> Actually it turns out that if I omit --enable-nls but keep
> --with-libintl=..\svn-win32-libintl all the tests pass.
>
> Is --enable
Actually it turns out that if I omit --enable-nls but keep
--with-libintl=..\svn-win32-libintl
all the tests pass.
Is --enable-nls required for something? Based on the documentation I
thought --enable-nls was somehow linked to --with-libintl. What do I lose
if I don't pass the --enable-nls argum
Hello,
When building subversion with the --with-libintl option, I have a number of
tests that don't pass in the test suite. If I remove the --with-libintl
option and rebuild, all tests pass. I am using the svn-win32libintl package
downloaded from tigris.
Here's my call to gen-make.py. This won
