similar to: [LLVMdev] trying to build llvm-gcc for arm, error: 'V1DI_pointer_node' undeclared (first use in this function)

You need to configure with --enable-llvm. (It would still be nice if V1DI_pointer_node was defined; I'll take a look at that.) On May 20, 2010, at 1:04 PM, Anatoly Yakovenko wrote: > i am getting this compilation error: > > > gcc -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic >

any ideas what library has these symbols lang_eh_catch_all get_pointer_alignment validate_arglist i get these linker errors when trying to link llvm-gcc: make[1]: Entering directory `/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-gcc-4.2-2.7.source-objtree' make[2]: Entering directory

I am trying to build a cross compiler for arm on linux, here is how i have configured it cd llvm-gcc-4.2-2.7.source-objtree ../llvm-gcc-4.2-2.7.source/configure --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 --enable-multilib --enable-target-optspace --enable-interwork --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++

> ../llvm-gcc-4.2-2.7.source/configure > --enable-llvm=/home/anatolyy/qctp406/pakman/depot/users/anatolyy/proto/crosscompiler/llvm-2.7 > --enable-multilib --enable-target-optspace --enable-interwork > --with-newlib --with-gnu-as --with-gnu-ld --enable-languages=c,c++ > --target=arm-elf This means that the compiler is built for ARMv4 which is not pretty good supported. Try to switch

Hi Anatoly, > any ideas what library has these symbols > > lang_eh_catch_all > get_pointer_alignment > validate_arglist it sounds like you are trying to build a version of llvm-gcc without LLVM enabled. Did you specify --enable-llvm=path_to_llvm_build_directory when configuring llvm-gcc? These symbols are all defined in llvm-gcc itself, but only when ENABLE_LLVM is defined.

Hi Koen, The process to build llvm-gcc as a crosscompiler is basically the same as build a normal gcc as crosscompiler. The differences: you need a LLVM installed (compiled for the host). You must configure llvm-gcc with --enable-llvm. Problems: - Today LLVM supports ARM/EABI, but llvm-gcc don't. You must apply the patch:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anton Korobeynikov schreef: > Hello, Koen. > >> So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 >> to ARM/EABI? > Well, just supply appropriate --host/--target options to configure. To llvm or llvm-gcc4? > I haven't tried ARM, but this definitely works for crosscompiling from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After hearing Chris' talk at bossaconference I wanted to see if I could use LLVM (and/or llvm-gcc) as a crosscompiler for ARM. The documentation beautifully outlines how to build it for your host and how to crosscompile it, but not how to build it as a cross-compiler. So my question is: How should I build llvm and llvm-gcc4 to have it

Hi, We have been working on porting llvm-gcc crosscompiler (basically I had to create new dummy target configuration with some minimal information about the our processor, endianess, type sizes, etc.) which compiles llvm bytecode (doesn't compile native binaries nor assembler) for our processor architecture and new llvm target for our custom processor. We already managed to compile also

On Sun, 2007-04-01 at 21:26 +0200, Koen Kooi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > After hearing Chris' talk at bossaconference I wanted to see if I could use LLVM (and/or > llvm-gcc) as a crosscompiler for ARM. The documentation beautifully outlines how to build > it for your host and how to crosscompile it, but not how to build it as a

Hello, Koen. > So my question is: How should I build llvm and llvm-gcc4 to have it cross-compile from x86 > to ARM/EABI? Well, just supply appropriate --host/--target options to configure. I haven't tried ARM, but this definitely works for crosscompiling from linux to mingw32. Please also note, that you'll need native (=arm) tools (binutils, libcheaders, etc) during gcc build

We currently use KLIBCKERNELSRC and KLIBCKERNELOBJ variables which used to be required to point to a kernel source and object directories. However the kernel headers were reorganised starting in Linux 3.7 such that that doesn't work properly. This series removes KLIBCKERNELOBJ and changes the use and documentation of KLIBCKERNELSRC to be consistent. Ben. Ben Hutchings (4): [klibc]

Previously klibc $(objtree)/.config depended on the kernel output directory. This would cause 'defconfig has changed, please remove or edit .config' build errors if $(KLIBCKERNELOBJ) directory was modified. This directory dependency is a false dependency that does not indicate that the target, $(objtree)/.config, needs to be regenerated. Signed-off-by: Greg Thelen <gthelen at

On Tue, Apr 28, 2020 at 05:16:33PM +0200, Joerg Roedel wrote: > From: Joerg Roedel <jroedel at suse.de> > > Install an exception handler for #VC exception that uses a GHCB. Also > add the infrastructure for handling different exit-codes by decoding > the instruction that caused the exception and error handling. > > Signed-off-by: Joerg Roedel <jroedel at suse.de>

On Tue, Apr 28, 2020 at 05:16:33PM +0200, Joerg Roedel wrote: > From: Joerg Roedel <jroedel at suse.de> > > Install an exception handler for #VC exception that uses a GHCB. Also > add the infrastructure for handling different exit-codes by decoding > the instruction that caused the exception and error handling. > > Signed-off-by: Joerg Roedel <jroedel at suse.de>

The following patchset implements 3 seperate series of changes. External Building ================= Patches 1 through 8 enable to use of klibc's build system while leaving the src tree pristine (and potentially read only). Specifically: - srctree=<Sources for klibc> - objtree=<Ouput directory for klibc> - KLIBCKERNELSRC=<Kernel sources> - KLIBCKERNELOBJ=<Kernel

i have just downloaded the course code for wine for my ps3 but when i run './tools/wineinstall' i get the error message 'port.c:183:2: error: #error You must implement wine_switch_to_stack for your platform' i also get the error after i run 'make' (after i run ./configure' and 'make depend' now is it because wine does not support ps3?? or is there something i

From: Heiko Carstens <heiko.carstens@de.ibm.com> vfork support for s390/s390x. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- diff -purN a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def --- a/usr/klibc/SYSCALLS.def 2006-06-07 09:44:33.000000000 +0200 +++ b/usr/klibc/SYSCALLS.def 2006-06-07 13:01:54.000000000 +0200 @@ -28,7 +28,7 @@ void _exit,exit::_exit(int) ; A

Hi, I'm getting a returning build failure when building a linux->windows crosscompiler out of LLVM/Clang. Attached is config.log and below is the output of "make VERBOSE=1" llvm[2]: Linking Release executable FileCheck (without symbols) g++ -I/home/ruben/mingw-w64/toolchain/linux64mingw64/llvm-clang/include

Hi Ruben, Try adding a --build=x86_64-gnu-linux option to configure as well. I don't have that configuration locally, so I can't check to be certain, but IIRC, our configure wants all three for a cross compile like this. -Jim On Aug 21, 2011, at 7:19 AM, Ruben Van Boxem wrote: > Hi, > > I'm getting a returning build failure when building a linux->windows >