similar to: [LLVMdev] Re: [llvm-commits] CVS: llvm/lib/Target/PowerPC/PPC32AsmPrinter.cpp

LLVM build without big problems in obj dir == src dir case (for example, last night tester build) But I have problem with building CVS version LLVM in obj dir != src dir case. ======= Finished building ModuleMaker debug executable (without symbols) ======= gmake[2]: Leaving directory `/usr/home/wanderer/pkg/build/llvm/obj/examples/ModuleMaker' gmake[1]: Leaving directory

I can't boostrap LLVM CFE at FreeBSD with current LLVM and LLVM CFE CVS sources. GCC bootstrap terminated with error: /usr/home/wanderer/pkg/build/llvm/objcfe/gcc/xgcc -B/usr/home/wanderer/pkg/build/llvm/objcfe/gcc/ -B/home/wanderer/pkg/build /llvm/night/cfe/i386-unknown-freebsd5.3/bin/ -B/home/wanderer/pkg/build/llvm/night/cfe/i386-unknown-freebsd5.3/lib/ -isystem

I resend email with updated (after mass header move) log examples. > LLVM build without big problems in obj dir == src dir case (for example, > last night tester build) > But I have problem with building CVS version LLVM in obj dir != src dir > case. > gmake[1]: Entering directory `/usr/home/wanderer/pkg/build/llvm/obj/projects' gmake[2]: Entering directory

>> This looks like your crtend.a file did not get built correctly. Try >> doing >> make clean/make install in llvm/runtime/ again. >> > gmake clean in llvm/runtime/ remove all build tree of nighttest starting > with llvm/runtime/../.. > And then i can't do gmake install :) > > Ok > I will rebuld llvm and check build logs for crtend.a creating and

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >> because (I believe) of an upgrade that happened on the machine (the >> qmtest >> binary doesn't work anymore?). Are you seeing a problem on freebsd where >> the feature tests go into a loop? If so, can you provide us with more >> information? >> make, ~ > ps -xu

Command from LLVM CFE bootstrap sequence at FreeBSD: gmake -C runtime install-bytecode terminated with error (verbose mode): --8X------------------------------------------------------- llvm[2]: Installing Debug Bytecode Archive /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a /usr/bin/install -c -D /usr/home/wanderer/pkg/build/llvm/obj/Debug/lib/libcrtend.bca

A typo in test/Makefile was the trigger for this problem: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ 020216.html John, can you please look into this bug some more and add some error checking to the llvm-specific qmtest python modules to make this error less severe? Thanks! -Brian On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: > > I think there is a very

Current CVS version LLVM install failed for me with error: gmake[2]: Entering directory `/usr/home/wanderer/pkg/build/llvm/obj/tools/llvmc' llvm[2]: Installing Configuration Files To /home/wanderer/pkg/llvm/etc/llvm llvm[2]: Installing Debug /home/wanderer/pkg/llvm/bin/llvmc llvm[2]: Installing additional C++ configuration clones install: /cc: Permission denied gmake[2]: *** [install] Error

Brian Gaeke wrote: > > A typo in test/Makefile was the trigger for this problem: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ > 020216.html > > John, can you please look into this bug some more and add some error > checking to the llvm-specific qmtest python modules to make this error > less severe? Does the fork bomb occur in the

>I successfully build CFE frontend at FreeBSD 5.3. > > Next nighttest run show more detail information :) After last 2 nighttest runs i see stable failure result: llvm[2]: Compiling dummylib.c for Debug build (bytecode) llvm-g++: installation problem, cannot exec `gccas': No such file or directory gmake[3]: ***

For VC++, I solved this by having bison/flex put the files into the obj directories. I also have it unconditionally regenerate the files if bison/flex is available, and copy them from src if they are not. Chris Lattner wrote: > On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote: > >> I can't build LLVM CFE after this patchs >>

No solutions come to mind. Conflicts are conflicts and must be resolved manually. This situation should only occur if you change the .l/.y file and then update the .h/.cpp files after someone else has changed the .l/.y file and regenerated the .h and .cpp. That doesn't seem like a high frequency scenario that we need to worry about. Not sure there's much we could do even if it was. Reid.

On Wed, 11 Jan 2006, Vladimir A. Merzliakov wrote: > I can't build LLVM CFE after this patchs > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html This is most likely because you have conflict markers in the generated files in the lib/AsmParser directory. Try removing

I can't build LLVM CFE after this patchs http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030639.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060109/030654.html Build terminated with messages: --8X---------------------------------------------- llvm[2]: Compiling Lexer.cpp for Debug build In file included from

Sloppy me. I fixed the path for llvm-gcc but not for llvm-g++. My last patch to Makefile.rules fixes that so it should start working again. Reid. On Fri, 2004-12-24 at 05:21, Vladimir Merzliakov wrote: > >I successfully build CFE frontend at FreeBSD 5.3. > > > > Next nighttest run show more detail information :) > > After last 2 nighttest runs i see stable failure

Next problem detected by nighttest: LLVM build fail with errors: gmake[4]: Entering directory `/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime' llvm[4]: Compiling stacker_rt.c for Debug build (bytecode) default/bin/llvm-gcc: not found gmake[4]: *** [/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime/Debug/stacker_rt.bc] Error 1

I attempt install and use qmtest for run LLVM testsuit at FreeBSD, but without success. I have installed qm-2.2 (latest and single version accessable from http://www.codesourcery.com/qmtest/download.html in sources) When I start qmtest for LLVM ("make qmtest" in <llvm-obj-dir>/test directory - right?) error printed: ---8X---------------

> Current CVS LLVM build without problems but gmake install failed with > message: > > `/usr/home/wanderer/pkg/build/llvm/obj/lib/System' > llvm[1]: Compiling MappedFile.cpp for Debug build > /home/wanderer/pkg/build/llvm/src/llvm/lib/System/MappedFile.cpp:27:35: > platform/MappedFile.cpp: No such file or directory Also note: i find text in LLVM build log:

>> All SingleSource and MultiSource tests failed in last run of FreeBSD >> nighttester (and in previous). >> Mostly with error: > > This looks like your crtend.a file did not get built correctly. Try doing > make clean/make install in llvm/runtime/ again. > gmake clean in llvm/runtime/ remove all build tree of nighttest starting with llvm/runtime/../.. And then i