> On Dec 19, 2015, at 7:14 , Davide Italiano <dccitali...@gmail.com> wrote:
>
> On Fri, Dec 18, 2015 at 7:58 AM, Davide Italiano <dccitali...@gmail.com
> <mailto:dccitali...@gmail.com>> wrote:
>> On Wed, Dec 16, 2015 at 2:25 PM, Jordan Rose <jordan_r...@apple.com> wrote:
>>>
>>>> On Dec 16, 2015, at 11:21 , Davide Italiano <dccitali...@gmail.com> wrote:
>>>>
>>>> On Wed, Dec 16, 2015 at 11:17 AM, Jordan Rose <jordan_r...@apple.com>
>>>> wrote:
>>>>> What's the compile command for the files that are failing? If the target
>>>>> triple there doesn't include a version number, it might be defaulting to
>>>>> something like "1.0".
>>>>>
>>>>> Jordan
>>>>>
>>>>
>>>> I see many of these, here's an example:
>>>> http://people.freebsd.org/~davide/swift/modules_failure.txt
>>>>
>>>> BTW, the triple includes a version number (freebsd-unknown-11.0)
>>>
>>> Ah, not the one I see: "-target x86_64-unknown-freebsd". Try adding "11.0"
>>> to that. (Presumably it comes from the Foundation build script, so you
>>> might have to find where it's being passed down.)
>>
>> Thanks!
>> I followed your suggestion and I was able to make progress.
>> While we're at this -- I had another issue with modules (when running
>> testsuite) that I wasn't able to solve (and which causes a lot of test
>> failures because Objective-C modules can't be build), i.e. missing
>> headers.
>>
>> Command Output (stderr):
>> --
>> <module-includes>:1:10: note: in file included from <module-includes>:1:
>> #include "/usr/include/complex.h"
>> ^
>> /usr/include/complex.h:32:10: error: 'sys/cdefs.h' file not found with
>> <angled> include; use "quotes" instead
>> #include <sys/cdefs.h>
>> ^
>> <module-includes>:2:10: note: in file included from <module-includes>:2:
>> #include "/usr/include/ctype.h"
>> ^
>> /usr/include/ctype.h:44:10: error: 'sys/cdefs.h' file not found with
>> <angled> include; use "quotes" instead
>> #include <sys/cdefs.h>
>> ^
>> [...]
>
> I tracked this one down and realized the problem is that include paths
> (i.e. /usr/include) aren't passed correctly to swiftc in the tests. I
> worked around
> this passing -I/usr/include but I'd like to fix this right for
> FreeBSD. Where's the correct place where CXXFLAGS and LDFLAGS should
> be passed?
Hm. The Clang inside Swift should be supplying by default just from the target
triple. If you pass "-Xcc -v" to swiftc it should dump the default search paths
for your platform. What does that look like?
Jordan
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
