MacVim @7.4.snapshot90 +ruby - build failure

[irfandurmus@…]

sudo port install macvim +ruby
--->  Computing dependencies for MacVim
--->  Fetching archive for MacVim
--->  Attempting to fetch MacVim-7.4.snapshot90_0+huge+ruby+ruby18.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/MacVim
--->  Attempting to fetch MacVim-7.4.snapshot90_0+huge+ruby+ruby18.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/MacVim
--->  Attempting to fetch MacVim-7.4.snapshot90_0+huge+ruby+ruby18.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/MacVim
--->  Fetching distfiles for MacVim
--->  Verifying checksums for MacVim
--->  Extracting MacVim
--->  Applying patches to MacVim
--->  Configuring MacVim
--->  Building MacVim
Error: org.macports.build for port MacVim returned: command execution failed
Please see the log file for port MacVim for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_editors_MacVim/MacVim/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port macvim failed

[irfandurmus@…]

ports - macvim - main.log

[irfandurmus@…]

btw

xcodebuild -version Xcode 7.2.1 Build version 7C1002

[mf2k (Frank Schima)]

The Priority field is for use by Macports team members only.

[irfandurmus@…]

Replying to mf2k@…:

The Priority field is for use by Macports team members only.

Didn't know that.. Thanks!

[ryandesign (Ryan Carsten Schmidt)]

Maybe duplicate of #44624?

[irfandurmus@…]

Replying to ryandesign@…:

Maybe duplicate of #44624?

output looks different but reason might/might not be the same, have no idea

[irfandurmus@…]

Hi everyone,

I got some resource, might help to maintainer:

Please see: ​http://nerderati.com/2010/07/26/compiling-vim-with-ruby-integration-on-snow-leopard/ ​https://groups.google.com/forum/#!topic/vim_dev/o0up0CxXr5o

Best!

[raimue (Rainer Müller)]

I think this has been lingering for too long and the old build log will not be that helpful anymore. If the build error still occurs with the current release, please file a new ticket.