Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] gccas problem with crtend.ll again"
2006 Apr 20
0
[LLVMdev] trying to bootstrap gcc 4.0.1 and the cvs llvm
On Thu, 20 Apr 2006, [UTF-8] Rafael Esp?ndola wrote:
> I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm.
>
> I was able to build the llvm tools without a problem.
> gcc has a small problem (from the apple branch IIRC): libojc is built
> unconditionally, so objc must be in the --enable-languages option for
> the build to be successful.
>
> Building
2006 Apr 20
2
[LLVMdev] trying to bootstrap gcc 4.0.1 and the cvs llvm
I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm.
I was able to build the llvm tools without a problem.
gcc has a small problem (from the apple branch IIRC): libojc is built
unconditionally, so objc must be in the --enable-languages option for
the build to be successful.
Building the rest of llvm fails with
llvm[3]: Compiling crtend.ll to crtend.bc for Debug build
2006 Aug 21
1
[LLVMdev] stdlib.h
Thank you, Reid,
I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get
gccld: warning: Cannot find library 'crtend'
gccld: warning: Cannot find library 'c'
I have the libraries in my llvm directory:
llvm/runtime/GCCLibraries/crtend
Well, how do I link this to the LLVM runtime stuff? Before building from
the source, I had copied all the .h from my old gcc 4.0 to
2006 Nov 16
5
[LLVMdev] 1.9 Prerelease Available for Testing
First, thanks for testing this!
> Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5)
>
> HIGH LEVEL COMMENTS
> * The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't
> that be llvm-1.9?
We have always labeled the dir just llvm which is fine. If you build llvm
it will know its version 1.9.
> * LLVM was built in Release mode
2006 Jul 30
2
[LLVMdev] Building llvm under cygwin
Hi!
I'm trying to build LLVM under cygwin.
I have the latest version of cygwin and CVS versions of llvm, llvm-test and
llvm-gcc.
make of tools only succeeded.
make of frontend succeeded too
but full make of llvm failed on crtend in llvm/runtime/GCCLibraries with the
following message:
llvm[0]: Compiling crtend.c for Debug build (bytecode)
/bin/sh: -c: line 0: syntax error near unexpected
2006 Jul 31
0
[LLVMdev] Building llvm under cygwin
If you're building llvm-gcc4, you don't need the runtime libraries, so
I'd just stick with the "tools-only" build and declare success. If
you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :)
However, the problem appears to be your PATH variable. In your path you
have the following directory: C:/Program Files/Microsoft DirectX SDK
(June
2004 Dec 08
0
[LLVMdev] Building llvm and cfrontend under cygwin
Hi Reid,
> 2. Make sure you aren't trying to link in some old/crufty crtend.bc
> file. Try doing "make uninstall ; make clean" in your crtend
> directory if you think this might be the case.
"make install" fails - there is no such target.
> If those don't clear the problem, please tell me what version
> of LLVM you're trying to compile
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
On Thu, 16 Nov 2006, Tanya M. Lattner wrote:
>> * I don't think this is ready for release. In particular the llvm-gcc4
>> binary
>> seg faults on FC 5 for most of llvm-test programs.
>> * I'm going to re-try without using the binaries and building
>> everything from scratch.
>
> Does llvm-gcc4 seg fault for make check? I've done extensive
2004 Dec 10
1
[LLVMdev] Building llvm and cfrontend under cygwin
Hi Chris,
> Also note, LLVM 1.4 will be released in the next few days, so if
waiting is
> an option, you might choose to do so.
Alright, I've got llvm and llvm-gcc from RELEASE_14 cvs and tried
building it under cygwin.
1) The first problem is with llvm in SysUtils.c:
int executeProgram(const char *filename, char *const argv[], char *const
envp[])
{
................
execveTy
2004 Dec 05
1
[LLVMdev] Building llvm and cfrontend under cygwin
Hi there,
I'm trying to build llvm under cygwin running under windows xp, and have
struck the following problem:
-- llvm: tools-only built ok
-- cfrontend: built ok
-- llvm: full build failed at the following point:
make[3]: Entering directory
`/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend'
Compiling crtend.c to bytecode
Compiling listend.ll to bytecode
Linking comp_main.bc
2004 Aug 19
0
[LLVMdev] Can't get llvmg++ to work
On Wed, 2004-08-18 at 22:14, Jeff Cohen wrote:
> I'm another new person to LLVM.
Hi Jeff. Welcome.
> I can't successfully compile and
> execute a simple C++ program. The compiler seems to work, as it
> produces a.out and a.out.bc files, but I get a whole bunch of warnings:
>
> WARNING: Found global types that are not compatible:
>
2006 Nov 16
0
[LLVMdev] 1.9 Prerelease Available for Testing
Tanya,
Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5)
HIGH LEVEL COMMENTS
* The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't
that be llvm-1.9?
* LLVM was built in Release mode in all cases
* I don't think this is ready for release. In particular the llvm-gcc4
binary
seg faults on FC 5 for most of llvm-test programs.
*
2004 Aug 19
4
[LLVMdev] Can't get llvmg++ to work
I'm another new person to LLVM. I can't successfully compile and
execute a simple C++ program. The compiler seems to work, as it
produces a.out and a.out.bc files, but I get a whole bunch of warnings:
WARNING: Found global types that are not compatible:
"struct.std::messages<wchar_t>"* %_ZN9__gnu_cxx10messages_cE
[16 x sbyte]*
2004 Dec 24
2
[LLVMdev] README: Build Environment Changes
>I successfully build CFE frontend at FreeBSD 5.3.
>
> Next nighttest run show more detail information :)
After last 2 nighttest runs i see stable failure result:
llvm[2]: Compiling dummylib.c for Debug build (bytecode)
llvm-g++: installation problem, cannot exec `gccas': No such file or
directory
gmake[3]: ***
2004 Aug 16
3
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
Chris Lattner wrote:
>On Sun, 15 Aug 2004, Robert Feldt wrote:
>
>
>
>>However, I wonder if someone supplies pre-built cfrontend binaries for
>>cygwin?
>>
>>
>
>Nope, we don't have one yet, sorry.
>
>
>
>>I followed the instructions and tried to build them myself but get
>>when building the cfrontend. Any ideas?
>>
2004 Aug 19
1
[LLVMdev] Can't get llvmg++ to work
On Thu, 19 Aug 2004 08:45:23 -0700
Reid Spencer <reid at x10sys.com> wrote:
> > I'm running FreeBSD 5.2.1 with gcc 3.3.3. I had some problem starting
> > the build as I had to get linux binary emulation to work. (The problem
> > here is that FreeBSD can be made compatible with 5 different distros,
> > and not all of them work with LLVM. I used linux_base-8;
2004 Aug 16
1
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
Misha Brukman wrote:
>On Mon, Aug 16, 2004 at 01:07:39PM +0200, Robert Feldt wrote:
>
>
>>However, when I go back to rebuild llvm, reconfigure, setting the
>>CFEINSTALL dir, then make it can build the tools ok but not the
>>runtime:
>>
>>
>[snip]
>
>
>>Compiling crtend.c to bytecode
>>Files/ATI: not found
>>
>>
2006 Aug 20
2
[LLVMdev] stdlib.h
> Rebuilding llvm-gcc4 from source should work fine. Please see the
> directions in the file README.LLVM at the top level src directory. You
> can check llvm-gcc4 out from Subversion with the command:
Dear guys,
I've rebuild my llvm-gcc3 (not llvm-gcc4) from source, and now it can
find stdlib.c and all the other sources, but I am having some other
problems with the new
2004 Dec 24
0
[LLVMdev] README: Build Environment Changes
Sloppy me. I fixed the path for llvm-gcc but not for llvm-g++. My last
patch to Makefile.rules fixes that so it should start working again.
Reid.
On Fri, 2004-12-24 at 05:21, Vladimir Merzliakov wrote:
> >I successfully build CFE frontend at FreeBSD 5.3.
> >
> > Next nighttest run show more detail information :)
>
> After last 2 nighttest runs i see stable failure
2004 Aug 20
2
[LLVMdev] Can't get llvmg++ to work
On Thu, 19 Aug 2004 08:45:23 -0700
Reid Spencer <reid at x10sys.com> wrote:
>
> Also, as a general note, make sure you follow precisely the steps for
> building the c front end. If you discover any BSDisms that aren't
> documented, we'd love to hear about them.
>
> Thanks,
>
> Reid.
>
OK. I've built the front end without any heartaches, but I did