Opened 10 years ago

Closed 10 years ago

#44356 closed defect (duplicate)

Error: org.macports.build for port llvm-3.2 returned: command execution failed

Reported by: bugmail-macports@… Owned by: jeremyhu (Jeremy Huddleston Sequoia)
Priority: Normal Milestone:
Component: ports Version: 2.3.1
Keywords: Cc: sunlounger001@…
Port: llvm-3.2

Description

I can't install llvm-3.2 on my mac. I tried cleaning it but still doesn't go through.

xavier@imac-xavier:~$ sudo port clean llvm-3.2
--->  Cleaning llvm-3.2
xavier@imac-xavier:~$ sudo port install llvm-3.2
--->  Computing dependencies for llvm-3.2
--->  Fetching archive for llvm-3.2
--->  Attempting to fetch llvm-3.2-3.2_3.darwin_13.x86_64.tbz2 from http://packages.macports.org/llvm-3.2
--->  Attempting to fetch llvm-3.2-3.2_3.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/llvm-3.2
--->  Attempting to fetch llvm-3.2-3.2_3.darwin_13.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/llvm-3.2
--->  Fetching distfiles for llvm-3.2
--->  Verifying checksums for llvm-3.2
--->  Extracting llvm-3.2
--->  Applying patches to llvm-3.2
--->  Configuring llvm-3.2
--->  Building llvm-3.2
Error: org.macports.build for port llvm-3.2 returned: command execution failed
Please see the log file for port llvm-3.2 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_llvm-3.2/llvm-3.2/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port llvm-3.2 failed

It isn't quite clear to me what the source error is. I'm attaching the full log

Attachments (1)

main.log (1.9 MB) - added by bugmail-macports@… 10 years ago.
llvm-3.2/main.log

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by bugmail-macports@…

Attachment: main.log added

llvm-3.2/main.log

comment:1 Changed 10 years ago by mf2k (Frank Schima)

Cc: jeremyhu@… removed
Owner: changed from macports-tickets@… to jeremyhu@…

comment:2 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

:info:build LazyValueInfo.cpp:998:14: error: no matching member function for call to 'insert'
:info:build     worklist.insert(worklist.end(), succ_begin(ToUpdate), succ_end(ToUpdate));
:info:build     ~~~~~~~~~^~~~~~
:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:718:14: note: candidate function not viable: no known conversion from 'succ_iterator' (aka 'SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>') to 'size_type' (aka 'unsigned long') for 2nd argument
:info:build     iterator insert(const_iterator __position, size_type __n, const_reference __x);
:info:build              ^
:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:722:14: note: candidate template ignored: disabled by 'enable_if' [with _InputIterator = llvm::SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>]
:info:build              __is_input_iterator  <_InputIterator>::value &&
:info:build              ^
:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:733:13: note: candidate template ignored: disabled by 'enable_if' [with _ForwardIterator = llvm::SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>]
:info:build             __is_forward_iterator<_ForwardIterator>::value &&
:info:build             ^
:info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:710:14: note: candidate function not viable: requires 2 arguments, but 3 were provided
:info:build     iterator insert(const_iterator __position, const_reference __x);
:info:build              ^

comment:3 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Is there a reason you need 3.2? I suggest you use 3.4 as 3.2 was a bit fragile.

comment:4 Changed 10 years ago by bugmail-macports@…

No reason indeed, it was probably pulled automatically some time ago. I installed 3.4, rebuilt the ports depending on 3.2, uninstalled 3.2 and now everything is looking fine. Thanks!

comment:5 in reply to:  4 Changed 10 years ago by sunlounger001@…

I get the same error when I try upgrading llvm-3.2, so I did as you mentioned, and installed llvm-3.4, but I am new to using ports, so my question is: How did you rebuild the ports that depend on 3.2, to use 3.4? Thanks,

Replying to bugmail-macports@…:

No reason indeed, it was probably pulled automatically some time ago. I installed 3.4, rebuilt the ports depending on 3.2, uninstalled 3.2 and now everything is looking fine. Thanks!

comment:6 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: sunlounger001@… added
Resolution: duplicate
Status: newclosed

Duplicate of #43977.

sunlounger001, if you have ports installed that depend on llvm-3.2, probably they do so via a variant. For example, commonly people have the ld64 and cctools ports installed, and at one time in the past +llvm32 was the default variant in those ports, because 3.2 was the latest stable version of llvm at the time. MacPorts preserves variant selections on upgrades, so if you initially installed those ports back then, and never changed the variant, then you'll still be using the +llvm32 variant today. The default variant on those ports today is +llvm34. To get that new default, just reinstall the ports:

sudo port install ld64 cctools

If you want specific variants, specify them. For example, if you want to use the +llvm35 variant on both ports instead, use:

sudo port install ld64 +llvm35 cctools +llvm35
Note: See TracTickets for help on using tickets.