[swift-build-dev] SwiftPM Boostrap Crash

[Daniel Dunbar]

I would certainly *hope* no brew package is causing a copy of the Swift stdlibs to end up in usr/local?

 - Daniel

> On Jan 8, 2016, at 10:04 AM, Max Howell <max.howell at apple.com> wrote:
> 
> I’d guess that something in /usr/local/include or lib was getting selected instead of the correct swift libraries? Unless otherwise specified /usr/local is first in the search paths.
> 
>> On Jan 8, 2016, at 8:43 AM, Daniel Dunbar <daniel_dunbar at apple.com <mailto:daniel_dunbar at apple.com>> wrote:
>> 
>> That is very interesting information. I don't see offhand how a brew package could cause this problem, but if you see it again (esp. if you discover what package it was) please let us know!
>> 
>>  - Daniel
>> 
>>> On Jan 8, 2016, at 7:32 AM, Ryan Lovelett <swift-dev at ryan.lovelett.me <mailto:swift-dev at ryan.lovelett.me>> wrote:
>>> 
>>> Ok that was a real facepalm then drag your hand down your face for emphasis moment.
>>>  
>>> The swift file I was trying to compile was called `test.swift` which would become `test` once a linked executable. However I was in the root of the https://github.com/apple/swift <https://github.com/apple/swift> repository that already has a `test` directory. That is why it couldn't link. Sigh. Once I renamed it to `ryan` it compiled and linked just fine.
>>>  
>>> Which then led me back to the actual problem, i.e., could not build swiftpm. Still not sure exactly what was causing the issue but I was able to get past it.
>>>  
>>> I started comparing the configuration, home brew, env config, etc, of my work laptop (that didn't work) and my personal laptop (that did work) and I noticed that my work machine had a bunch of homebrew packages that my personal didn't. I uninstalled everything on my work laptop that wasn't on my personal machine. Voila, it builds again.
>>>  
>>> Apologies for the radio silence. And thank you for all the support that you were not required to give; it is appreciated.
>>>  
>>>  
>>> On Thu, Jan 7, 2016, at 11:37 AM, Max Howell wrote:
>>>>> ld: can't open output file for writing: test
>>>> 
>>>> swiftc can’t write the output to the current directory. When you run this is your current directory writable?
>>>  
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20160108/f873c29f/attachment.html>