Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there"
2011 Jun 11
0
[LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there
Hi Yuri!
On Sat, Jun 11, 2011 at 5:49 PM, Yuri wrote:
> This page says that llvm works on MinGW:
> http://llvm.org/docs/GettingStarted.html
> I tried to build llvm trunk. llvm build now requires Python:
> llvm[2]: Creating 'llvm-lit' script...
> /bin/sh: python: command not found
>
> And current stable python version (3.2) doesn't even build on MinGW (see
>
2011 Jun 11
1
[LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there
On 06/11/2011 09:32, Csaba Raduly wrote:
> There are various precompiled Windows binaries for Python (yes, even
> 3.2), from http://www.python.org/download/ or
> http://www.activestate.com/activepython-3
>
Thanks!
I got msi based installer (3.2) from http://www.python.org/download/.
But llvm build now fails with this message:
File "<string>", line 1
import
2013 May 16
5
[LLVMdev] Test failures
Hi,
Two days ago, the test suite started failing. Initially there were
hundreds of failing tests; now only seven remain.
They appear to be related to SystemZ.
Here's the last failed test:
********************
FAIL: LLVM :: MC/Disassembler/SystemZ/unmapped.txt (11484 of 14435)
******************** TEST 'LLVM ::
MC/Disassembler/SystemZ/unmapped.txt' FAILED ********************
Script:
2014 Nov 18
2
[LLVMdev] Test failure
Hi,
For a couple of days now, one of the tests fails:
FAIL: LLVM :: MC/R600/sopp.s (16225 of 19902)
******************** TEST 'LLVM :: MC/R600/sopp.s' FAILED ********************
Script:
--
/home/csabaraduly/workspace/LLVM/build/Release+Asserts/bin/llvm-mc
-arch=r600 -mcpu=SI -show-encoding
/home/csabaraduly/workspace/LLVM/llvm/test/MC/R600/sopp.s |
2011 Oct 23
5
[LLVMdev] build warnings
On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote:
> Hi Paul,
>
> That should be easy enough, because the LLVM build has no warnings in it!
>
> Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :)
So, all the "variable might be used
2010 Dec 23
3
[LLVMdev] LLVM on Cygwin: why tests don't run
Hi all,
LLVM+clang builds fine under Cygwin 1.7, but "make check-all" fails to
run because lit doesn't find the freshly built clang. The reason is as
follows: in llvm/utils/lit/lit/Util.py, in the "which" method, there's
66: # Get suffixes to search.
67: pathext = os.environ.get('PATHEXT', '').split(os.pathsep)
The problem is, PATHEXT is imported
2013 May 16
1
[LLVMdev] Test failures
On Thu, May 16, 2013 at 11:30 AM, Renato Golin <renato.golin at linaro.org> wrote:
> On 16 May 2013 09:01, Csaba Raduly <rcsaba at gmail.com> wrote:
>>
>> "s390x--linux-gnu" seems wrong: either there's a dash too many or a
>> word too few.
>
>
> Nope, this triple is correct. The canonicalization of the triple (actually a
> quadruple)
2011 Feb 09
3
[LLVMdev] Building LLVM on Cygwin.
On Wed, Feb 9, 2011 at 9:40 AM, NAKAMURA Takumi <geek4civic at gmail.com>wrote:
> Anand,
>
>
> I have not tried building llvm-gcc, though, ...
>
> Please show me "/path/to/config.status --version".
>
[Anand] Here is the config.status output taken from '/cygdrive/c/llvm-2.8':
./config.status --version
llvm config.status 2.8
configured by
2011 Dec 08
2
[LLVMdev] Executable file size comparison
On Thursday, December 08, 2011 02:46:39 AM Csaba Raduly wrote:
> On Wed, Dec 7, 2011 at 9:43 PM, Richard Pennington wrote:
> > I compiled a program and standard library using clang/LLVM and found the
> > results interesting:
> >
> > text data bss dec hex filename
> > 141312 4076 16668 162056 27908 bzip2.arm
> > 131764 4076
2011 Feb 10
0
[LLVMdev] Building LLVM on Cygwin.
Hi Anand
On Wed, Feb 9, 2011 at 7:19 PM, Anand Arumugam wrote:
> On Wed, Feb 9, 2011 at 9:40 AM, NAKAMURA Takumi wrote:
>>
>> Anand,
>>
>>
>> I have not tried building llvm-gcc, though, ...
>>
>> Please show me "/path/to/config.status --version".
>
> [Anand] Here is the config.status output taken from '/cygdrive/c/llvm-2.8':
2013 Nov 14
2
[LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose
Yes, ARM normally runs as a little-endian and it is a 32-bit CPU. It CAN
be configured to be a big-endian system, but that requires hardware support
as far as I know.
I do have an old, slow Mac Mini G4 PowerPC (big-endian) that I could hook
up as a builder too. I was thinking of it the moment you mentioned big
endian. I actually bought it for testing C++ code on because big-endian
machines are
2011 Oct 20
4
[LLVMdev] error building clang
The latest in my problems building clang-only:
llvm[4]: Linking Debug+Asserts executable clang
/llvm/build/Debug+Asserts/lib/libclangLex.a: could not read symbols: File
format not recognized
collect2: ld returned 1 exit status
Any suggestions appreciated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2011 Jan 11
2
[LLVMdev] clang+LLVM fails to compile ctags
clang version 2.9 (trunk 123166)
Target: x86_64-unknown-linux-gnu
Thread model: posix
Fails to compile ctags 5.8 (also 5.6), specifically eiffel.c:
$ clang -v -c e.c -O2 -Wno-unused-value
clang version 2.9 (trunk 123166)
Target: x86_64-unknown-linux-gnu
Thread model: posix
"/home/csaba/bin/clang" -cc1 -triple x86_64-unknown-linux-gnu
-emit-obj -disable-free -main-file-name e.c
2015 Oct 14
3
../../../Makefile.common:60:../../../Makefile.config:don't have that file or directory
I installed LLVM3.7.0 according to the LLVM document. I can use
"clang","LLVM-dis"commands ,and so on.
but when I execute commad "make" at llvm/lib/Transform/Hello directory, the
error is :
../../../Makefile.common:60:../../../Makefile.config:don't have that file
or directory
../../../Makefile.common:68:../../../Makefile.rules:don't have that file or
2011 Apr 20
3
[LLVMdev] Is this a bug in clang?
This code is undefined, meaning that all bets are off, don't do it.
I.e. It reads the value of I between two sequence points and uses it
for something other than determining the value written. From: Csaba
Raduly
Sent: Tuesday, April 19, 2011 3:44 AM
To: Joe Armstrong
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Is this a bug in clang?
Hi Joe
On Tue, Apr 19, 2011 at 10:59 AM, Joe
2013 Nov 14
0
[LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose
On Thu, Nov 14, 2013 at 4:40 AM, Mikael Lyngvig wrote:
> Yes, ARM normally runs as a little-endian and it is a 32-bit CPU. It CAN be
> configured to be a big-endian system, but that requires hardware support as
> far as I know.
>
> I do have an old, slow Mac Mini G4 PowerPC (big-endian) that I could hook up
> as a builder too. I was thinking of it the moment you mentioned big
2011 Oct 21
0
[LLVMdev] error building clang
On Thu, Oct 20, 2011 at 10:59 PM, monica j wrote:
> The latest in my problems building clang-only:
>
> llvm[4]: Linking Debug+Asserts executable clang
> /llvm/build/Debug+Asserts/lib/libclangLex.a: could not read symbols: File
> format not recognized
> collect2: ld returned 1 exit status
What is the output of
file /llvm/build/Debug+Asserts/lib/libclangLex.a
?
Csaba
--
GCS
2011 Jan 11
0
[LLVMdev] clang+LLVM fails to compile ctags
On 11.01.2011, at 12:02, Csaba Raduly wrote:
> clang version 2.9 (trunk 123166)
> Target: x86_64-unknown-linux-gnu
> Thread model: posix
>
> Fails to compile ctags 5.8 (also 5.6), specifically eiffel.c:
>
> $ clang -v -c e.c -O2 -Wno-unused-value
> clang version 2.9 (trunk 123166)
[…]
> bool<unnamed>::LoopRotate::rotateLoop(llvm::Loop*): Assertion `DidIt
>
2013 May 16
0
[LLVMdev] Test failures
On 16 May 2013 09:01, Csaba Raduly <rcsaba at gmail.com> wrote:
> "s390x--linux-gnu" seems wrong: either there's a dash too many or a
> word too few.
>
Nope, this triple is correct. The canonicalization of the triple (actually
a quadruple) always print all fields, empty or not.
I'm not sure what's going on, though. How are you building this? Is your
2013 May 16
0
[LLVMdev] Test failures
Csaba Raduly <rcsaba at gmail.com> wrote:
> error: no disassembler for target s390x--linux-gnu
The SystemZ disassembler was only recently added. To process major changes
to the source tree like the addition of a completely new component, it
seems to be necessary to explicitly re-run configure (or sometimes even
remove the build directory completely and start from scratch). I've