[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #10, sr#110502 (group m4): Try to do what I wrote in https://savannah.gnu.org/support/?110502#comment6 . ___ Reply to this item at: __

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #9, sr#110502 (group m4): I'm opened on any suggestions which I can try to do. ___ Reply to this item at: ___ Message sent via Sav

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #8, sr#110502 (group m4): In my last comment, I said "you will need to dig a bit by your own." If you cannot do this or don't want to do this, we should close this ticket, with resolution "works for me". ___ Reply to this

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #7, sr#110502 (group m4): Any update? 🤔 ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org/

[sr #110502] 1.4.19: test suite is failing

Update of sr #110502 (project m4): Priority: 5 - Normal => 3 - Low ___ Follow-up Comment #6: Your CFLAGS and LDFLAGS contain exotic options that are not available on machines I have access to. T

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #5, sr #110502 (project m4): [comment #4 comment #4:] > Please tell us how to reproduce the issue: > * which operating system? Linux x86_64 > * which values of CC, CPPFLAGS, CFLAGS, LDFLAGS used at configure time? [tkloczko@barrel SPECS]$ rpm -E %set_build_flags CFLAGS="-O2

[sr #110502] 1.4.19: test suite is failing

Update of sr #110502 (project m4): Status:None => Need Info ___ Follow-up Comment #4: Please tell us how to reproduce the issue: * which operating system? * which values of CC, CPPFLAGS,

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #3, sr #110502 (project m4): [comment #2 comment #2:] > > These are gnulib unit test failures; I'll forward your report there. They do not affect the operation of m4 itself. > > It affects building and testing procedures. > > OK. So why m4 executest gnulib test units? Because

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #2, sr #110502 (project m4): > These are gnulib unit test failures; I'll forward your report there. They do not affect the operation of m4 itself. It affects building and testing procedures. OK. So why m4 executest gnulib test units? _

Re: [sr #110502] 1.4.19: test suite is failing

On Tue, Jun 01, 2021 at 06:06:13AM -0400, Tomasz Kłoczko wrote: > URL: > > Operating System: None > > FAIL: test-posix_spawn-dup2-stdout > == > > subprocess failed: No such file or directory > FAIL test-posix_sp

[sr #110502] 1.4.19: test suite is failing

Follow-up Comment #1, sr #110502 (project m4): comment #0 original submission:] > Liooks like some files are missing in dist tar ball. > > Please next time generate that tar ball using "distchec" target instead just "dist". The tarball WAS generated with 'make distcheck', and passed on my machin

[sr #110502] 1.4.19: test suite is failing

Additional Item Attachment, sr #110502 (project m4): File name: m4-po_to_utf-8.patch Size:222 KB ___ Reply to this item at:

[sr #110502] 1.4.19: test suite is failing

URL: <https://savannah.gnu.org/support/?110502> Summary: 1.4.19: test suite is failing Project: GNU M4 Submitted by: kloczek Submitted on: Tue 01 Jun 2021 10:06:12 AM UTC Category: None Prior

test-suite

= GNU M4 1.4.17: tests/test-suite.log = # TOTAL: 163 # PASS: 143 # SKIP: 19 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 SKIP: test-btowc1.sh Skipping test: no tradit