<div dir="ltr"><div>I just found more error details in the log. You can find it below. Hope this helps.</div><div><br></div><div><font size="4">Error 1</font></div><div>--------------------------------------</div><div><br></div><div><div>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Public/XCTestMain.swift</div><div> cd /Users/madhusamuel/dev/swift/swift-corelibs-xctest</div><div> ...</div><div> ...</div><div>/Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Public/XCTestMain.swift:65:71: error: 'lastPathComponent' is unavailable: Use lastPathComponent on URL instead.</div><div> currentTestSuite = XCTestSuite(name: "\(testBundle.bundlePath.lastPathComponent).xctest")</div><div> ^~~~~~~~~~~~~~~~~</div><div>SwiftFoundation.String:173:16: note: 'lastPathComponent' has been explicitly marked unavailable here</div><div> public var lastPathComponent: String { get }</div><div> ^</div></div><div><br></div><div><br></div><div><font size="4">Error 2</font></div><div>--------------------------------------</div><div><div>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Private/TestListing.swift</div><div> cd /Users/madhusamuel/dev/swift/swift-corelibs-xctest</div><div> ...</div><div> ...</div><div> /Objects-normal/x86_64/TestListing.swiftdeps -o /Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/xctest-macosx-x86_64/XCTest.build/Debug/SwiftXCTest.build/Objects-normal/x86_64/TestListing.o</div><div>/Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Private/TestListing.swift:45:46: error: cannot convert value of type 'String.Encoding' to expected argument type 'UInt'</div><div> print(NSString(data: json, encoding: NSUTF8StringEncoding)!)</div><div> ^~~~~~~~~~~~~~~~~~~~</div><div> .rawValue</div><div>Assertion failed: (!failed && "Call arguments did not match up?"), function coerceCallArguments, file /Users/madhusamuel/dev/swift/swift/lib/Sema/CSApply.cpp, line 4655.</div><div>0 swift 0x000000010b6a6d5b llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 43</div><div>1 swift 0x000000010b6a5f86 llvm::sys::RunSignalHandlers() + 70</div><div>2 swift 0x000000010b6a7631 SignalHandler(int) + 641</div><div>3 libsystem_platform.dylib 0x00007fff8ecf552a _sigtramp + 26</div><div>4 swift 0x000000010c290579 cmark_strbuf__initbuf + 73960</div><div>5 swift 0x000000010b6a727e abort + 14</div><div>6 swift 0x000000010b6a7261 __assert_rtn + 81</div><div>7 swift 0x0000000108ff5bae (anonymous namespace)::ExprRewriter::coerceCallArguments(swift::Expr*, swift::Type, llvm::PointerUnion<swift::ApplyExpr*, llvm::PointerEmbeddedInt<unsigned int, 2> >, swift::constraints::ConstraintLocatorBuilder) + 6190</div><div>8 swift 0x0000000108fe4b0d (anonymous namespace)::ExprRewriter::finishApply(swift::ApplyExpr*, swift::Type, swift::constraints::ConstraintLocatorBuilder) + 541</div><div>9 swift 0x0000000108ff638e (anonymous namespace)::ExprRewriter::visitApplyExpr(swift::ApplyExpr*) + 78</div><div>10 swift 0x0000000108fe2325 (anonymous namespace)::ExprRewriter::walkToExprPost(swift::Expr*) + 21</div><div>11 swift 0x0000000109180db0 (anonymous namespace)::Traversal::visit(swift::Expr*) + 160</div><div>12 swift 0x0000000109182969 (anonymous namespace)::Traversal::visit(swift::Expr*) + 7257</div><div>13 swift 0x0000000109180145 swift::Expr::walk(swift::ASTWalker&) + 53</div><div>14 swift 0x0000000108fdedcb swift::constraints::ConstraintSystem::applySolution(swift::constraints::Solution&, swift::Expr*, swift::Type, bool, bool, bool) + 475</div><div>15 swift 0x0000000109081e53 swift::TypeChecker::typeCheckExpression(swift::Expr*&, swift::DeclContext*, swift::TypeLoc, swift::ContextualTypePurpose, swift::OptionSet<swift::TypeCheckExprFlags, unsigned int>, swift::ExprTypeCheckListener*) + 739</div><div>16 swift 0x00000001090f9fc4 swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 4820</div><div>17 swift 0x00000001090f8e3e swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 334</div><div>18 swift 0x00000001090f93d3 swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 1763</div><div>19 swift 0x00000001090f8e3e swift::ASTVisitor<(anonymous namespace)::StmtChecker, void, swift::Stmt*, void, void, void, void>::visit(swift::Stmt*) + 334</div><div>20 swift 0x00000001090f81f9 (anonymous namespace)::StmtChecker::typeCheckBody(swift::BraceStmt*&) + 25</div><div>21 swift 0x00000001090f74df swift::TypeChecker::typeCheckFunctionBodyUntil(swift::FuncDecl*, swift::SourceLoc) + 383</div><div>22 swift 0x00000001090f7303 swift::TypeChecker::typeCheckAbstractFunctionBodyUntil(swift::AbstractFunctionDecl*, swift::SourceLoc) + 35</div><div>23 swift 0x00000001090f7e84 swift::TypeChecker::typeCheckAbstractFunctionBody(swift::AbstractFunctionDecl*) + 180</div><div>24 swift 0x00000001090b3116 typeCheckFunctionsAndExternalDecls(swift::TypeChecker&) + 166</div><div>25 swift 0x00000001090b3db0 swift::performTypeChecking(swift::SourceFile&, swift::TopLevelContext&, swift::OptionSet<swift::TypeCheckingFlags, unsigned int>, unsigned int, unsigned int) + 1568</div><div>26 swift 0x0000000108d714bc swift::CompilerInstance::performSema() + 3916</div><div>27 swift 0x0000000108885c8a performCompile(swift::CompilerInstance&, swift::CompilerInvocation&, llvm::ArrayRef<char const*>, int&, swift::FrontendObserver*) + 442</div><div>28 swift 0x000000010888483f swift::performFrontend(llvm::ArrayRef<char const*>, char const*, void*, swift::FrontendObserver*) + 2895</div><div>29 swift 0x0000000108847300 main + 2448</div><div>30 libdyld.dylib 0x00007fff8bdc95ad start + 1</div><div>Stack dump:</div></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 2, 2016 at 8:29 AM, Madhu Samuel <span dir="ltr"><<a href="mailto:madhusamuel@gmail.com" target="_blank">madhusamuel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Brian,<div><br></div><div>Thanks for you response.</div><div><br></div><div>Still I cannot compile corelibs-xctest with xcode-beta. It seems the error is too generic to debug! If xctest is not yet configured against xcode 8 beta, probably, I will wait. At this point, I am lazy to create my own toolchain, since my last attempt went bust!</div><div><br></div><div><br></div><div><font size="4">The steps I followed</font></div><div><br></div><div><div>1. delete swift/build</div><div>2. utils/update-checkout</div><div>3. sudo xcode-select -s </div><div>/Applications/Xcode-beta.app/Contents/Developer</div><div>4. utils/build-script -r -t (success)</div><div>5. utils/build-script -R. (success)<br></div><div>6. </div><div>$ cd swift-corelibs-xctest</div><div>$ ../swift/utils/build-script --preset corelibs-xctest</div></div><div><br></div><div><font size="4"><br></font></div><div><font size="4">Environment</font></div><div><font size="4"><br></font></div><div><i>Swift Version: Swift version 3.0 (swiftlang-800.0.30 clang-800.0.24)</i></div><div>Xcode Environment: Version 8.0 beta (8S128d)</div><div>Python Version: Python 2.7.10</div><div><br></div><div><br></div><div><br></div><div><font size="4">The Error</font></div><div><br></div><div>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Public/XCTestExpectation.swift<br></div><div><br></div><div>.....</div><div>....</div><div><br></div><div><span class=""><div><br></div><div><unknown>:0: error: unable to execute command: Illegal instruction: 4</div><div><unknown>:0: error: compile command failed due to signal (use -v to see invocation)</div><div>** BUILD FAILED **</div><div><br></div><div><br></div><div>The following build commands failed:</div></span><div><span style="white-space:pre-wrap"> </span>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Public/XCTestMain.swift</div><span class=""><div><span style="white-space:pre-wrap"> </span>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Private/TestListing.swift</div><div><span style="white-space:pre-wrap"> </span>CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler</div></span><div>(3 failures)</div><span class=""><div>Traceback (most recent call last):</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 445, in <module></div><div> main()</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 441, in main</div><div> parsed_args.func(parsed_args)</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 64, in build</div><div> source_dir=SOURCE_DIR))</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 30, in run</div><div> subprocess.check_call(command, shell=True)</div><div> File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 540, in check_call</div><div> raise CalledProcessError(retcode, cmd)</div><div>subprocess.CalledProcessError: Command 'xcodebuild -workspace /Users/madhusamuel/dev/swift/swift-corelibs-xctest/XCTest.xcworkspace -scheme SwiftXCTest SWIFT_EXEC="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/swift-macosx-x86_64/bin/swiftc" SWIFT_LINK_OBJC_RUNTIME=YES SYMROOT="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/xctest-macosx-x86_64" OBJROOT="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/xctest-macosx-x86_64"' returned non-zero exit status 65</div><div>../swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</div><div>../swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</div></span></div><div><br></div><div><br></div><div>Regards,</div><div>Madhu</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 30, 2016 at 11:38 PM, Brian Gesiak <span dir="ltr"><<a href="mailto:modocache@gmail.com" target="_blank">modocache@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Madhu,<div><br></div><div>Sorry for the late reply to this -- I obviously need to update my email settings! :(<br><br>Could you pull down the latest changes to Swift, and let me know if you're still experiencing difficulties compiling corelibs-xctest?</div><span><font color="#888888"><div><br></div><div>- Brian Gesiak</div><div><br></div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 12:03 AM, Madhu Samuel <span dir="ltr"><<a href="mailto:madhusamuel@gmail.com" target="_blank">madhusamuel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Wow, the swift build is a success. Though there are a few warnings at the end. I guess the issue was with cached values in the build directory.<div><br></div><div>But, in the next step to build xctest using "/utils/build-script --preset corelibs-xctest", the build fails. The build error log is given below.</div><div><br></div><div>------------------------</div><div><br></div><div><div>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Public/XCTestExpectation.swift</div><div>....</div><div>....</div><div><br></div><div><unknown>:0: error: unable to execute command: Illegal instruction: 4</div><div><unknown>:0: error: compile command failed due to signal (use -v to see invocation)</div><div>** BUILD FAILED **</div><div><br></div><div><br></div><div>The following build commands failed:</div><div><span style="white-space:pre-wrap"> </span>CompileSwift normal x86_64 /Users/madhusamuel/dev/swift/swift-corelibs-xctest/Sources/XCTest/Private/TestListing.swift</div><div><span style="white-space:pre-wrap"> </span>CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler</div><div>(2 failures)</div><div>Traceback (most recent call last):</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 445, in <module></div><div> main()</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 441, in main</div><div> parsed_args.func(parsed_args)</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 64, in build</div><div> source_dir=SOURCE_DIR))</div><div> File "/Users/madhusamuel/dev/swift/swift-corelibs-xctest/build_script.py", line 30, in run</div><div> subprocess.check_call(command, shell=True)</div><div> File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 540, in check_call</div><div> raise CalledProcessError(retcode, cmd)</div><div>subprocess.CalledProcessError: Command 'xcodebuild -workspace /Users/madhusamuel/dev/swift/swift-corelibs-xctest/XCTest.xcworkspace -scheme SwiftXCTest SWIFT_EXEC="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/swift-macosx-x86_64/bin/swiftc" SWIFT_LINK_OBJC_RUNTIME=YES SYMROOT="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/xctest-macosx-x86_64" OBJROOT="/Users/madhusamuel/dev/swift/build/Ninja-ReleaseAssert/xctest-macosx-x86_64"' returned non-zero exit status 65</div><div>../swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</div><div>../swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting</div></div><div><br></div><div><div><br></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 12:35 PM, Madhu Samuel <span dir="ltr"><<a href="mailto:madhusamuel@gmail.com" target="_blank">madhusamuel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Brian Croom,<div><br></div><div>Thanks for the quick response. I deleted the entire build directory now. Initiated a new build. Fingers crossed... </div><div><br></div><div>Will update the status as soon as the build finishes. </div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 21, 2016 at 12:31 PM, Brian Croom <span dir="ltr"><<a href="mailto:brian.s.croom@gmail.com" target="_blank">brian.s.croom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hmm, have you tried deleting your `build/swift-macosx-x86_64/` directory? I wonder if cached CMake values could cause that issue.<div><br></div><div>(By the way, I can confirm that getting the build going for the first time is the most challenging! I hope we can get things going for you soon.)</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-20 22:22 GMT-04:00 Madhu Samuel <span dir="ltr"><<a href="mailto:madhusamuel@gmail.com" target="_blank">madhusamuel@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So after spending almost a week trying to build swift and core libraries (mainly xctest) during the end of May un-successfully, I made up my mind to give another attempt today.<div><br></div><div>I checkout the latest code from swift repo. Since the xctest documentation says, "Confirm you're able to build the Swift project using utils/build-script -R", that's where I started. </div><div><br></div><div>Unfortunately, build-script -R gives the below error.</div><div><br></div><div><unknown>:0: error: Swift does not support the SDK 'MacOSX10.11.sdk'<br></div><div><br></div><div><br></div><div>My active developer directory is '/Applications/Xcode-beta.app/Contents/Developer'.</div><div>The toolchain is 'Xode 8.0'</div><div><br></div><div>The build is taken in Mac OSX El Capitan 10.11.4</div><div><br></div><div>Let me know whether I miss anything? I assume getting the build working for the first time is the hardest, but there I am!</div><div><br></div><div>Any help is appreciated!</div><div><br></div><div>Regards,<br>Madhu</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 30, 2016 at 8:32 AM, Madhu Samuel <span dir="ltr"><<a href="mailto:madhusamuel@gmail.com" target="_blank">madhusamuel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<p><span>Wow, that was a quick response. Thanks Brian Gesiak and Brian Croom. </span></p>
<p><span>My first quick attempt using build-toolchain script to build my own tool chain failed. Anyway I will give it another try and let you know the status.</span></p></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 30, 2016 at 1:52 AM, Brian Croom <span dir="ltr"><<a href="mailto:brian.s.croom@gmail.com" target="_blank">brian.s.croom@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's right, breaking changes have been made to Swift since the latest toolchain snapshot was released, and Corelibs Foundation has been updated accordingly.<div><br></div><div>Until the next snapshot, an alternative to building your own toolchain would be to check out an older commit of Foundation which still builds with the compiler in the snapshot toolchain<span></span>, since XCTest doesn't depend on any of the more recent Foundation changes. I've had success using this commit: <a href="https://github.com/apple/swift-corelibs-foundation/commit/04d4f92870652160388f1c69de3fd7bb0656860c" target="_blank">https://github.com/apple/swift-corelibs-foundation/commit/04d4f92870652160388f1c69de3fd7bb0656860c</a> </div><span><font color="#888888"><div><br></div></font></span><div><span><font color="#888888">--Brian</font></span><div><div><br><br>söndag 29 maj 2016 skrev Brian Gesiak via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Madhu,</div><div><br></div><div>Oy, my bad -- I only just noticed you put the toolchain version at the bottom of your original email.</div><div><br></div><div>It's possible the May 9th toolchain is already too old to build XCTest. I'll double-check myself. In the meantime, you may want to try building your own toolchain and using that.</div><div><br></div><div>- Brian Gesiak<br><br><div></div><br></div><br><br><br>
<div class="gmail_quote">On Sun, May 29, 2016 at 7:23 AM -0700, "Brian Gesiak" <span dir="ltr"><<a>modocache@gmail.com</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"">
<div>Madhu,</div><div><br></div><div>Thanks for the report!</div><div><br></div><div>The main difference between the build scripts (which use xcodebuild) and using Xcode itself is the version of Swift that is used. The build scripts build a Swift 3.0 compiler, then use that to build XCTest. When using Xcode directly, you need to select a recent Swift toolchain yourself.</div><div><br></div><div>Which Swift toolchain are you using to compile XCTest in Xcode?</div><div><br></div><div>Our tests only make sure apple/swift master works. If the latest Swift toolchain from <a dir="ltr" href="http://swift.org" target="_blank">http://swift.org</a> doesn't work, you may have to built your own toolchain. You can do so using the `utils/build-toolchain` script in the Swift repository.</div><div><br></div><div>Once you figure out your Swift toolchain version, let us know! You should be able to find out in the preferences pane in Xcode.</div><div><br></div><div>- Brian Gesiak</div><div><br><div></div><br></div><br><br><br>
<div class="gmail_quote">On Sun, May 29, 2016 at 1:24 AM -0700, "Madhu Samuel via swift-corelibs-dev" <span dir="ltr"><<a>swift-corelibs-dev@swift.org</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"">
<div dir="ltr"><div><div>Hi All,</div><div><br></div><div>I am new to this forum. </div><div><br></div><div>I am trying to build the xctest project. I followed the instructions at <a href="https://github.com/apple/swift-corelibs-xctest" target="_blank">https://github.com/apple/swift-corelibs-xctest</a></div><div><br></div><div>I am able to successfully build via the build scripts. But, if I build XCTest using xcode using the SwiftXCTest scheme I am getting a few errors. </div><div><br></div><div>1. swift-corelibs-foundation/Foundation/NSXMLDTDNode.swift:242:64: error: cannot convert value of type 'UnsafeMutablePointer<Void>' (aka 'UnsafeMutablePointer<()>') to expected argument type 'OpaquePointer'</div><div> let unmanaged = Unmanaged<NSXMLDTDNode>.fromOpaque(privateData)</div><div><br></div><div>2. swift-corelibs-foundation/Foundation/NSTimer.swift:14:47: error: cannot convert value of type 'UnsafeMutablePointer<Void>' (aka 'UnsafeMutablePointer<()>') to expected argument type 'OpaquePointer'</div><div> let t = Unmanaged<NSTimer>.fromOpaque(info!).takeUnretainedValue()</div><div><br></div><div>etc.</div><div><br></div><div>My dev environment, </div><div>OS: Mac OSX El Capitan 10.11.4 (15E65).</div><div>Xcode Version: Version 7.3.1 (7D1014)</div><div>XCode Toolchain: Swift Development Snapshot 2016-05-09 (a)</div><div><br></div><div>Any help is appreciated.</div><div><br></div><div>Regards,</div><div>Madhu</div><div><br></div><div><br></div></div></div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div></blockquote></div></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>