<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 5/31/2012 8:52 AM, Justin Holewinski wrote:
<blockquote
cite="mid:CAJgxuachz1mG7gEpB4Jw-Uj7C3sw6WsHD5uqUZuHBx9E99VtdQ@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Thu, May 31, 2012 at 1:44 AM,
MortenMacFly <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mac-fly@gmx.net" target="_blank">mac-fly@gmx.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Windows7, Cmake 2.8.8, MinGW 4.6.1. compiler:<br>
<br>
I got two questions seeking for help:<br>
<br>
1.) I am trying to compile LLVM/Clang from trunk using the
instructions from<br>
the LLVM homepage which works fine except that the llvm-config
tool is not<br>
being built. When I do a "make" in the "tools\llvm-config"
folder it fails,<br>
too with:<br>
../../Makefile.common:60: ../../Makefile.config: No such file
or directory<br>
../../Makefile.common:68: /Makefile.rules: No such file or
directory<br>
mingw32-make.exe: *** No rule to make target
`/Makefile.rules'. Stop.<br>
Those files are there, so I am a bit lost. Is there a
configuration switch I<br>
am missing to build this tool? I searched through the Cmake
options, but I<br>
could not find any.<br>
</blockquote>
<div><br>
</div>
<div>The llvm-config tool is not built on Windows, since it
requires sed which is not available by default on Windows. I
actually have a patch for this somewhere (build llvm-config on
Windows if sed is found), I'll try to find it and post it.</div>
</div>
</blockquote>
<br>
This "No Makefile.rules" problem is different, and recent, from what
I see. <br>
<br>
With mingw, msys, and gnuwin32, on win7, then configure and make<br>
will normally succeed, including building llvm-config.exe.<br>
<br>
I've run into this "No Makefile.rules" problem, and as best I know<br>
so far, it's tied to the change in the llvm.org Getting Started
procedure:<br>
now it's called for to checkout LLVM, checkout clang, AND <br>
checkout Compiler-RT. I followed that path a week ago and hit<br>
the same breakage described above.<br>
<br>
I'm now going thru procedures one at a time; <br>
svn checkout LLVM and configure and make, succeeds;<br>
repeat, adding "--enable-shared" to configure; succeeds;<br>
svn checkout clang and repeat: both static and shared succeed;<br>
<br>
...and that's how far I've got. Am waiting for compiler-rt<br>
right now, to find out if it re-introduces the breakage, or<br>
if something has been changed in trunk in the last few<br>
days to cause different behavior.<br>
<br>
I agree with Mikael that we do need an up-to-date, tested,<br>
preferably buildbotted, Windows build procedure. I think<br>
it doesn't matter too much what tool choices are made,<br>
most project setups start with "download this set of tools"<br>
anyway. But there needs to be at least one path that can<br>
be followed to success, and that path needs to be tested,<br>
and known to be up-to-date.<br>
<br>
<br>
cheers,<br>
Kevin<br>
<br>
</body>
</html>