- **Patch**: new --> review
- **Comment**:

This passes make and a full make doc, but I cannot run the usual pattern of

make,
make test-baseline
apply patch
make clean
make
make check
make doc

It fails on the second 'make' (after make clean) ..

--snip---

tml 
mkdir -p ./out
touch ./out/dummy.dep
echo '*' > ./out/.gitignore
For tracking crashes: use

        grep sourcefilename `grep -L systems.texi out/lybook-testdb/*/*log|sed 
s/log/ly/g`

make --no-builtin-rules -C input/regression out=test local-test
make[1]: Entering directory '/home/jlowe/lilypond-git/build/input/regression'
mkdir -p ./out-test
touch ./out-test/dummy.dep
echo '*' > ./out-test/.gitignore
rm -f ./out-test/collated-files.html
if test -d /home/jlowe/lilypond-git/.git  ; then \
        echo -e 'HEAD is:\n\n\t' ; \
        (cd /home/jlowe/lilypond-git && git log --max-count=1 --pretty=oneline 
) ;\
        echo -e '\n\n\n' ; \
        (cd /home/jlowe/lilypond-git && git diff ) ; \
fi > ./out-test/tree.gittxt
make LILYPOND_BOOK_LILYPOND_FLAGS="-dbackend=eps --formats=ps -djob-count=4 
-dseparate-log-files -dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc 
-I /home/jlowe/lilypond-git/Documentation/included/ -ddump-profile 
-dcheck-internal-types -ddump-signatures -danti-alias-factor=1" 
LILYPOND_BOOK_WARN= ./out-test/collated-files.html 
LYS_OUTPUT_DIR=/home/jlowe/lilypond-git/build/out/lybook-testdb
make[2]: Entering directory '/home/jlowe/lilypond-git/build/input/regression'
/usr/bin/python -tt 
/home/jlowe/lilypond-git/scripts/build/create-version-itexi.py > 
out-test/version.itexi
/usr/bin/python -tt 
/home/jlowe/lilypond-git/scripts/build/create-weblinks-itexi.py > 
out-test/weblinks.itexi
/home/jlowe/lilypond-git/build/scripts/build/out/lys-to-tely 
--name=./out-test/collated-files.tely --title="LilyPond Regression Tests" 
--author="Han-Wen Nienhuys and Jan Nieuwenhuizen" 
--input-filename=out-test/collated-files.list
/bin/sh: 1: /home/jlowe/lilypond-git/build/scripts/build/out/lys-to-tely: not 
found
/home/jlowe/lilypond-git/./make/lysdoc-rules.make:19: recipe for target 
'out-test/collated-files.tely' failed
make[2]: *** [out-test/collated-files.tely] Error 127
make[2]: *** Waiting for unfinished jobs....
Traceback (most recent call last):
  File "/home/jlowe/lilypond-git/scripts/build/create-weblinks-itexi.py", line 
15, in <module>
    import langdefs
ImportError: No module named langdefs
/home/jlowe/lilypond-git/stepmake/stepmake/texinfo-rules.make:95: recipe for 
target 'out-test/weblinks.itexi' failed
make[2]: *** [out-test/weblinks.itexi] Error 1
make[2]: Leaving directory '/home/jlowe/lilypond-git/build/input/regression'
/home/jlowe/lilypond-git/./make/lysdoc-targets.make:12: recipe for target 
'local-test' failed
make[1]: *** [local-test] Error 2
make[1]: Leaving directory '/home/jlowe/lilypond-git/build/input/regression'
/home/jlowe/lilypond-git/GNUmakefile.in:308: recipe for target 'test' failed
make: *** [test] Error 2


Is this something that is bound to happen and cannot be tested normally or is 
this something that the patch submitter didn't take into account on our side or 
something else such as a specific configuration environment that isn't 
universal?




---

** [issues:#5077] build fail on GNU Hurd because of PATH_MAX**

**Status:** Started
**Created:** Wed Feb 22, 2017 01:06 PM UTC by Federico Bruni
**Last Updated:** Thu Feb 23, 2017 07:54 PM UTC
**Owner:** pkx166h
**Attachments:**

- 
[hurd_file_name_support.patch](https://sourceforge.net/p/testlilyissues/issues/5077/attachment/hurd_file_name_support.patch)
 (1.6 kB; text/x-patch)


http://codereview.appspot.com/319400043



Report: http://lists.gnu.org/archive/html/bug-lilypond/2017-01/msg00023.html

LilyPond failed to build on GNU Hurd because Hurd does not have PATH_MAX.
Fortunately, a workaround is available thanks to the combined effort of
Debian developers Don Armstrong (Debian package maintainer for LilyPond)
and Petter Reinholdtsen (Debian Hurd guru).

Petter expressed his wish to send this patch upstream to be included in
future releases of LilyPond, hence this bug report with the attached patch!
 :-)

A little bit of history:

2013-05-13, Don Armstrong <don AT debian.org>:

  Changelog for LilyPond Debian package version 2.16.2-2:

  * Patch around using PATH_MAX in flower/file-name.cc to have builds work
    on hurd (hopefully).

2014-09-10, Petter Reinholdtsen <pere AT hungry.com>, <pere AT debian.org>:

  https://bugs.debian.org/761036

  Hi.  The lilypond package do not build on hurd, even with a hurd patch
  in place.  The cause seem to be a typo in the file
  debian/patches/hurd_file_name_support, checking for _GNU_SOURCE_
  instead of _GNU_SOURCE (at least that is what the getcwd() manual page
  claim to look for).

  Attached is an updated patch, fixing that bug, a memory leak
  forgetting to release the memory allocated by get_current_dir_name(),
  and adding the same code in the test code.

  Please replace the patch in the current source with this new one, and
  consider sending it upstream. :)

2016-07-18, Dr. Tobias Quathamer <toddy AT debian.org>:

  Reviewed and committed the patch to the debian-experimental branch
  (intended for an experiment with LilyPond 2.19.x and Guile-2.x)
  in the LilyPond deb packaging git repository:


https://anonscm.debian.org/git/collab-maint/lilypond.git/commit/?h=debian-experimental&id=e56df084666dbf9905d90c062b1f462aeb6f5f4a

2017-01-27, me:

  Discovered the above, and cherry-picked Dr. Tobias's commit onto the
  "debian" (stable) branch with 2.18.2.

Many thanks!

Anthony
foka AT debian.org


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

Reply via email to