That is true, it is not sufficient. Even if to add sysroot-prefix to all
.h-files within modulemap, they are found correctly, but their's inner includes
are given wrongly, without sysroot prefix. Could anybody hint, what source code
is responsible for internal parsing of .h-files, starting from
I think, I know how to add sysroot to place in code, which I have shown. But,
may be, it is not sufficient. It is also need to provide adding of prefix when
traversing other "angled" include-directives from modulemap-file in deep. I do
not know how to do that, but I am looking for.
01.04.2016,
I believe the bug still exists. I tried to build armv7 on native hardware
yesterday and hit this bug. I haven't had time to look into it at all though.
- Will
> On Mar 31, 2016, at 1:11 PM, Iliya Trub via swift-dev
> wrote:
>
> Dear colleagues
> What about my last message from this thread?
Dear colleagues
What about my last message from this thread? Does bug exist or not? Really, I
get glibs.modulemap after overall compiler building under arm-emulator, then
use cross-compiling under x86_64 Ubuntu, and swift takes headers, listed within
glibc.modulemap (starting from /usr/include),
It seems to me, the last phenomena is explained by swift compiler bug. Let us
look into clang/lib/Lex/ModuleMap.cpp source file, method parseHeaderDecl. We
can find, for example, following lines:
if (llvm::sys::path::is_absolute(Header.FileName)) {
RelativePathName = Header.FileName;
File
Yes, Dmitry. I found corresponding module.map for arm and placed it into glibs
subdirectory of my swiftc's include path. It was found. But, it seems to me,
sysroot argument is not applied to paths, written in that module.map or I do
not how to correct do that.
I add to swift command-line followi
Then you should have a module map for Glibc in the build products.
Dmitri
On Thu, Mar 24, 2016 at 2:32 PM, Труб Илья wrote:
> I have built all targets for arm (including modules and libraries) within the
> native arm environment on arm-emulator with chroot.
>
> 25.03.2016, 00:25, "Dmitri Griben
I have built all targets for arm (including modules and libraries) within the
native arm environment on arm-emulator with chroot.
25.03.2016, 00:25, "Dmitri Gribenko" :
> On Thu, Mar 24, 2016 at 2:03 PM, Труб Илья wrote:
>> Thanks for your answer, Dmitry. I will look for examples of module maps
On Thu, Mar 24, 2016 at 2:03 PM, Труб Илья wrote:
>
> Thanks for your answer, Dmitry. I will look for examples of module maps in
> test sources.
You shouldn't need to. If you have built Swift for arm, you should
have the right one produced by the build system.
How did you compile the standard
Thanks for your answer, Dmitry. I will look for examples of module maps in test
sources.
24.03.2016, 23:56, "Dmitri Gribenko" :
> On Thu, Mar 24, 2016 at 1:30 PM, Труб Илья wrote:
>> Dear colleagues
>> I have faced with strange behaviour, when I compile some swift source on
>> Ubuntu 14, targ
On Thu, Mar 24, 2016 at 1:30 PM, Труб Илья wrote:
> Dear colleagues
> I have faced with strange behaviour, when I compile some swift source on
> Ubuntu 14, target=arm-linux-gnueabi, all neccessary modules for arm present,
> -sysroot and
> -isysroot are passed via -Xcc.
>
> :61:10: note: in file
Dear colleagues
I have faced with strange behaviour, when I compile some swift source on Ubuntu
14, target=arm-linux-gnueabi, all neccessary modules for arm present, -sysroot
and
-isysroot are passed via -Xcc.
:61:10: note: in file included from :61:
#include "/usr/include/x86_64-linux-gnu/sys
12 matches
Mail list logo
