similar to: [LLVMdev] Build warnings and errors

Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Build warnings and errors"

2012 Apr 18
0
[LLVMdev] Build warnings and errors
Jim's comment handles the tablegen stuff... On Wed, Apr 18, 2012 at 10:50 AM, Sean Silva <silvas at purdue.edu> wrote: > At the bottom there is a failure when building the clang driver, > complaining about finding `DEFAULT_SYSROOT` > > I'm building with ninja (generated by CMake). > Have you updated both LLVM and Clang? This was a relatively recent change, but
2012 Apr 18
2
[LLVMdev] Build warnings and errors
On Apr 18, 2012, at 1:00 PM, Chandler Carruth <chandlerc at google.com> wrote: > Jim's comment handles the tablegen stuff... > > On Wed, Apr 18, 2012 at 10:50 AM, Sean Silva <silvas at purdue.edu> wrote: > At the bottom there is a failure when building the clang driver, complaining about finding `DEFAULT_SYSROOT` > > I'm building with ninja (generated by
2012 Apr 18
0
[LLVMdev] Build warnings and errors
On Apr 18, 2012, at 1:03 PM, Eric Christopher <echristo at apple.com> wrote: > > On Apr 18, 2012, at 1:00 PM, Chandler Carruth <chandlerc at google.com> wrote: > >> Jim's comment handles the tablegen stuff... >> >> On Wed, Apr 18, 2012 at 10:50 AM, Sean Silva <silvas at purdue.edu> wrote: >> At the bottom there is a failure when building
2012 Apr 18
1
[LLVMdev] Build warnings and errors
On Apr 18, 2012, at 1:07 PM, Andrew Trick <atrick at apple.com> wrote: > On Apr 18, 2012, at 1:03 PM, Eric Christopher <echristo at apple.com> wrote: > >> >> On Apr 18, 2012, at 1:00 PM, Chandler Carruth <chandlerc at google.com> wrote: >> >>> Jim's comment handles the tablegen stuff... >>> >>> On Wed, Apr 18, 2012 at
2015 Jul 16
4
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
Hi Jack, On Thu, Jul 16, 2015 at 4:03 PM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > Hans, > Do we intend to leave -fopenmp defaulted to the no-op libgomp > support for 3.7.0 or do the sensible thing by applying... > > Index: CMakeLists.txt > =================================================================== > --- CMakeLists.txt (revision 242425)
2016 Dec 02
2
Failed to configure LLVM for use with Musl
I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt
2015 Jul 17
2
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
Seems on OpenSUSE x86, it's called i586, not i686 :-( +Alexey: do you think we can handle this in the compiler-rt cmake files somehow? Maybe try targeting both i686 and i586 unless that would break something else? On Fri, Jul 17, 2015 at 1:31 AM, Nikola Smiljanic <popizdeh at gmail.com> wrote: > CMake Error at projects/compiler-rt/cmake/config-ix.cmake:125 (message): > Cannot
2015 Jul 21
2
[LLVMdev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
Building phase 2 fails on i686 Fedora 22 CMake Error at projects/compiler-rt/cmake/config-ix.cmake:125 (message): Cannot compile for i686: CMakeError.log attached On Wed, Jul 22, 2015 at 8:20 AM, Alexey Samsonov <vonosmas at gmail.com> wrote: > The problem is we "guess" that the host architecture is i686, and fail > when we find out that we can't target it (__i686__
2012 May 22
1
[LLVMdev] Issues with clang build
Hi, I am on r157251. When I try to build clang, I get this error. Driver.cpp:52:47: error: use of undeclared identifier 'DEFAULT_SYSROOT' ClangExecutable(ClangExecutable), SysRoot(DEFAULT_SYSROOT), ^ 1 error generated. make[4]: *** [/home/ganapathy/projects/llvm/tools/clang/lib/Driver/Release+Asserts/Driver.o] Error 1 Can
2012 Apr 04
1
[LLVMdev] build warnings
Just picked up some warnings while building LLVM: http://pastie.org/3724174 --Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120403/c8e17f99/attachment.html>
2012 Apr 18
4
FW: tinc Digest, Vol 90, Issue 17
Dear C?dric, If I am using windows version of tinc, how can I check the connection list? Regards, Eric -----Original Message----- From: tinc-bounces at tinc-vpn.org [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of tinc-request at tinc-vpn.org Sent: Wednesday, April 18, 2012 6:00 PM To: tinc at tinc-vpn.org Subject: tinc Digest, Vol 90, Issue 17 Send tinc mailing list submissions to tinc at
2012 Apr 18
0
[LLVMdev] sysroot configury broken?
Hi all, I see this in configure.ac: AC_ARG_WITH(sysroot, AS_HELP_STRING([--with-default-sysroot], [Add --sysroot=<path> to all compiler invocations.]),, withval="") AC_DEFINE_UNQUOTED(DEFAULT_SYSROOT,"$withval", [Default <path> to all compiler invocations for --sysroot=<path>.]) The macro seems to suggest that I should write
2012 May 07
1
[LLVMdev] TableGen backend API refactoring.
tl;dr: is anyone opposed to making the interface to a TableGen backend be: void MyBackend(RecordKeeper &, raw_ostream & /* maybe some other args, per backend's needs */); ?? Currently, this is the "interface" for a TableGen backend: struct TableGenBackend { virtual void anchor(); virtual ~TableGenBackend() {} // run - All TableGen backends should implement the run
2012 Dec 04
5
[LLVMdev] LLVM documentation work help
Sean, I can create html, pdf and epub, then put them on <https://github.com/Jonathan2251/lbd/tree/gh-pages>. The uvbook example as below can click the pdf link and pop up a download window while I cannot. The uvbook link is put on http://username.github.com/... while the "make gh-pages" put them on https://github.com/username/...  How can I have the download link like uvbook
2012 Apr 18
0
[LLVMdev] STLport
Oops, I had the arguments backward. Patch re-attached with the correct ordering > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Joerg Sonnenberger > Sent: Wednesday, April 18, 2012 8:39 AM > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] STLport > > On Wed, Apr 18, 2012 at 03:04:00PM +0000,
2012 Apr 19
1
[LLVMdev] Hexagon Patch for
Hi, Here's a Hexagon patch for replacing transfer/copy instructions to combine for review. This patch does not yield any warnings on Hexagon, Arm and X86 build on Linux. This work is by Arnold Schwaighofer. Sirish -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:
2012 Sep 21
2
[LLVMdev] yaml2obj.rst where to link? (Sphinx warns)
Also, why does it say yaml2py?: yaml2obj takes a YAML description of an object file and converts it to a binary file. $ yaml2py input-file .. program:: yaml2py --Sean Silva On Thu, Sep 20, 2012 at 4:59 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Wed, Sep 19, 2012 at 8:25 PM, Sean Silva <silvas at purdue.edu> wrote: >> Sphinx warns that yaml2obj
2012 Dec 03
3
[LLVMdev] LLVM documentation work help
Sean, The `.. code-block:: bash` is work. Thank your information. Currently, I can put reStructuredText files on github. But, your example uvbook seems put the html and pdf on different github directory. Do you put html and pdf on github with version control? Jonathan On 2012/12/3, at 上午7:43, Sean Silva <silvas at purdue.edu> wrote: > It looks like things are going well. > >
2012 Apr 18
1
[LLVMdev] STLport
Hi Micah, Looks like the diff is not against LLVM 3.0 release, but rather against some other "internal" version. :-) On Wed, Apr 18, 2012 at 9:42 AM, Villmow, Micah <Micah.Villmow at amd.com>wrote: > Oops, I had the arguments backward. Patch re-attached with the correct > ordering > > > -----Original Message----- > > From: llvmdev-bounces at cs.uiuc.edu
2013 Jun 18
3
[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR
On Tue, Jun 18, 2013 at 12:03 PM, Sean Silva <silvas at purdue.edu> wrote: > Instead of a blacklist, why not a whitelist? Given the size of LangRef, > you're bound to leave something out of your blacklist that needs to be > there (also, future additions to LLVM IR will need to be added to the > blacklist; are you sure you can catch *all* of them?). A whitelist seems >