Displaying 20 results from an estimated 287 matches for "crtends".
Did you mean:
crtend
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 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 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?
>>
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
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
2006 Oct 10
1
[LLVMdev] gccas problem with crtend.ll again
> 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
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
>>
>>
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 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:
>
2003 Dec 07
2
[LLVMdev] Can you hint on solution to following problem
gccld: Cannot find linker input file 'crtend.o
I have set the LLVM_LIB_SEARCH_PATH
ls -l $LLVM_LIB_SEARCH_PATH
total 104
-rw-r--r-- 1 muj20 muj20 12788 Dec 7 17:05 crtend.o
-rw-r--r-- 1 muj20 muj20 1984 Dec 7 17:05 libc.bc
-rw-r--r-- 1 muj20 muj20 120 Dec 7 17:05 libcurses.bc
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
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.
2006 Dec 01
1
[LLVMdev] crtend
Before upgrading to the latest LLVM today, I used to run the following
command:
llvm-gcc -fno-inline -o __tmp.homer___ llvmtest/sliceme2.bc
-L/home/testbed1/lefever/work/llvm/install/lib -lcrtend
However, it is given the following error.
/usr/bin/ld: cannot find -lcrtend
collect2: ld returned 1 exit status
make: *** [llvmtest/sliceme2.cbc] Error 1
Has the crtend library been moved?
Thanks,
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?:
2007 Jan 10
4
[LLVMdev] llvm-gcc build fail on RHEL v4 x86_64
...ot; \
LIBGCC2_CFLAGS="-O2 -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem
./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDED " \
MULTILIB_CFLAGS="" T= crtbegin.o crtend.o crtbeginS.o crtendS.o
crtbeginT.o
make[3]: Entering directory `/home/xzx/llvm-gcc-obj/gcc'
make[3]: `crtbegin.o' is up to date.
make[3]: `crtend.o' is up to date.
make[3]: `crtbeginS.o' is up to date.
make[3]: `crtendS.o' is up to date.
make[3]: `crtbeginT.o' is up to date.
make[3]: Leaving dir...
2006 Feb 27
2
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Robert,
Thanks for the info, you've confirmed what I was trying to do, but when
I compile:
-----------------------
#include <stdio.h>
int main(int argc, char *argv[])
{
printf("yo\n");
return 0;
}
-----------------------
without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not
call __main:
-----------------------
; ModuleID =
2017 Jun 02
6
Providing __dso_handle in LLVM
This is a followup to the discussion that started in D28791. To provide the
context, we need a way to provide __dso_handle in Fuchsia. __dso_handle
symbol is mandated by C++ ABI with a value which is an address in one of
the object's segments, and as such this symbol has to be included
statically and cannot be a part of a shared library. Different systems
provide it differently:
1. On
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
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