search for: fixhead

...ume you have an Mac with an Intel processor. Yes. Sorry, I forgot to mentioned it in the mailbody. > Download this: > http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz I think that is the same tarball I used before. > Let me know if that doesn't work. Again: there is no fixheader-script like you describe here http:// llvm.org/docs/GettingStarted.html#quickstart. (in the gcc3 frontends there are fixheader-scripts, but there is no gcc3-frontend for darwin intel/x86) And I think it is necessary. Some gcc output: ----------------------------------------------------------...

...think that is the same tarball I used before. Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is a binary for llvm-gcc4 for Mac x86. You don't need to compile anything or fix any headers. >> Let me know if that doesn't work. > > Again: there is no fixheader-script like you describe here http:// > llvm.org/docs/GettingStarted.html#quickstart. (in the gcc3 frontends > there are fixheader-scripts, but there is no gcc3-frontend for darwin > intel/x86) There is no fixheader script for llvm-gcc4. That is for llvm-gcc3. Lastly, I think maybe I m...

Hi, I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on my old ppc-based mac). There are no fixheaders-script and no include directories ... Are there working gcc 4 binaries? Did I miss some informations on the llvm-webpage? Or do I have to build my own gcc frontend? Thank you Nico

...hings from fresh perspectives sometimes :) > > -Chris > Actually, my request for more info in the "Getting Started" had some hidden questions, as I don't know the answer to them :) So to be a little more clear, here are the two I had: Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 frontends uses? Is it possible to install both the gcc4 and the gcc3.4 frontends at the same time, or are they mutually exclusive? If so, how? If not, would it require a full rebuild, and renaming the executables something like llvm-gcc3? Thanks again, -e

...f the rare facts I understand ;-) > You don't need to compile anything or > fix any headers. Ok. But then it doesn't work. Or I forgot to set pathes or make to less links ... I don't know. >>> Let me know if that doesn't work. >> >> Again: there is no fixheader-script like you describe here http:// >> llvm.org/docs/GettingStarted.html#quickstart. (in the gcc3 frontends >> there are fixheader-scripts, but there is no gcc3-frontend for darwin >> intel/x86) > > There is no fixheader script for llvm-gcc4. That is for llvm-gcc3. Ok....

> I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I > think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on > my old ppc-based mac). There are no fixheaders-script and no include > directories ... > Are there working gcc 4 binaries? Did I miss some informations on the > llvm-webpage? > Or do I have to build my own gcc frontend? I assume you have an Mac with an Intel processor. Download this: http://llvm.org/releases/1.8/llvm-gcc4-1.8-x...

Erick Tryzelaar wrote: > Actually, my request for more info in the "Getting Started" had some > hidden questions, as I don't know the answer to them :) So to be a > little more clear, here are the two I had: > > Does the gcc4 no longer need the "fixheaders" script that the gcc3.4 > frontends uses? > > Is it possible to install both the gcc4 and the gcc3.4 frontends at > the same time, or are they mutually exclusive? If so, how? If not, > would it require a full rebuild, and renaming the executables > something like llvm-...

Hi, I have written a ModulePass (c++ code) that does transformation to LLVM bytecode. How do I build,compile and run it on windows. a) I need Win32 LLVM tools. (so I downloaded)b) How do I build the dll( modulepass) so that I can pass it to optimizer or other llvm tool.c) To test, I need to compile a test C code, emit llvm intermediate code and pass it to optimizer so  that it can run my

...the front end don't cover the gcc4 package. Here are the couple things I'd wish could be fleshed out a bit more: Under "Getting Started Quickly (A Summary)", it'd be nice if the section 4 could also have an example for gcc4. Since that package doesn't include a "fixheaders" script, it's unclear whether or not there's anything that I need to do after I extract the code. Under "Getting Started With LLVM", section "Terminology and Notation", the description of "LLVMGCCDIR" should be extended to also say "or where ev...

(*) The “Getting Started Quickly” section describes commands using gunzip; the binaries are distributed using bzip2 instead. (*) The directory structure after step 4 doesn’t have a “llvm-3.4” or “platform” directory; no such command ‘fixheaders’ can be found. (*) The docs aren’t clear as to which “source code” is needed for step 5: the LLVM source code, or one of the GCC front-end source bundles. I’m assuming the LLVM source code, but links here to the most-recent-released-bundles for each would be *very* helpful here. (*) There are...

...on't believe that the build system for LLVM proper is the problem. I think the problems stem from the following: o) The llvm-gcc binary distributions take awhile due to the following complications: o After building it, I put the build into a cfrontend directory and add copyright files and fixheader scripts. o For systems in which I don't want to deal with header file licensing issues (i.e. Solaris and MacOS X), I remove all of the system headers that GCC fixed when I built it. o Building llvm-gcc and LLVM is sort of a chicken and egg problem. I have to build LLVM, then llvm-gcc, a...

...a new GCC Frontend for PowerPC/MacOS X on the LLVM 1.5 Download page. This frontend is identical to the previous one for 1.5, except that MacOS X header files that were fixed by the GCC build process are no longer included in the distribution. These header files should be fixed by running the fixheaders script included with the GCC Frontend. If you have any problems using the new GCC frontend, please email the llvmdev list so that we can look into it. Thanks. -- John T. -- John T. Criswell Research Programmer University of Illinois at Urbana-Champaign "It's today!" said Pigl...

...over the gcc4 > package. Here are the couple things I'd wish could be fleshed out a bit > more: > > Under "Getting Started Quickly (A Summary)", it'd be nice if the section > 4 could also have an example for gcc4. Since that package doesn't > include a "fixheaders" script, it's unclear whether or not there's > anything that I need to do after I extract the code. > > Under "Getting Started With LLVM", section "Terminology and Notation", > the description of "LLVMGCCDIR" should be extended to also say...

Erick Tryzelaar wrote: >> It's a "least surprise" issue. If gcc3 produces bytecode directly, why >> did the gcc4 driver create such a large departure from original, >> expected functionality? It's a rhetorical question, BTW. >> > > I actually know this one :) I believe the powers that be decided that > having a gcc-compatible interface was

On Thu, 24 Aug 2006, Scott Michel wrote: > That's why I would either make sure that the difference is highlighted > in the FAQ and that the difference is highlighted in the "Getting > Started" pages. Otherwise, it'll remain a mailing list FAQ. Patches welcome. Please send a patch, or even just some suggested text, and we'll be happy to include it. Remember that

> (*) The �Getting Started Quickly� section describes commands using gunzip; > the binaries are distributed using bzip2 instead. > > (*) The directory structure after step 4 doesn�t have a �llvm-3.4� or > �platform� directory; no such command �fixheaders� can be found. These two sections have been fixed. Thanks! > (*) The docs aren�t clear as to which �source code� is needed for step 5: > the LLVM source code, or one of the GCC front-end source bundles. I�m > assuming the LLVM source code, but links here to the > most-recent-releas...

On Sun, 2004-10-10, Misha Brukman asked "Why can't we use wildcards instead of listing all the sources" and then wrote in response to my reply: > On Sun, Oct 10, 2004 at 04:40:48PM -0700, Reid Spencer wrote: > > http://www.gnu.org/software/automake/manual/html_mono/automake.html#wildcards > > > > is your answer. > > I think their "answer" is

...d system for LLVM proper is the > problem. I think the problems stem from the following: > > o) The llvm-gcc binary distributions take awhile due to the following > complications: > o After building it, I put the build into a cfrontend directory and add > copyright files and fixheader scripts. > o For systems in which I don't want to deal with header file licensing > issues (i.e. Solaris and MacOS X), I remove all of the system headers > that GCC fixed when I built it. > o Building llvm-gcc and LLVM is sort of a chicken and egg problem. I > have to bui...