similar to: [LLVMdev] All SingleSource and MultiSource tests failed at FreeBSD

On Wed, 10 Nov 2004, Vladimir Merzliakov wrote: > 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. -Chris > ---8X--------------------- > gcc -O3 Output/2002-05-02-CastTest3.llc-ls.s

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

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

> Only thing I can think of is that your "platform" link is missing. > make sure "platform is a symbolic link to your platform's subdirectory > in the llvm/lib/System directory. If you're on FreeBSD then: > > ln -s FreeBSD platform > > this should have been done for you when you configured. My fault. I make cvs update llvm and AFTER remove build

On Thu, 11 Nov 2004, Vladimir Merzliakov wrote: > > This looks like your crtend.a file did not get built correctly. Try doing > > make clean/make install in llvm/runtime/ again. > > lib\Debug\libcrtend.a builded. > > But i not found it in LLVM installation dir after install. 'make install' should install this into the CFRONTEND/bytecodeobjs directory. -Chris --

On Wed, 2004-11-10 at 11:06, Vladimir Merzliakov wrote: > > 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: > >

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

> Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? After providing :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm at CVSROOT this problem disappear. But have personal problem: I must have now 2 copy LLVM sources 1) to plain build llvm 2) to nighttester run Can I use llvm builded in nighttest/build directory to install plain llvm? Vladimir

Vladimir, Did the checkout fail? Its trying to do a chdir("llvm") in the build directory (second argument to the script) but that directory doesn't exist or isn't executable. Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? Reid. On Thu, 2004-06-24 at 10:42, Vladimir Merzliakov wrote: > > Are you using the NightlyTest.pl file? To run the

On Sat, Oct 05, 2019 at 03:01:43PM +0100, Pete Biggs wrote: > In the future new features and upgrades will appear in Stream as a sort > of rolling release and it will form the basis of future RHEL releases > (and subsequently CentOS releases). It will also be the place for > community input into RHEL/CentOS. Think of it as halfway between the > cutting edge Fedora and the stable

At the LLVM Developers' Meeting in November, I promised to work on isolating a subset of the current test suite that is useful for benchmarking. Having looked at this in more detail, most of the applications and benchmarks in the test suite are useful for benchmarking, and so I think that a better way of phrasing it is that we should construct a list of programs in the test suite that are not

> > Hrm, you probably have to tell it how to check out the LLVM tree. The > /home/vadve/shared/PublicCVS path is the internal path to the root of the > CVS repository. I'm not sure if the tester script has the ability to > check out the tree over anon cvs yet. Reid do you know? :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm work for me Waiting test results...

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > check out the tree over anon cvs yet. Reid do you know? > :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm work for me > > Waiting test results... Great! It might take a while. The tester takes about 6 hours to run on a 2proc 3.0ghz Xeon box :) But that's with spec95/2k and povray included. -Chris --

> Are you using the NightlyTest.pl file? To run the tester I don't use > gmake directly at all. Instead, I have this in my crontab: > > 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 > > When run like this,

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm > dir? > > After providing :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm at > CVSROOT > this problem disappear. > > But have personal problem: I must have now 2 copy LLVM sources > 1) to plain build llvm > 2) to nighttester run >

Hi all, Is anyone else seeing tests in the Multisource/Applications directory failing with something looking like this: /Users/wendling/llvm/llvm.obj/Debug/bin/gccld -L/Users/wendling/llvm/ llvm-gcc4.install/lib/gcc/powerpc-apple-darwin8.8.0/3.4-llvm -L/ Users/wendling/llvm/llvm-gcc4.install/lib Output/siod.linked.bc -lc -lpthread -lltdl -lm -o Output/siod.llvm gccld: warning: Cannot

On Sun, 29 Oct 2006, Bill Wendling wrote: > Is there a way to make bugpoint use gccld (or the equivalent with llc > flags)? In a multisource/external dir, use 'make bugpoint-gccld'. In singlesource, use 'make Output/progname.bugpoint-gccld'. -Chris -- http://nondot.org/sabre/ http://llvm.org/

On May 21, 2008, at 11:45 AM, Török Edwin wrote: > The forking was introduced because the runtime was too small; I think this direction is wrong. I'd rather have some infrastructure that can get nanoseconds or tick counters and print them... This then allows for a microbenchmark suite, which I think fits in nicely with the llvm philosophy.

After commit http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050228/024420.html I can't build LLVM at FreeBSD. Build terminate with message: llvm[3]: Compiling AlphaRegisterInfo.cpp for Debug build /home/wanderer/pkg/build/llvm/src/llvm/lib/Target/Alpha/AlphaRegisterInfo.cpp:34: error: integer constant is too large for "long" type

Evan Cheng wrote: > On May 21, 2008, at 6:09 AM, Matthijs Kooijman wrote: > > >> Hi, >> >> I've been toying around with the testsuite for a bit, and after >> recompiling >> llvm-gcc a bunch of times and fixing a nasty bashism bug, I actually >> got it to >> run and pass most tests. >> >> When running, I noticed a very long