Opened 11 years ago
Closed 11 years ago
#41822 closed defect (fixed)
Lilypond build fails
Reported by: | jarvis@… | Owned by: | nerdling (Jeremy Lavergne) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | LenoreHorner | |
Port: | lilypond |
Description (last modified by nerdling (Jeremy Lavergne))
Attempting 'port install lilypond' with a clean installation of MacPorts fails.
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.16.2/scripts/build/out/run-and-check "LANG= makeinfo --enable-encoding --error-limit=0 -I /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.16.2/Documentation -I. -I./out --output=out/lilypond-internals.info out/internals.texi" "internals.makeinfo.log" Please check the logfile changes.makeinfo.log for errors make[1]: *** [out/lilypond-changes.info] Error 1 make[1]: *** Waiting for unfinished jobs.... Please check the logfile usage.makeinfo.log for errors make[1]: *** [out/lilypond-usage.info] Error 1 Please check the logfile contributor.makeinfo.log for errors make[1]: *** [out/lilypond-contributor.info] Error 1 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.16.2/Documentation' make: *** [all] Error 2 make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.16.2' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/work/lilypond-2.16.2" && /usr/bin/make -j4 -w all Exit code: 2 Error: org.macports.build for port lilypond returned: command execution failed Warning: targets not executed for lilypond: org.macports.activate org.macports.build org.macports.destroot org.macports.install Please see the log file for port lilypond for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port lilypond failed
Attachments (5)
Change History (14)
Changed 11 years ago by jarvis@…
comment:1 Changed 11 years ago by mf2k (Frank Schima)
Owner: | changed from macports-tickets@… to snc@… |
---|
In the future, please Cc the port maintainers (port info --maintainers lilypond
).
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to jarvis@…:
Please check the logfile changes.makeinfo.log for errors make[1]: *** [out/lilypond-changes.info] Error 1 make[1]: *** Waiting for unfinished jobs.... Please check the logfile usage.makeinfo.log for errors make[1]: *** [out/lilypond-usage.info] Error 1 Please check the logfile contributor.makeinfo.log for errors
Please attach these logfiles so that we may see what went wrong. They should be somewhere inside the directory identified by the command port work lilypond
comment:3 Changed 11 years ago by jarvis@…
Tue 17 Dec 2013 11:16:03 WST
Output of uname -mprsv
:
Darwin 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64 i386
Information from diskutil:
File System Personality: Case-sensitive Journaled HFS+
Clean installation with binaries
- Uninstall macports as per instructions on website.
- Install macports from source
tar -xjf ~/Desktop/Mavericks\ Setup/Installed/MacPorts-2.2.1.tar.bz2 cd MacPorts-2.2.1 ./configure make sudo make install sudo port -v selfupdate sudo port install lilypond
Fails with message
---> Extracting lilypond ---> Applying patches to lilypond ---> Configuring lilypond ---> Building lilypond Error: org.macports.build for port lilypond returned: command execution failed Please see the log file for port lilypond for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_lilypond/lilypond/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port lilypond failed
Changed 11 years ago by jarvis@…
Attachment: | changes.makeinfo.log added |
---|
changes.makeinfo.log from binary installation
Changed 11 years ago by jarvis@…
Attachment: | contributor.makeinfo.log added |
---|
contributor.makeinfo.log from binary installation
Changed 11 years ago by jarvis@…
Attachment: | usage.makeinfo.log added |
---|
usage.makeinfo.log from binary installation
Changed 11 years ago by jarvis@…
Attachment: | main-2013-12-17.log added |
---|
main.log from clean run of binary install on 2013-12-17
comment:5 Changed 11 years ago by LenoreHorner
My main log looks the same as the second one jarvis attached (it's not from installing as binary though). I can't find the other logs. There's a warning about not finding gettext domain that appears several times towards the end of the log, but since I did a clean install of 10.9.1 I thought there should be gettext problems. I am not using a case-sensitive file system. What else can we do to help find the error. I confess the log file means nothing to me in terms of what to do to fix the problem.
comment:6 Changed 11 years ago by jarvis@…
If Lenore is using a case-insensitive filesystem, and I'm using a case-sensitive filesystem then I guess we can eliminate a case-sensitivity issue...
comment:7 Changed 11 years ago by nerdling (Jeremy Lavergne)
Description: | modified (diff) |
---|---|
Summary: | Lilypond binary installation fails → Lilypond build fails |
Lilypond 2.18.x is the current branch: if you do a port selfupdate
does lilypond 2.18.2 build for you where 2.16.x did not?
comment:8 Changed 11 years ago by LenoreHorner
I do have 2.18.0_0 installed. I've had it installed for some time now. My recollection is that I checked back for a new version, and installed as soon as that was available.
comment:9 Changed 11 years ago by nerdling (Jeremy Lavergne)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks, this was fixed with their release then.
error log