similar to: [LLVMdev] Where do header files patched with llvm-gcc come from?

Hi 陈晓宇, > The llvm-gcc front end mingw binary on llvm.org <http://llvm.org> has patched a > lot of *.h files under include directory. But when building llvm-gcc on mingw > myself, there is no header file generated under include directory. So where do > these header files come from? I am concerned for their licenses. if you mean the top level include directory in the llvm-gcc

I just tried to compile llvm-gcc against the top of llvm and I ran into this error: /.../llvm/llvm-gcc-build/./prev-gcc/xgcc -B/.../llvm/llvm-gcc-build/./prev-gcc/ -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c -DHAVE_CONFIG_H -g -O2 -I. -I/.../llvm/llvm-gcc-4.2/libiberty/../include  -W -Wall -pedantic -Wwrite-strings -Wstrict-prototypes -Wc++-compat

I was building llvm2.9 using MinGW64 on windows, msys was 32 bit so I specified --host option for a cross compiling. Following are my configure options: ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj --host=x86_64-w64-mingw32 --disable-multilib The error: make[1]: Entering directory `/home/AutoESL/llvm-obj/lib/VMCore' make[1]: ***

Hello > The llvm-gcc front end mingw binary on llvm.org has patched a lot of *.h > files under include directory. But when building llvm-gcc on mingw myself, > there is no header file generated under include directory. So where do these > header files come from? I am concerned for their licenses. These are ordinary mingw-runtime and w32-api headers. As far as I remember, only

Chen, see http://llvm.org/docs/GettingStarted.html#pf_12 ...Takumi ps. Excuse me, PE+ (aka pep) means "Executable file format for WIndows x64". 2011/5/16 陈晓宇 <xychen0921 at gmail.com>: > The stack trace: > > Starting program: > C:\MinGW\msys\1.0\home\xchen\llvm-obj\lib\Target\CellSPU/../.. > /../Debug/bin/tblgen.exe -I

Chen, 2011/5/13 陈晓宇 <xychen0921 at gmail.com>: > ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj >                             --host=x86_64-w64-mingw32 >                             --disable-multilib Please try with "--build=x86_64-w64-mingw32", not "--host". If you would still have any troubles, make sure your x86_64-w64-g++.exe can generate correct

On Aug 15, 2009, at 5:05 PM, Erick Tryzelaar wrote: > I just tried to compile llvm-gcc against the top of llvm and I ran > into this error: > > /.../llvm/llvm-gcc-build/./prev-gcc/xgcc > -B/.../llvm/llvm-gcc-build/./prev-gcc/ > -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c > -DHAVE_CONFIG_H -g -O2 -I. > -I/.../llvm/llvm-gcc-4.2/libiberty/../include -W

When compile 403.gcc, there are link errors. 1) environment 1.1) OS Linux gnode107 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux *1.2) The default GCC compiler is * gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for

debug1: X11 connection requested. debug2: fd 20 setting TCP_NODELAY debug2: fd 20 is O_NONBLOCK debug2: fd 20 is O_NONBLOCK debug1: channel 3: new [X11 connection from 127.0.0.1 port 47773] debug1: channel 3: open confirm rwindow 3000 rmax 35840 debug1: server_input_channel_req: channel 3 request exit-status reply 0 debug1: session_by_channel: unknown channel 3 debug1: dump: used 1 session 0

Hi , I open secure Session with X11 forwarding. when run any standard X applicattion like xterm xclock it come up without any error. I start my user X application it fails. On User application side it fails when "xtOpenDisplay" system call with localhost:10.0. On SSH server debug message are : > debug1: X11 connection requested. > debug2: fd 20 setting TCP_NODELAY >

Rails users, what are your current best practices for dealing with post-1.0.0 rails bugfixes on your rails apps? * Are you using the latest rails revision? * Are you using some nameless revision you froze some time ago? * Are you downloading and applying specific patches to rails-1.0.0? Rails core, what are your thoughts about periodically applying a few backwards-compatible patches to

Hi - if I have a doubly patched kernel (2.4.5) (1) Apply gkernel/CVS ext3 patches (2) Apply Neil Brown/Reiserfs team knfsd and reiserfs patches Will ext3 be exportable by knfsd (i.e. inherit automagically the nfsd_operations thingies from ext2) or does it need further patching? -- Chan Shih-Ping (Richard) <cshihpin@dso.org.sg> DSO National Laboratories 20 Science Park Drive

I''ve the same problem of Julien Bisconti. Can someone help me ? I try to compile iproute2 for my target ppc 8260. Thank you !

oh ok, hmm the game still crashed :(

Hello, I''ve applied ``bridge-utils-0.9.5-ipmode-1.diff'''' to be able to use my shaper as bridge and don''t lose the netfilter capabilities, the patch applies with no error messages, which makes me supose everything is working fine. But when i try to recompile the bridge-utils utilities i get the message transcript below:

Hi all, Here is the context. We are running Samba in a DCE/DFS environnement on AIX box (4.3.3 and 5.2). We've patched the Samba source to support this environnement (although, we didn't created the patch, someone working for IBM US dit it). We are using Samba 2.2.7b and 2.2.8a. We have a lot of Samba connections (400-600 shares everytime, 24 hours per day). We were running with only

Using R 2.6.0 patched I was able to calculate the variance of each row of a matrix without error, even if some rows had only NAs. I would just get NAs back as the variance for those rows. Now with R 2.7.0 patched I get an error "no complete element pairs" if any one row has all NAs. Can anyone tell if I can make R 2.7.0 patched behave as R 2.6.0 did so I don't have to change all my

Hey, can someone upload the patched buffer.c file somewhere? I don't got GIT and an if i try to patch it via the patch command i get the following error: > patching file dlls/wined3d/buffer.c > patch unexpectedly ends in middle of line > Hunk #1 succeeded at 1512 with fuzz 1 (offset 13 lines).

Hello, Again it's not possible to compile the patched FUSE on gluster.org against newest linux kernels, and the question came up: why isn't there a patch against the kernel tree's FUSE? It seems to be much newer, and would obviously compile against the kernel. Another question is due to my lack of knowledge of the reasons behind: why is it required to patch FUSE at all? Why

Hi, Sorry for that ..... Today R did load both ca and rgl packages with no problems ... the single thing i've done since Friday was to put "defrag" on drive C, i even didn't re-start the computer ...actually it was re-started several time with same weird problem ... so i suppose something was segmented badly on the hard drive. Monica > From: pisicandru at hotmail.com >