llvm dev - Nov 2018 - Errors in configuration for LLVM with CMake GUI

I tried to configure CMake for LLVM using the GUI and I've attached the logs
for the attempt to this message.  I installed Perl and the latest version of GCC
before that attempt.  There were still errors that stopped it from being able to
generate project files, though.

I'd like to know how I can get this to work.  How do I tell it where to find
Backtrace, Libomp, Compiler-RT, LLD and Clang?  And where exactly is Backtrace? 
I copy-pasted the locations for the stuff I checked out for LLVM, so I'm not
really sure where the stuff I need to put into CMake for Compiler-RT, Backtrace
and Libomp is (it's where it should be, that's all I know).

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/30bd6f7f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CMakeError.log
Type: application/octet-stream
Size: 652508 bytes
Desc: CMakeError.log
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/30bd6f7f/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CMakeOutput.log
Type: application/octet-stream
Size: 259613 bytes
Desc: CMakeOutput.log
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181128/30bd6f7f/attachment-0003.obj>

I checked your CMakeError.log again. The .h include files it is marking as
missing are not LLVM include files, but are OS-related (e.g.,
malloc/malloc.h), and in some cases appear to be potentially Linux ones
(dlfcn.h, sys/ioctl, malloc_np.h). I can't imagine why your build might be
looking for Linux as opposed to Windows include files. That could be a clue
to your problem.

You said you installed the latest version of GCC before this attempt. This
confuses me further, since you are using Visual Studio to build with, and
that makes no use of GCC. In fact, honestly I am wondering if your GCC
implementation libraries are somehow in your search path wrt environment
variables, and your build is actually trying to use the GNU/Linux header
files rather than the VS Windows header files, which would certainly blow
it up. Again, I am no expert here, so I don't have a definite answer, but
based on what little I know, this setup doesn't sound safe. Maybe get rid
of GCC completely, as I am not sure when/how you would even use it on the
Windows side.

Similarly, I don't believe Perl has anything to do with this either, as
neither CMake nor VS make any use of it. But I can't imagine it causing any
problems for you to have it.

I don't know anything about Backtrace, Libomp, Compiler-RT, so I cannot
help you there. As we have discussed before, the source for clang and lld
go into the llvm source folder's "tools" folder by those names. If
they are
there, after the configure step of the CMake-Gui, options will
automatically appear for both clang and lld. You will want to mouse click
the checkbox next to CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS prior to hitting
the generate button.

Sorry I don't know more than that, but hopefully that will help some ...
and then others can chime in if they know more about this than me.

On Thu, Nov 29, 2018 at 2:52 PM Osman Zakir via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I tried to configure CMake for LLVM using the GUI and I've attached the
> logs for the attempt to this message.  I installed Perl and the latest
> version of GCC before that attempt.  There were still errors that stopped
> it from being able to generate project files, though.
>
> I'd like to know how I can get this to work.  How do I tell it where to
> find Backtrace, Libomp, Compiler-RT, LLD and Clang?  And where exactly is
> Backtrace?  I copy-pasted the locations for the stuff I checked out for
> LLVM, so I'm not really sure where the stuff I need to put into CMake
for
> Compiler-RT, Backtrace and Libomp is (it's where it should be,
that's all I
> know).
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181129/50499f78/attachment.html>

I probably need GCC for Git bash.  And the one I have is MinGW's GCC, which
is the one for Windows.  I don't know why CMake is trying to find Linux
headers.  Hopefully someone who knows better what to do will weigh in here.

@Jonathan Goodwin<mailto:jondgoodwin at gmail.com> , are you sure you
didn't have to tell it where the header files for Windows are?  If I need to
specify the paths to those headers, how do I do it?
________________________________
From: Jonathan Goodwin <jondgoodwin at gmail.com>
Sent: Thursday, November 29, 2018 10:42 AM
To: Osman Zakir
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Errors in configuration for LLVM with CMake GUI

I checked your CMakeError.log again. The .h include files it is marking as
missing are not LLVM include files, but are OS-related (e.g., malloc/malloc.h),
and in some cases appear to be potentially Linux ones (dlfcn.h, sys/ioctl,
malloc_np.h). I can't imagine why your build might be looking for Linux as
opposed to Windows include files. That could be a clue to your problem.

You said you installed the latest version of GCC before this attempt. This
confuses me further, since you are using Visual Studio to build with, and that
makes no use of GCC. In fact, honestly I am wondering if your GCC implementation
libraries are somehow in your search path wrt environment variables, and your
build is actually trying to use the GNU/Linux header files rather than the VS
Windows header files, which would certainly blow it up. Again, I am no expert
here, so I don't have a definite answer, but based on what little I know,
this setup doesn't sound safe. Maybe get rid of GCC completely, as I am not
sure when/how you would even use it on the Windows side.

Similarly, I don't believe Perl has anything to do with this either, as
neither CMake nor VS make any use of it. But I can't imagine it causing any
problems for you to have it.

I don't know anything about Backtrace, Libomp, Compiler-RT, so I cannot help
you there. As we have discussed before, the source for clang and lld go into the
llvm source folder's "tools" folder by those names. If they are
there, after the configure step of the CMake-Gui, options will automatically
appear for both clang and lld. You will want to mouse click the checkbox next to
CLANG_BUILD_TOOLS and LLD_BUILD_TOOLS prior to hitting the generate button.

Sorry I don't know more than that, but hopefully that will help some ... and
then others can chime in if they know more about this than me.

On Thu, Nov 29, 2018 at 2:52 PM Osman Zakir via llvm-dev <llvm-dev at
lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
I tried to configure CMake for LLVM using the GUI and I've attached the logs
for the attempt to this message.  I installed Perl and the latest version of GCC
before that attempt.  There were still errors that stopped it from being able to
generate project files, though.

I'd like to know how I can get this to work.  How do I tell it where to find
Backtrace, Libomp, Compiler-RT, LLD and Clang?  And where exactly is Backtrace? 
I copy-pasted the locations for the stuff I checked out for LLVM, so I'm not
really sure where the stuff I need to put into CMake for Compiler-RT, Backtrace
and Libomp is (it's where it should be, that's all I know).

_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181129/d10138a8/attachment.html>