similar to: [LLVMdev] successfully bootstraped on a i686-linux-gnu

On Fri, 21 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > To work aroud the problem I edited gcc/objc/config-lang.in and removed > the comment from the line > #target_libs=target-libobjc > > With this change it is again possible to build without objc. The > complete configure line was > > ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL > --enable-languages=c,c++

Hi, I recently bootstrapped gcc4 frontend on a i686-linux-gnu too. As I notice, if the llvm "tools-only " was build with srcdir != objdir , the building of llvm-gcc4-1.7.source encountered mistakes of unable to find some header files. So I just edited llvm-gcc4-1.7.source/gcc/Makefile.in and a line like this: INCLUDES += -I$(LLVMOBJDIR)/include With this change, the building errors

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

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

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 >

LLVMers, If you're not working from the CVS "head", you can ignore this. Otherwise, please read it! I have committed changes to CVS head that require changes to your build environment. This is part of PR432. The changes involve getting the CFE to build an executable named llvm-gcc instead of gcc. The hyphenated name was chosen to be consistent with other LLVM tools, it is also

After commit 102300, any obj-c software compiled with clang crashes at launch time with the following stack trace. Reverting this specific commit fix the issue. ------------------------------------------------------------------------------------------------ Date/Time: 2010-04-26 10:07:01.630 +0200 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Interval Since Last Report:

I managed to build a reduced test case: ================== foo.m ================== #include <Foundation/Foundation.h> @interface BaseNode : NSObject <NSCoding, NSCopying> { } @end @implementation BaseNode @end int main(int argc, char **argv) { return 0; } ========================================== # clang -o foo -arch i386 -framework Foundation foo.m foo.m:8:1: warning:

> 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

Hi all, After successfully building llvm tools-only and cfontend, I went back to llvm directory and ran configure --with-llvmgccdir=$CFEINSTALL Unfortunately, at the end of the process I got the following configure: WARNING: ***** llvm C/C++ front end was not found, or does not configure: WARNING: ***** appear to be working. And I do have CFEINSTALL environment variable.... BTW, I have noticed

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

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? >>

Linux GABI [1] introduced new .note.gnu.property section which contains a program property note which describes special handling requirements for linker and run-time loader. LLD does not support .note.gnu.property yet. GABI specifies 2 types of entries: GNU_PROPERTY_STACK_SIZE and GNU_PROPERTY_NO_COPY_ON_PROTECTED: * GNU_PROPERTY_STACK_SIZE: Its pr_data field contains an integer in the format

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

Ignore this at your own peril. I have committed changes to CVS that introduce a fully functional llvm-ar tool, and a new lib/Linker library that uses the archive's symbol table to hasten linking. However, this implies that archives read by the LLVM tools *must* have an LLVM symbol table in them. This happens automatically for the crtend.a library, but not for the runtime libraries produced by

I have a small single-board computer (SBC) I'd like to run OpenSSH on, but when I build the binaries on my development station and copy them over, I get "Illegal Instruction" errors when running them (sshd, ssh-keygen, ssh-add, ssh-agent, ssh-keyscan). I have successfully built zlib 1.2.1 and tested it with minigzip on the SBC, so I don't think the problem is with zlib. I have

But there already was an "install", and it did far more than install the bytecode files. That changed too? On Wed, 10 Nov 2004 23:28:27 -0800 Reid Spencer <reid at x10sys.com> wrote: > Yeah, its just "install" now. > > I'll fix the documentation. > > Reid. > > On Wed, 2004-11-10 at 23:19, Jeff Cohen wrote: > > My rebuild from scratch

Dear People, I have following situation with "OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f": a) I will send files via scp to: "OpenSSH_3.8p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004" b) used command: scp [-vvv] -p -B -C /home/gdg/generation/cr/test_lnx50/lnx50.test2.000001 gdg at lnx50:/home/gdg/EMPFANG/lnx50.test2 Login without PW runs fine,

I think we should wait until there is someone wanting to use these features with lld. Cheers, Rafael ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On March 20, 2018 6:59 AM, George Rimar <grimar at accesssoftek.com> wrote: > Linux GABI [1] introduced new .note.gnu.property section which contains a program > property note which describes special handling requirements for linker and run-time

Peter, thanks for the idea! I did it exactly as you described... and I still get "Illegal instruction" on the 386 platform. I also tried # CFLAGS='-mcpu=i386 -march=i386' ./configure --prefix=/my/prefix/here and # CFLAGS="-mcpu=i386 -march=i386" ./configure --prefix=/my/prefix/here just for grins, and all had the same result. Still trying... Thanks, Mike >