Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Building llvm and cfrontend under cygwin"
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
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:
>
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 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 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
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?
>>
2003 Oct 26
2
[LLVMdev] redhat 9, compiling llvm-1.0.tar.gz
Hi all,
compilation of package llvm-1.0.tar.gz under redhat 9 is failed with following output:
-------
make[3]: *** No rule to make target `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/C++-Exception.bc', needed by `/home/vak/llvm/llvm/lib/BytecodeLibs/libcrtend.bc'. Stop.
make[3]: Leaving directory `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend'
...skipped
-------
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
0
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
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
[snip]
> I don't understand the error message since I see no reference to
> Files/ATI. Any clues?
Can
2004 Aug 15
0
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
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?
That is really wierd. Looking at that line of gcc.c, I have no idea how
it ever worked. In any case, this
2004 Aug 20
0
[LLVMdev] Can't get llvmg++ to work
Hi Jeff,
On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote:
> OK. I've built the front end without any heartaches, but I did
> encountered the following glitches:
>
> The documentation of --with-llvmgccdir is a bit ambiguous. I had to try
> several paths before I got the right one. It should state that the
> directory is <path>/cfrontend/<platform>/llvm-gcc.
2004 Aug 15
2
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
Chris Lattner wrote:
> LLVM Compiler Infrastructure -- Release 1.3
> http://llvm.cs.uiuc.edu
>
>We are pleased to announce the release of version 1.3 of the LLVM
>Compiler Infrastructure.
>
>
>
Great news, thanks.
However, I wonder if someone supplies pre-built cfrontend binaries for
cygwin?
I followed the instructions and tried to
2005 Jan 09
1
[LLVMdev] Cygwin build is still broken
Happy New Year all,
I've just updated to the latest CVS version and cygwin port is still
broken. When building full llvm:
llvm[3]: Compiling crtend.c for Debug build (bytecode)
llvm[3]: Compiling listend.ll for Debug build
llvm[3]: Linking comp_main.bc component...
assertion "(Result->isFirstClassType() || Result == Type::VoidTy ||
isa<OpaqueType>(Result)) && "LLVM
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
>>
>>
2005 Jan 26
3
[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi
Hi Jeff and others,
When building the llvm runtime, I always get this error message: 'Can't
destroy file: The process cannot access the file because it is being used by
another process.' The file is destoyed anyway.
I think that the the real error is the path for the file (*/\file.tmp).
However, I can't find the bug in the source. Do you have any clue?:
2005 Jan 26
0
[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi
It looks like what you're getting is a sharing violation. Although, I
don't understand why. The llvm-ar.exe when its building an archive file
always builds it in a temporary. Only when that is complete does it
remove the old one and rename the temporary. Perhaps this is a result of
doing parallel build and the "lib3.tmp" file (that name looks wrong to
me) is being accessed by
2005 Jan 26
1
[LLVMdev] Building the llvm runtime: 'Can't destroy file: Theprocess cannot access the fi
Hi Reid,
I don't think I've initiated a parallel build by this command:
------------------------
make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapi
LDFLAGS+='-Wl,--no-keep-memory' -r VERBOSE=1
------------------------
Henrik.
>From: Reid Spencer Date: Wed, 26 Jan 2005 12:05:51 -0800
>
>It looks like what you're getting is a sharing violation. Although, I
2004 Jul 21
0
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Chris Lattner wrote:
>
> Yes, this makes a tremendous amount of sense. Do you think you could
> prepare some patches to make this happen? If you have any questions, feel
> free to ask :)
Ok, a patch[1] is attached. I didn't care to coerce the offset, since I
assume that it is an uint, but maybe I should? Hopefully I've understood
the llvm source
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote:
>
> Hi, I'm thinking out loud, please give me some feedback.
>
> Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are
> implemented as:
>
> llvm.gcread(sbyte** object, uint offset)
> llvm.gcwrite(sbyte* data, sbyte** object, uint offset)
>
> Where you also have the offset into the object. In
2004 Dec 22
0
[LLVMdev] More on Cygwin
Privet,
> > Unfortunately, at the end of the process I got the following
> > configure: WARNING: ***** llvm C/C++ front end was not
> > found, or does not appear to be working.
> Yes, Reid changed the CFE build instructions to add
> "--program-prefix=llvm" to the end of the configure line, but
> autoconf and Makefiles are not yet updated with that change.