Opened 9 years ago

Closed 8 years ago

#48063 closed defect (invalid)

MacVim doesn’t build on 10.6

Reported by: FGasper (Felipe Gasper) Owned by: raimue (Rainer Müller)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc:
Port: MacVim

Description (last modified by ryandesign (Ryan Carsten Schmidt))

After the checksums, the log has:

:debug:install Creating MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2
:debug:install Environment: 
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/work/.CC_PRINT_OPTIONS'
CPATH='/opt/local/include'
LIBRARY_PATH='/opt/local/lib'
MACOSX_DEPLOYMENT_TARGET='10.6'
:debug:install Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/work/destroot" && /usr/bin/tar -cvf - . | /usr/bin/bzip2 -c9 > /opt/local/var/macports/software/macvim/MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2'
:debug:install Executing command line:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/work/destroot" && /usr/bin/tar -cvf - . | /usr/bin/bzip2 -c9 > /opt/local/var/macports/software/macvim/MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2 
:info:install sh: /opt/local/var/macports/software/macvim/MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2: Operation not permitted
:info:install a .
:info:install a ./+COMMENT
:info:install a ./+CONTENTStar: Write error: Broken pipe
:info:install Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/work/destroot" && /usr/bin/tar -cvf - . | /usr/bin/bzip2 -c9 > /opt/local/var/macports/software/macvim/MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2 
:info:install Exit code: 1
:error:install org.macports.install for port MacVim returned: command execution failed
:debug:install Error code: CHILDSTATUS 87051 1
:debug:install Backtrace: command execution failed
    while executing
"system $fullcmdstring"
    ("eval" body line 1)
    invoked from within
"eval system $notty $nice \$fullcmdstring"
    invoked from within
"command_exec archive"
    (procedure "create_archive" line 208)
    invoked from within
"create_archive $location $portarchivetype"
    (procedure "portinstall::install_main" line 22)
    invoked from within
"portinstall::install_main org.macports.install"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"
:info:install Warning: targets not executed for MacVim: org.macports.install
:notice:install Please see the log file for port MacVim for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/main.log

The weird thing is that I can execute the command

cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_editors_MacVim/MacVim/work/destroot" && /usr/bin/tar -cvf - . | /usr/bin/bzip2 -c9 > /opt/local/var/macports/software/macvim/MacVim-7.4.snapshot76_1+huge.darwin_10.x86_64.tbz2

… just fine when I “sudo bash”.

Attachments (1)

main.log (658.2 KB) - added by FGasper (Felipe Gasper) 9 years ago.
Log from last full “port upgrade macvim” run

Download all attachments as: .zip

Change History (9)

Changed 9 years ago by FGasper (Felipe Gasper)

Attachment: main.log added

Log from last full “port upgrade macvim” run

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

Description: modified (diff)
Owner: changed from macports-tickets@… to raimue@…
Port: MacVim added

I agree, that is weird...

comment:2 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Does this happen for any other ports or just MacVim? Does cleaning MacVim and retrying change anything?

comment:3 Changed 9 years ago by FGasper (Felipe Gasper)

I’m only seeing it on MacVim, but it might happen with other ports. Cleaning and retrying doesn’t change anything.

The weird thing to me is that I’m able to generate the .bz2-ball manually..? I don’t know enough about MacPorts or MacOS to know what’s different between just me sudo/bash’d versus running “port”.

-FG

comment:4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

What are the permissions and ownership of /opt/local/var/macports/software/macvim/, and does it differ from the permissions and ownership of any other directory in /opt/local/var/macports/software/?

comment:5 Changed 9 years ago by FGasper (Felipe Gasper)

Here is a sampling of what I have in that directory:

drwxr-xr-x    4 root      admin    136 Feb 20 11:35 llvm-3.4
drwxr-xr-x    3 root      admin    102 Jan 13 17:34 llvm_select
drwxr-xr-x    3 macports  admin    102 Jan 13 17:34 lua
drwxr-xr-x    4 macports  admin    136 Apr 20 13:42 lzo2
drwxr-xr-x    3 macports  admin    102 Jan 13 17:34 m4
drwxr-xr-x    4 macports  admin    136 Jun 15 12:08 macvim
drwxr-xr-x    3 root      admin    102 Sep 26  2012 md5sha1sum
drwxr-xr-x    6 root      admin    204 May 14 20:40 mercurial
drwxr-xr-x    8 root      admin    272 May 14 20:11 mesa
drwxr-xr-x    3 macports  admin    102 Oct 22  2011 mhash
drwxr-xr-x    3 root      admin    102 Jan 13 13:49 mobipocket
drwxr-xr-x    3 root      admin    102 Oct 28  2014 mozjs17
drwxr-xr-x    3 root      admin    102 Jan 13 17:34 mpfr
drwxr-xr-x    3 macports  admin    102 Jan 13 17:34 mysql5

comment:6 Changed 9 years ago by raimue (Rainer Müller)

Do you have enough empty disk space? Although I would expect the appropriate errno in that case.

As this happens in the install phase I doubt it is caused by the MacVim port itself.

comment:7 Changed 9 years ago by FGasper (Felipe Gasper)

I have enough disk space … many GiB free.

What strikes me is that I can create the tarball manually, but MacPorts fails when it attempts to execute the same command.

Would a dtruss help, perhaps?

comment:8 Changed 8 years ago by raimue (Rainer Müller)

Resolution: invalid
Status: newclosed

MacVim requires at least OS X 10.8. Whatever it was, I still doubt this was related to MacVim.

Note: See TracTickets for help on using tickets.