Opened 10 years ago
Closed 10 years ago
#43977 closed defect (fixed)
llvm-3.2 Build Error in CodeExtractor.cpp:751
Reported by: | ddmarshall@… | Owned by: | jeremyhu (Jeremy Huddleston Sequoia) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.0 |
Keywords: | Cc: | greger.cronquist@… | |
Port: | llvm-3.2 |
Description
I tried to upgrade llvm-3.2 and I got the following error:
:info:build CodeExtractor.cpp:751:28: error: no matching constructor for initialization of 'std::vector<BasicBlock *>' :info:build std::vector<BasicBlock*> Succs(succ_begin(codeReplacer), :info:build ^ ~~~~~~~~~~~~~~~~~~~~~~~~~
I've attached the entire build log file.
This was using XCode Version 5.1.1 (5B1008) on OS X Mavericks (10.9.3). I don't know if other OS/Compiler variations will produce this error.
Attachments (1)
Change History (9)
Changed 10 years ago by ddmarshall@…
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to jeremyhu@… |
---|
comment:3 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
:info:build CodeExtractor.cpp:751:28: error: no matching constructor for initialization of 'std::vector<BasicBlock *>' :info:build std::vector<BasicBlock*> Succs(succ_begin(codeReplacer), :info:build ^ ~~~~~~~~~~~~~~~~~~~~~~~~~ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:524:5: note: candidate constructor not viable: no known conversion from 'succ_iterator' (aka 'SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>') to 'size_type' (aka 'unsigned long') for 1st argument :info:build vector(size_type __n, const_reference __x); :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:569:5: note: candidate constructor not viable: no known conversion from 'succ_iterator' (aka 'SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>') to 'const std::__1::vector<llvm::BasicBlock *, std::__1::allocator<llvm::BasicBlock *> >' for 1st argument :info:build vector(const vector& __x, const allocator_type& __a); :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:528:35: note: candidate template ignored: disabled by 'enable_if' [with _InputIterator = llvm::SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>] :info:build typename enable_if<__is_input_iterator <_InputIterator>::value && :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:543:35: note: candidate template ignored: disabled by 'enable_if' [with _ForwardIterator = llvm::SuccIterator<llvm::TerminatorInst *, llvm::BasicBlock>] :info:build typename enable_if<__is_forward_iterator<_ForwardIterator>::value && :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:535:9: note: candidate constructor template not viable: requires at least 3 arguments, but 2 were provided :info:build vector(_InputIterator __first, _InputIterator __last, const allocator_type& __a, :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:549:9: note: candidate constructor template not viable: requires at least 3 arguments, but 2 were provided :info:build vector(_ForwardIterator __first, _ForwardIterator __last, const allocator_type& __a, :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:506:5: note: candidate constructor not viable: requires 0 arguments, but 2 were provided :info:build vector() :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:513:40: note: candidate constructor not viable: requires single argument '__a', but 2 arguments were provided :info:build _LIBCPP_INLINE_VISIBILITY explicit vector(const allocator_type& __a) :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:520:14: note: candidate constructor not viable: requires single argument '__n', but 2 arguments were provided :info:build explicit vector(size_type __n); :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:525:5: note: candidate constructor not viable: requires 3 arguments, but 2 were provided :info:build vector(size_type __n, const_reference __x, const allocator_type& __a); :info:build ^ :info:build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/vector:568:5: note: candidate constructor not viable: requires single argument '__x', but 2 arguments were provided :info:build vector(const vector& __x); :info:build ^
comment:4 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
comment:5 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Is there any particular reason why people need 3.2? I'd rather just not fix this and go back to only supporting 3.3 and later on Mavericks.
comment:6 Changed 10 years ago by ddmarshall@…
I would prefer a fix to this so that I can perform build tests for my own code with 3.2 while in Mavericks, but I cannot call it a need for 3.2. Ending support of 3.2 on Mavericks is an acceptable resolution.
comment:7 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
comment:8 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Build log with error. Search for 'CodeExtractor.cpp:751' to get to beginning of build error.