Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#59090 closed defect (fixed)

mercurial 5.1 build command execution failed - IndexError: list index out of range

Reported by: klausness Owned by: jmroot (Joshua Root)
Priority: Normal Milestone:
Component: ports Version: 2.6.0
Keywords: Cc:
Port: mercurial

Description

Attempting to upgrade mercurial, build failed with IndexError: list index out of range.

MacOS 10.13.6, Xcode 10.1

From the log:

:info:build running build_ext
:info:build building 'mercurial.cext.base85' extension
:info:build creating build/temp.macosx-10.13-x86_64-2.7
:info:build creating build/temp.macosx-10.13-x86_64-2.7/mercurial
:info:build creating build/temp.macosx-10.13-x86_64-2.7/mercurial/cext
:info:build Traceback (most recent call last):
:info:build   File "setup.py", line 1512, in <module>
:info:build     **extra)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 151, in setup
:info:build     dist.run_commands()
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands
:info:build     self.run_command(cmd)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command
:info:build     cmd_obj.run()
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build.py", line 127, in run
:info:build     self.run_command(cmd_name)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/cmd.py", line 326, in run_command
:info:build     self.distribution.run_command(command)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command
:info:build     cmd_obj.run()
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build_ext.py", line 340, in run
:info:build     self.build_extensions()
:info:build   File "setup.py", line 510, in build_extensions
:info:build     return build_ext.build_extensions(self)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build_ext.py", line 449, in build_extensions
:info:build     self.build_extension(ext)
:info:build   File "setup.py", line 517, in build_extension
:info:build     build_ext.build_extension(self, ext)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/command/build_ext.py", line 499, in build_extension
:info:build     depends=ext.depends)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/ccompiler.py", line 574, in compile
:info:build     self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/unixccompiler.py", line 119, in _compile
:info:build     cc_args + extra_postargs)
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_osx_support.py", line 357, in compiler_fixup
:info:build     sysroot = compiler_so[idx+1]
:info:build IndexError: list index out of range
:info:build make: *** [build] Error 1
:info:build make: *** Waiting for unfinished jobs....
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/mercurial-5.1/doc'
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/mercurial-5.1'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_mercurial/mercurial/work/mercurial-5.1" && make -j8 -w all PYTHON=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 
:info:build Exit code: 2
:error:build Failed to build mercurial: command execution failed
:debug:build Error code: CHILDSTATUS 67313 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"

Attachments (2)

main.log (84.5 KB) - added by klausness 5 years ago.
Log
main.2.log (107.2 KB) - added by ylluminarious (George Plymale II) 5 years ago.
new error log after updating

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by klausness

Attachment: main.log added

Log

comment:1 Changed 5 years ago by jmroot (Joshua Root)

Looks like python is trying to be clever with the compiler flags and isn't quite clever enough. I'll look into it.

comment:2 Changed 5 years ago by jmroot (Joshua Root)

Owner: set to jmroot
Resolution: fixed
Status: newclosed

In 2498b96b4016c90f68748b330a6c1bd92e52d906/macports-ports (master):

python pg: don't add flags for an empty sysroot

Fixes: #59090

comment:3 in reply to:  2 Changed 5 years ago by ylluminarious (George Plymale II)

Replying to jmroot:

In 2498b96b4016c90f68748b330a6c1bd92e52d906/macports-ports (master):

python pg: don't add flags for an empty sysroot

Fixes: #59090

This problem seems to still be occurring. I just updated via sudo port selfupdate and did a fresh installation of the port, but it still fails with a similar error. I made sure that my local port tree's version of python-1.0.tcl had your newest changes. I'm not sure what's going on exactly, but I'm still seeing this issue.

Changed 5 years ago by ylluminarious (George Plymale II)

Attachment: main.2.log added

new error log after updating

comment:4 Changed 5 years ago by jmroot (Joshua Root)

That's a quite different error. Probably best to open a new ticket.

comment:5 in reply to:  4 Changed 5 years ago by ylluminarious (George Plymale II)

Replying to jmroot:

That's a quite different error. Probably best to open a new ticket.

Okay, I made a new ticket here: #59108

comment:6 Changed 5 years ago by klausness

The original issue is resolved for me. Thanks for the quick fix.

Note: See TracTickets for help on using tickets.