<html><body><p><font size="2">Thanks! However, it looks like I am using clang 3.8 already:</font><br><br><font size="2">$ clang -v</font><br><font size="2">clang version 3.8.0-2ubuntu3 (tags/RELEASE_380/final)</font><br><font size="2">Target: x86_64-pc-linux-gnu</font><br><font size="2">Thread model: posix</font><br><font size="2">InstalledDir: /usr/bin</font><br><font size="2">Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/5.4.0</font><br><font size="2">Found candidate GCC installation: /usr/bin/../lib/gcc/i686-linux-gnu/6.0.0</font><br><font size="2">Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0</font><br><font size="2">Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/6.0.0</font><br><font size="2">Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/5.4.0</font><br><font size="2">Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0</font><br><font size="2">Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0</font><br><font size="2">Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0</font><br><font size="2">Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0</font><br><font size="2">Candidate multilib: .;@m64</font><br><font size="2">Selected multilib: .;@m64<br></font><br><font size="2">$ apt list clang -a</font><br><br><font size="2">Listing... Done</font><br><font size="2">clang/xenial-updates,now 1:3.8-33ubuntu3.1 amd64 [installed]</font><br><font size="2">clang/xenial 1:3.8-33ubuntu3 amd64</font><br><font size="2"><br>Regards,<br><br>Vivian Kong<br>Linux on z Systems Open Source Ecosystem<br>IBM Canada Toronto Lab</font><br><br><img width="16" height="16" src="cid:1__=0ABB0B9EDFC2C5118f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for Florian Friedrich ---2017/04/25 10:43:32 AM---What version of clang are you using? I’ve had the same"><font size="2" color="#424282">Florian Friedrich ---2017/04/25 10:43:32 AM---What version of clang are you using? I’ve had the same problem with clang 3.9 when building on Ubunt</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Florian Friedrich <ffried@me.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">Vivian Kong/Toronto/IBM@IBMCA</font><br><font size="2" color="#5F5F5F">Cc: </font><font size="2">swift-dev <swift-dev@swift.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">2017/04/25 10:43 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [swift-dev] Building swift-3.1-branch from source</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br>What version of clang are you using? I’ve had the same problem with clang 3.9 when building on Ubuntu 16.04 on RasPi: <a href="https://twitter.com/ffried/status/833985445516165121"><u><font color="#0000FF">https://twitter.com/ffried/status/833985445516165121</font></u></a><br>Using clang 3.8 worked fine.<br><br><br><font size="2" face="Helvetica Neue">best regards,</font><br><br><font face="Helvetica Neue">Florian Friedrich</font><br><font size="1" color="#5A5A5A" face="Helvetica Neue">(CTO / CIO, Senior Developer @ ser.soft GmbH)</font><br><br>
<ul><ul>On 25. Apr 2017, at 16:35, Vivian Kong via swift-dev <<a href="mailto:swift-dev@swift.org"><u><font color="#0000FF">swift-dev@swift.org</font></u></a>> wrote:<br>
<p><font size="2">I actually have a question regarding build as well. I haven't been able to build 3.1 branch from source on Ubuntu 16.04 x86_64. I hit this error:<br><br>./swift/utils/build-script -r</font><br><font size="2"><br>...</font><br><font size="2"><br>swift: using gold linker<br>+ /usr/bin/cmake --build /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64 -- -j2 all swift-test-stdlib-linux-x86_64<br>[5/63] Linking CXX executable bin/swift-reflection-dump<br>FAILED: : && /usr/bin/clang++ -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Werror=date-time -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -Wdocumentation -Wimplicit-fallthrough -Wunreachable-code -Woverloaded-virtual -O2 -L/home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/swift-linux-x86_64/./lib/swift/linux -target x86_64-unknown-linux-gnu -lpthread -ldl -fuse-ld=gold tools/swift-reflection-dump/CMakeFiles/swift-reflection-dump.dir/swift-reflection-dump.cpp.o -o bin/swift-reflection-dump -L/home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/./lib -lswiftReflection /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMObject.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMSupport.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMBitReader.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMCore.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMMCParser.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMMC.a /home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/lib/libLLVMSupport.a -lrt -ldl -ltinfo -lpthread -lz -lm -Wl,-rpath,/home/vivkong/swift31/build/Ninja-RelWithDebInfoAssert/llvm-linux-x86_64/./lib && :<br>/home/vivkong/swift31/swift/include/swift/Remote/MetadataReader.h:92: error: undefined reference to 'swift::Demangle::mangleNode(std::shared_ptr<swift::Demangle::Node> const&)'<br>/home/vivkong/swift31/swift/include/swift/Remote/MetadataReader.h:152: error: undefined reference to 'swift::Demangle::mangleNode(std::shared_ptr<swift::Demangle::Node> const&)'<br>/home/vivkong/swift31/swift/include/swift/Reflection/TypeRefBuilder.h:171: error: undefined reference to 'swift::Demangle::mangleNode(std::shared_ptr<swift::Demangle::Node> const&)'<br>clang: error: linker command failed with exit code 1 (use -v to see invocation)<br>[5/63] Linking CXX static library lib/libswiftBasic.a<br>ninja: build stopped: subcommand failed.<br>./swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</font><br><font size="2"><br>I saw </font><a href="https://bugs.swift.org/browse/SR-4147"><u><font size="2" color="#0000FF">https://bugs.swift.org/browse/SR-4147</font></u></a><font size="2"> opened for the master branch (and the workaround is to move to Ubuntu 16.04). I'm actually able to build the 3.1 branch on s390x so I'm wondering if I'm missing some pre-reqs or setting? Any clues would be much appreciated!<br><br>Regards,<br><br>Vivian Kong<br>Linux on z Systems Open Source Ecosystem<br>IBM Canada Toronto Lab</font><br><br><graycol.gif><font size="2" color="#424282">Ian Partridge ---2017/04/25 10:27:39 AM---On 25 April 2017 at 15:15, Vivian Kong <</font><a href="mailto:vivkong@ca.ibm.com"><u><font size="2" color="#0000FF">vivkong@ca.ibm.com</font></u></a><font size="2" color="#424282">> wrote: > I had to remove swift/utils/swi</font><br><font size="2" color="#5F5F5F"><br>From: </font><font size="2">Ian Partridge <</font><a href="mailto:ipartridge@gmail.com"><u><font size="2" color="#0000FF">ipartridge@gmail.com</font></u></a><font size="2">></font><font size="2" color="#5F5F5F"><br>To: </font><font size="2">Vivian Kong/Toronto/IBM@IBMCA</font><font size="2" color="#5F5F5F"><br>Cc: </font><font size="2">Alex Blewitt <</font><a href="mailto:alblue@apple.com"><u><font size="2" color="#0000FF">alblue@apple.com</font></u></a><font size="2">>, swift-dev <</font><a href="mailto:swift-dev@swift.org"><u><font size="2" color="#0000FF">swift-dev@swift.org</font></u></a><font size="2">></font><font size="2" color="#5F5F5F"><br>Date: </font><font size="2">2017/04/25 10:27 AM</font><font size="2" color="#5F5F5F"><br>Subject: </font><font size="2">Re: [swift-dev] Building swift-3.1-branch from source</font><p><hr width="100%" size="2" align="left" noshade><br><br><tt><font size="2"><br>On 25 April 2017 at 15:15, Vivian Kong <</font></tt><a href="mailto:vivkong@ca.ibm.com"><tt><u><font size="2" color="#0000FF">vivkong@ca.ibm.com</font></u></tt></a><tt><font size="2">> wrote:<br>> I had to remove swift/utils/swift_build_support/__init__.pyc if it is there (it got generated when I use the checkout script from the master branch). Wonder if that might help you.<br><br>Yes it works! Thanks!<br><br>-- <br>Ian Partridge<br></font></tt><br><br><br><br>_______________________________________________<br>swift-dev mailing list<u><font color="#0000FF"><br></font></u><a href="mailto:swift-dev@swift.org"><u><font color="#0000FF">swift-dev@swift.org</font></u></a><br><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></ul></ul><br><br><BR>
</body></html>