Opened 7 years ago

Last modified 3 years ago

#48690 new defect

Upgrading "guile18" fails

Reported by: dave@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: MasakiOita, shapovalow@…, drkp (Dan Ports)
Port: guile18

Description (last modified by ryandesign (Ryan Schmidt))

Uograding MacPorts failed when building "guile18":

--->  Staging guile18 into destroot
Error: org.macports.destroot for port guile18 returned: command execution failed
Please see the log file for port guile18 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_guile18/guile18/main.log
Error: Unable to upgrade port: 1
Error rebuilding guile18
    while executing
"error "Error rebuilding $portname""
    (procedure "revupgrade_scanandrebuild" line 395)
    invoked from within
"revupgrade_scanandrebuild broken_port_counts $opts"
    (procedure "macports::revupgrade" line 5)
    invoked from within
"macports::revupgrade $opts"
    (procedure "action_revupgrade" line 2)
    invoked from within
"action_revupgrade $action $portlist $opts"
    (procedure "action_upgrade" line 25)
    invoked from within
"$action_proc $action $portlist [array get global_options]"
    (procedure "process_cmd" line 103)
    invoked from within
"process_cmd $remaining_args"
    invoked from within
"if { [llength $remaining_args] > 0 } {

    # If there are remaining arguments, process those as a command
    set exit_status [process_cmd $remaining..."
    (file "/opt/local/bin/port" line 5268)
ozzie:~ dave$ 

Attachments (1)

main.log (477.8 KB) - added by dave@… 7 years ago.

Download all attachments as: .zip

Change History (7)

Changed 7 years ago by dave@…

Attachment: main.log added

comment:1 Changed 7 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)

The relevant portion of the log appears to be:

:info:destroot ./gh.texi:1000: must be after `@deftypefun' to use `@deftypefunx'
:info:destroot ./fdl.texi:411: raising the section level of @appendixsubsec which is too low
:info:destroot ./api-utility.texi:566: warning: node `C Hooks' is next for `Hook Reference' in menu but not in sectioning
:info:destroot ./api-utility.texi:674: warning: node `Hook Reference' is prev for `C Hooks' in menu but not in sectioning
:info:destroot ./api-options.texi:510: warning: node next `Printing options' in menu `Debugger options' and in sectioning `Evaluator options' differ
:info:destroot ./api-options.texi:533: warning: node prev `Evaluator options' in menu `Debugger options' and in sectioning `Printing options' differ
:info:destroot ./api-options.texi:544: warning: node next `Evaluator trap options' in menu `Examples of option use' and in sectioning `Debugger options' differ
:info:destroot ./api-options.texi:625: warning: node next `Debugger options' in menu `Evaluator options' and in sectioning `Examples of option use' differ
:info:destroot ./api-options.texi:625: warning: node prev `Debugger options' in menu `Printing options' and in sectioning `Evaluator trap options' differ
:info:destroot ./api-options.texi:681: warning: node prev `Examples of option use' in menu `Evaluator trap options' and in sectioning `Debugger options' differ
:info:destroot make[2]: *** [guile.info] Error 1

This makes it sound like a texinfo problem. texinfo was updated to version 6 last month in r138717; it's possible guile18's use of texinfo is not compatible with texinfo 6 and needs to be patched in some way.

Actually, according to this gentoo bug, it's an incompatibility with texinfo 5 already: https://bugs.gentoo.org/show_bug.cgi?id=464044

Also a debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738295

These have patches attached that we might use.

comment:2 Changed 7 years ago by MasakiOita

Cc: epimetheus314@… added

Cc Me!

comment:3 Changed 7 years ago by shapovalow@…

Cc: shapovalow@… added

Cc Me!

comment:5 Changed 7 years ago by drkp (Dan Ports)

Cc: dports@… added

Cc Me!

comment:6 Changed 3 years ago by codefisher (Michael Buckley)

I am still getting this error, 4 years later, my error log has exactly the same as @ryandesign posted, even the line numbers are are the same. Is there any possibility of a fix? I am trying to install lilypond.

Note: See TracTickets for help on using tickets.