New Japanese PO file for 'm4' (version 1.4o)

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'm4' has been submitted
by the Japanese team of translators.  The file is available at:

    http://translationproject.org/latest/m4/ja.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/m4/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/m4.html

If any question arises, please contact the translation coordinator.

bugs-Please see it once

Re: bugs-Please see it once

On 10/25/2010 03:04 PM, Rajan Modi wrote:
>
>   ===============================
> 6 of 99 tests failed
> (11 tests were not run)
> See tests/test-suite.log
> Please report to bug-m4 <at> gnu.org

Thanks for the report.  However, you omitted some crucial details.

What system is this on?  What were the six tests that failed?

> rajan <at> scoe-3e6045b113 ~/ns-allinone-2.28/m4-1.4.15
> $ make install
> git: not found

Hmm - it would be nice if we could find the source of that spurious 
message and squelch it.

> while executing make installcheck i got following errors
> ./stackovf.test: skipping test, no stack overflow support detected in m4
> Skipped checks were:
>    ./125.changeword ./126.changeword ./127.changeword ./128.changeword ./129.chan
> geword ./130.changeword ./stackovf.test
> All checks successful

That was not an error, just a list of skipped tests (because you didn't 
configure with the expensive --enable-changeword) and a warning that if 
you want stack overflow detection, you should probably consider 
installing GNU libsigsegv.

But your just-built m4 tested flawlessly; which means the earlier tests 
that you reported failures for are probably signs of gnulib testsuite 
weaknesses.

--

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Re: bugs-Please see it once

[please keep the list in the loop, and please don't top-post on 
technical lists]

On 10/25/2010 04:05 PM, Rajan Modi wrote:
>
> i saw C:\cygwin\home\rajan\ns-allinone-2.28\gmp-4.2.2\tests
> but there is no such test-suite.log..

Rather, I was asking about m4-1.4.15/tests/test-suite.log, or at a very 
minimum, the six FAIL: lines from 'make check' output in your m4 build 
directory.

> I am using cygwin 2.28...

No you aren't, because there's no such cygwin version.  However, I 
tested a build of m4 1.4.15 on cygwin 1.7.7, and could not reproduce any 
failures (although I did see several skips due to cygwin's incomplete 
locale support), so I'm not sure why you are getting different behavior.

>
> I am trying to include package called libecc-0.12.1..
>
> but error was thrown called gmp 4.2 required..
> so downloaded the package  gmp-4.2.2..
>
> again to install that another error occured called
> checking for times... yes
> checking for vsnprintf... yes
> checking whether vsnprintf works... yes
> checking whether sscanf needs writable input... no
> checking for struct pst_processor.psp_iticksperclktick... no
> checking for suitable m4... configure: error: No usable m4 in $PATH or /usr/5bin
>   (see config.log for reasons).

Cygwin currently includes pre-built m4 1.4.15 and gmp 4.3.1 as optional 
development packages; rather than compiling these packages from source, 
and having to repeat any porting efforts yourself, have you considered 
just using the pre-built binaries already available from cygwin?  If you 
need more help on how to use cygwin's setup.exe to install gmp and m4, 
then ask on the cygwin mailing lists.

> please help me sir..i am new to cygwin and  ns2

Cygwin questions are better directed to the cygwin mailing list, cygwin 
AT cygwin DOT com.

--

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

older cygwin failures [was: bugs-Please see it once]

[please keep the list in the loop, and quit top-posting, or I will be 
unlikely to reply further]

On 10/25/2010 04:23 PM, Rajan Modi wrote:
>
> i m using ns 2.28

That doesn't help me.  I need to know what release of cygwin you are 
running on; the output of 'uname -a' and './build-aux/config.guess' are 
more valuable than telling me that you are trying to build ns 2.28.

>   and sir i am sending u the contents of log file..

Thank you.  These failures are all related to gnulib tests, so I'm 
adding the gnulib list in cc:.

> FAIL: test-fopen-safer.exe (exit: 134)
> ======================================
> test-fopen.h:48: assertion failed

That one is testing for a particular errno value from 
fopen("file/","r"), which should fail; older cygwin had a bug where it 
would mistakenly succeed, but current cygwin does not have this bug. 
Since cygwin is actively maintained, and more importantly, open source, 
it is more efficient for gnulib to focus only on current releases and 
fix bugs in cygwin itself, rather than maintaining lots of ports in 
gnulib to work around older cygwin bugs.  Therefore, my recommendation 
is to upgrade to the latest cygwin version rather than making packages 
like m4 install workarounds for bugs that have been fixed in the 
meantime.  The cygwin list is a better resource if you have questions on 
how to perform this upgrade.

> FAIL: test-fopen.exe (exit: 134)
> ================================
> test-fopen.h:48: assertion failed
> FAIL: test-lseek.sh (exit: 1)
> =============================
> test-lseek.c:42: assertion failed
> Signal 6

> FAIL: test-open.exe (exit: 134)
> ===============================
> test-open.h:46: assertion failed
> FAIL: test-sigaction.exe (exit: 139)
> ====================================
> test-sigaction.c:75: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
> test-sigaction.c:79: assertion failed
>        4 [sig] test-sigaction 2088 handle_threadlist_exception:
> handle_threadlist_exception called with threadlist_ix -1
>    46213 [sig] test-sigaction 2088 handle_threadlist_exception:
> handle_threadlist_exception called with threadlist_ix -1
> FAIL: test-symlink.exe (exit: 134)
> ==================================
> test-symlink.h:47: assertion failed

I did not look closer at these other failures, but suspect that they are 
all in the same category of using an out-of-date version of cygwin. 
Again, telling me what system you are using will go a long way in 
deciphering these failure reports, and deciding whether it was a recent 
enough version of cygwin for me to downgrade from my 1.7.7 installation 
and figure out workarounds for gnulib to use.

--

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org