Hey Mohit!

Were you able to build successfully?

Michael

> On Mar 30, 2017, at 4:29 PM, Michael Gottesman <mgottes...@apple.com> wrote:
> 
> I was just informed that swift-corelibs-foundation is actually using ninja! 
> My bad!
> 
> Still I would use the preset from the bots. It should just work. Otherwise, 
> you are missing a dependency or have differing versions/etc.
> 
> Michael
> 
>> On Mar 30, 2017, at 4:25 PM, Michael Gottesman <mgottes...@apple.com 
>> <mailto:mgottes...@apple.com>> wrote:
>> 
>>> 
>>> On Mar 30, 2017, at 4:22 PM, Michael Gottesman via swift-users 
>>> <swift-us...@swift.org <mailto:swift-us...@swift.org>> wrote:
>>> 
>>>> 
>>>> On Mar 30, 2017, at 12:31 PM, Mohit Athwani via swift-users 
>>>> <swift-us...@swift.org <mailto:swift-us...@swift.org>> wrote:
>>>> 
>>>> I'm trying to get back to work starting from scratch on Swift Foundation 
>>>> on my Ubuntu 16.04 LTS system.
>>>> 
>>>> I cloned the main swift repo and all of it's dependencies via ssh
>>>> ./swift/utils/update-checkout --clone-with-ssh
>>>> and after running (taken from instructions from the Foundation site):
>>>> 
>>>> swift/utils/build-script --xctest --foundation -t
>>>> 
>>>> I get the following error:
>>>> 
>>>> + make build-tests
>>>> /bin/bash ../libtool  --tag=CC   --mode=link 
>>>> /home/mohit/Documents/swift-source/build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang
>>>>  -Wall -Wno-deprecated-declarations  -fblocks 
>>>> -I/home/mohit/Documents/swift-source/swift-corelibs-libdispatch/src/BlocksRuntime
>>>>  -isystem /usr/include/bsd -DLIBBSD_OVERLAY   -g -O0 -rpath 
>>>> /home/mohit/Documents/swift-source/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/linux/x86_64
>>>>   -o dispatch_apply dispatch_apply.o libbsdtests.la 
>>>> <http://libbsdtests.la/> ../src/libdispatch.la <http://libdispatch.la/>  
>>>> -lbsd 
>>>> -L/home/mohit/Documents/swift-source/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/linux/x86_64
>>>>  -lswiftCore -lswiftSwiftOnoneSupport -lpthread 
>>>> libtool: link: 
>>>> /home/mohit/Documents/swift-source/build/Ninja-DebugAssert/llvm-linux-x86_64/bin/clang
>>>>  -Wall -Wno-deprecated-declarations -fblocks 
>>>> -I/home/mohit/Documents/swift-source/swift-corelibs-libdispatch/src/BlocksRuntime
>>>>  -isystem /usr/include/bsd -DLIBBSD_OVERLAY -g -O0 -o .libs/dispatch_apply 
>>>> dispatch_apply.o  ./.libs/libbsdtests.a ../src/.libs/libdispatch.so -lbsd 
>>>> -L/home/mohit/Documents/swift-source/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/linux/x86_64
>>>>  -lswiftCore -lswiftSwiftOnoneSupport -lpthread -Wl,-rpath 
>>>> -Wl,//usr/lib/swift/linux -Wl,-rpath 
>>>> -Wl,/home/mohit/Documents/swift-source/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/linux/x86_64
>>>> /home/mohit/Documents/swift-source/build/Ninja-DebugAssert/swift-linux-x86_64/lib/swift/linux/x86_64/libswiftCore.so:
>>>>  undefined reference to `objc_release'
>>>> clang-4.0: error: linker command failed with exit code 1 (use -v to see 
>>>> invocation)
>>>> Makefile:1123: recipe for target 'dispatch_apply' failed
>>>> make: *** [dispatch_apply] Error 1
>>>> swift/utils/build-script: fatal error: command terminated with a non-zero 
>>>> exit status 2, aborting
>>>> 
>>>> Looks like there is some undefined reference for objc_release in 
>>>> libswiftCore.
>>>> 
>>>> From the looks of the message it looks like swift was actually built but 
>>>> it's just that test cases weren't built. On this hunch, I went into my 
>>>> swift-corelibs-foundation folder and tried to execute:
>>>> 
>>>> ninja
>>>> 
>>>> Which tells me:
>>>> 
>>>> ninja: error: loading 'build.ninja': No such file or directory
>>> 
>>> swift-corelibs-foundation does not use ninja. I would use the build-script 
>>> line from the bots. That way you know you are doing the right thing.
>>> 
>>> Specifically:
>>> 
>>> URL: 
>>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/2413/consoleFull
>>>  
>>> <https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_04/2413/consoleFull>
>>> 
>>> Preset: buildbot_incremental_linux
>>> 
>>> If that does not work on your system, then something is misconfigured.
>> 
>> Let me elaborate, when I say misconfigured, I mean you are missing a 
>> dependency.
>> 
>>> 
>>> Also I wouldn't use --clone-with-ssh it is unnecessary.
>>> 
>>> 
>>>> 
>>>> Given my lack of experience here, I'm not quite sure how to go about 
>>>> resolving these issues.
>>>> 
>>>> Could somebody help me out here please.
>>>> 
>>>> Thanks,
>>>> 
>>>> Mohit
>>>> _______________________________________________
>>>> swift-users mailing list
>>>> swift-us...@swift.org <mailto:swift-us...@swift.org>
>>>> https://lists.swift.org/mailman/listinfo/swift-users 
>>>> <https://lists.swift.org/mailman/listinfo/swift-users>
>>> 
>>> _______________________________________________
>>> swift-users mailing list
>>> swift-us...@swift.org <mailto:swift-us...@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-users 
>>> <https://lists.swift.org/mailman/listinfo/swift-users>

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Reply via email to