[llvm-commits] [dragonegg] r105219 - /dragonegg/trunk/README
baldrick at free.fr
Mon May 31 02:26:18 PDT 2010
Date: Mon May 31 04:26:18 2010
New Revision: 105219
Try to clarify the role of libelf when building gcc.
--- dragonegg/trunk/README (original)
+++ dragonegg/trunk/README Mon May 31 04:26:18 2010
@@ -27,8 +27,8 @@
Configure gcc with your favorite options and also with --enable-plugin and
--enable-lto. Build gcc and install it somewhere. If you don't have libelf
-installed then the build will fail, because gcc's LTO code makes use of it,
+installed then the configure step may fail because the configure script thinks
+that LTO requires libelf, though in fact it does not when using dragonegg. See
In theory the gcc you build can be a cross-compiler, and the plugin should work
and build code for the targetted platform. I don't think anyone has ever tried
@@ -38,6 +38,15 @@
libraries and concludes that plugins won't work. You can find patches to fix
+NOTE: This may be fixed in gcc mainline (gcc 4.6).
+Darwin special 2: the gcc configure script thinks darwin doesn't support LTO
+because it is not an ELF platform. Dragonegg repurposes the LTO infrastructure,
+and thus needs LTO support enabled, but it makes no use of the parts of LTO that
+require ELF. You just need to turn off the ELF check in the configure script.
+If anyone has a patch to do this, I will be happy to add it here!
+NOTE: This is fixed in gcc mainline (gcc 4.6).
Step 2: Build the plugin
More information about the llvm-commits