similar to: [LLVMdev] Trying to compile frontend 4.0 fails on cygwin

In the last step after building and installing binutils 2.21 for ARM and LLVM-src, I am trying to build LLVM-GCC. However, I get the repeated system config checking promt. I used the following configuration:   I created a directory called arm_objects and then I write:   $ ../llvm-gcc-4.2/configure --target=arm-linux --program-prefix=llvm- --prefix=/llv m/arm --enable-pic --disable-optimized

The very first time you build GCC, you should do "make bootstrap". After that, you can use "make" and "make install" Reid. On Fri, 2005-05-20 at 00:15 +0800, thean kiat sew wrote: > Hi, I am still new to LLVM and also GNU softwares. > > I am doing a project using LLVM. > > I was building cfrontend on my windows cygwin, however I encountered >

Hi, I am still new to LLVM and also GNU softwares. I am doing a project using LLVM. I was building cfrontend on my windows cygwin, however I encountered this problem, may I now what is the cause? ******************************** my configuration output is: bash-2.05b$ ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-n ls --disable-shared --enable-languages=c,c++ loading

Thanks for the quick answer! Syncing to r61112 got rid of the ICE, but I still get the following error: make "DESTDIR=" "RPATH_ENVVAR=DYLD_LIBRARY_PATH" "TARGET_SUBDIR=i686-apple-darwin9" "bindir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/bin" "datadir=/Users/jyasskin/src/llvm-gcc-4.2/trunk/obj/../install/share"

Sorry again, my bad. I actually was using --enable-pics instead of --enable-pic. Now LLVM is being compiled. Hope the last phase llvm-gcc compilation would be a success. Thanks a lot. Akramul --- On Sun, 2/1/11, akramul azim <bijoy123_8 at yahoo.com> wrote: From: akramul azim <bijoy123_8 at yahoo.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "Bill Wendling"

Sorry I used --enable-pic, not --enable-pics. It was a typo. Akramul --- On Sun, 2/1/11, akramul azim <bijoy123_8 at yahoo.com> wrote: From: akramul azim <bijoy123_8 at yahoo.com> Subject: Re: [LLVMdev] LLVM for ARM target To: "Bill Wendling" <wendling at apple.com> Cc: "Anton Korobeynikov" <anton at korobeynikov.info>, llvmdev at cs.uiuc.edu Date:

On Tue, Nov 6, 2012 at 2:19 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > Binutils and LLVM > > As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. > > As a start, I'd like to summarize the current status, and

when i run ./configure in fedora 9 64 bit i get this error checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking whether make sets $(MAKE)... yes checking for gcc... gcc -m32 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. this is

Hi, I downloaded wine source from winehq and installed all dependencies as per the wiki: http://wiki.winehq.org/WineOn64bit However when i run ./configure,its displays the following and exits: Code: $ ./configure ## --------- ## ## Platform. ## ## --------- ## hostname = localhost.localdomain uname -m = x86_64 uname -r = 2.6.26.5-45.fc9.x86_64 uname -s = Linux uname -v = #1 SMP Sat Sep 20

Hello, The lack of debian packages for 0.9.13 have made me decide to compile from source instead. So I uninstalled all wine files and downloaded the sources. I'm using a system based mostly on Debian Sarge, but with some backports. I ran ./configure and there were some packages I had to get, but soon it worked well. When I tried make depend the problems started. This is the output I get

Newbie trying to install wine in his Mac OSX, getting the old annoying message, home:~/Desktop/wine G3$ /Users/G3/Desktop/wine/tools/wineinstall WINE Installer v0.75 Running configure... configure: creating cache config.cache checking build system type... powerpc-apple-darwin8.7.0 checking host system type... powerpc-apple-darwin8.7.0 checking whether make sets $(MAKE)... no checking for gcc...

Binutils and LLVM As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. As a start, I'd like to summarize the current status, and ask people for help updating the list. List taken from <http://www.gnu.org/software/binutils/>

On Sat, Jul 25, 2015 at 5:24 PM, Martell Malone <martellmalone at gmail.com> wrote: > It's doable to support dlltool-style import libraries by LLD. .idata >> sections in dlltool-style libraries are designed so that they will >> naturally construct the import descriptor table by just sorting them by >> section name. Supporting them is not hard. > > > I

Hi Avraham, A quick question - I realized I did not have *Perl* installed. So I installed *ActiveState Perl* right now. Also I see I need *texinfo* and *texi2any*. I was able to installed *texinfo* from here: http://gnuwin32.sourceforge.net/packages/texinfo.htm. But not sure where to get *texi2any*. Can you guide me in this step? Regards, Indrajit On Fri, Feb 9, 2018 at 11:58 AM, Indrajit Sen

> > For example the gnu linker provides the section with the stub code and the > offset for injection. Meant to say dlltool here not gnu linker :) On Sat, Jul 25, 2015 at 11:17 AM, Martell Malone <martellmalone at gmail.com> wrote: > Hey guys, > > So I was able to modify dlltool to produce the exact same layout as > lib.exe with the same section numbers etc. >

Hey guys, So I was able to modify dlltool to produce the exact same layout as lib.exe with the same section numbers etc. I've first managed to first create the correct section so that lld gives me link errors and then resolve those errors to create an exe. This is one thing that is still missing that sticks out like a sore thumb In the actual imports of the functions the objects are very

It's doable to support dlltool-style import libraries by LLD. .idata sections in dlltool-style libraries are designed so that they will naturally construct the import descriptor table by just sorting them by section name. Supporting them is not hard. One thing we need to do is that currently we construct the import descriptor directly from short import libraries. We don't create

> > It's doable to support dlltool-style import libraries by LLD. .idata > sections in dlltool-style libraries are designed so that they will > naturally construct the import descriptor table by just sorting them by > section name. Supporting them is not hard. I don't really know my way around the code base of COFF well enough todo this myself. If you can point me in the

Hey everyone! In October/November 2018 I started the implementation of llvm-objcopy for MachO with the long-term plan to build some popular binary-level tools on top of it. That effort stopped at the stage where some boilerplate code for reading/writing MachO files was reviewed & committed to LLVM/tools/llvm-objcopy. Later I started working on llvm-lipo (a drop-in replacing for the tool

I forgot to attach the notes.txt with the objdump. On Thu, Jul 23, 2015 at 3:55 PM, Martell Malone <martellmalone at gmail.com> wrote: > Hi again rui, :) > > I've got all the patches into llvm and clang for supporting mingw-w64 via > compiler-rt and now we are able to build a full mingw-w64 toolchain without > gcc :) > With great help from yaron and rnk. > >