similar to: [LLVMdev] newbie llc build problem: BreakCriticalEdges.cpp:44: undefined reference to `llvm::LoopSimplifyID'

On Tue, 25 Oct 2005, Kurt Harriman wrote: > Looking into LLVM for a database query engine project... > > After downloading the latest source from CVS, it's my first time trying > to build LLVM. Following the "Getting Started" instructions, all went well > until gmake reported this error while trying to link llc: > AFAICT, 'LoopSimplifyID' does in fact

Hi LLVM'ers, I can't figure out why I get this error: -------------------------------------------------- c:/MinGW/bin/../libexec/gcc/mingw32/3.4.2/collect2.exe -Bdynamic -o c:/projects/build/MinGW/llvm-1-1/Debug/bin/llc.exe /mingw/lib/crt2.o c:/MinGW/bin/../lib/gcc/mingw32/3.4.2/crtbegin.o -Lc:/projects/build/MinGW/llvm-1-1/Debug/lib -Lc:/projects/build/MinGW/llvm-1-1/Debug/bin

Reid, Getting the same error again :-( /usr/gcc/gcc-3.4.3/libexec/gcc/i686-pc-cygwin/3.4.3/collect2.exe -Bdynamic --dl l-search-prefix=cyg -o /usr/build/llvm-2/Debug/bin/llc.exe /lib/crt0.o -L/usr/bu ild/llvm-2/Debug/lib -L/usr/build/llvm-2/Debug/bin -L/usr/gcc/gcc-3.4.3/lib/gcc/ i686-pc-cygwin/3.4.3 -L/usr/gcc/gcc-3.4.3/lib/gcc/i686-pc-cygwin/3.4.3/../../..

'collect2.exe' is an internal version of 'ld' called by GCC The GCC command line is :- g++ -I/usr/build/llvm-2/tools/llc -I/usr/src/llvm/tools/llc -I/usr/build/llvm-2/ include -I/usr/src/llvm/include -I/usr/build/llvm-2/include -I/usr/src/llvm/incl ude -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -Wall -W -Wwrite-strings -Wno-unused -g -D_DEBUG -v -o /usr/build/llvm-2/Debug/bin/llc.exe

I did not report this first error earlier as I thought it trivial. Basically it looks like something odd is happening with the configuration and 'include/llvm/config/config.h' Getting this error on building the tools on a fresh Cygwin install and update :- $ make tools-only make[1]: Entering directory `/usr/build/llvm/lib/System' llvm[1]: Compiling Path.cpp for Debug build In file

Hi, Andreas Neustifter wrote: > I'm writing a ModulePass that needs critical edges split up. I have the > statement > > AU.addRequiredID(BreakCriticalEdgesID); > > in my getAnalysisUsage() but the pass never gets executed. > > I guess I have to request pass execution for each function, but I can't > get behind how to do that, since there is no analysis group

On Fri, 11 Mar 2005, Marc Ordinas i Llopis wrote: > Sorry if this is obvious. > I'm trying to link LLVM-generated code with LLVM itself, and don't know how > to do it. Just as a little test, I've tried compiling the example > HowToUseJIT.cpp using llvm-g++, but I get tons of errors. > > Is there an easy way of doing this? Has anyone tried it before? What sort of

Hi all, Sorry if this is obvious. I'm trying to link LLVM-generated code with LLVM itself, and don't know how to do it. Just as a little test, I've tried compiling the example HowToUseJIT.cpp using llvm-g++, but I get tons of errors. Is there an easy way of doing this? Has anyone tried it before? Thanks, Marc Ordinas i Llopis | Tragnarion Studios

Hi, sorry for the delay, I've been swamped lately :-/ On Fri, 10 Mar 2006, Eric Kidd wrote: > Thanks for your advice! I did get everything working (eventually) by pasting > the following code into the Makefile for HowToUseJIT: > > .PHONY: dump-config > dump-config: > @echo Compile: $(Compile.CXX) > @echo Link: $(Link) > @echo Libs:

Okay, its not that simple. Several files in Transforms/Utils depend on things in lib/Analysis. A quick grep shows: BreakCriticalEdges.cpp:#include "llvm/Analysis/Dominators.h" BreakCriticalEdges.cpp:#include "llvm/Analysis/LoopInfo.h" CloneTrace.cpp:#include "llvm/Analysis/Trace.h" CodeExtractor.cpp:#include "llvm/Analysis/Dominators.h"

[R-devel'ers: spill over from R-core .. -- MM] >>>>> "KH" == Kurt Hornik <Kurt.Hornik@ci.tuwien.ac.at> writes: >>>>> Robert Gentleman writes: >> In preparing the next Windows release I want to make opening up >> system data files (and their documentation) more transparent. I >> would really like to adopt the

Hello Karl, Thursday, March 13, 2003, 1:44:40 AM, you wrote: KH> On Thu, 2003-03-13 at 00:26, Nicolas Bazin wrote: >> | >> configure:9221: result: no >> configure:9249: gcc -o conftest -O20 -fsigned-char -D_REENTRANT -I/home/Darkmeteor/include -I/home/Darkmeteor/include -I/home/Darkmeteor/include conftest.c -L/home/Darkmeteor/lib -lshout >> -lpthread

I have a couple of questions about the various Icecast builds that exist: 1) It seems like new builds being done today are all "kh" builds. Is that observation correct? If I see something non-kh, is it older by definition? 2) Other than possibly age, what is the conceptual different (if any) between kh and non-kh builds? What do kh builds hope to accomplish that old Icecast never did?

Hi, I'm writing a ModulePass that needs critical edges split up. I have the statement AU.addRequiredID(BreakCriticalEdgesID); in my getAnalysisUsage() but the pass never gets executed. I guess I have to request pass execution for each function, but I can't get behind how to do that, since there is no analysis group for that kind of transformation. Thanks, Andi

In trying to package up LLVM for Debian, it appears that x86_64 is no longer a supported architecture -- so, my first question is, is that correct? Best I can tell, the only thing that's supposed to work for x86_64 is the C backend. For Debian, I need to build everything from scratch. When trying to build llvm-gcc4 from source, though, I get part way through the build and am told that

[I do think this discussion belongs to R-devel rather than anywhere else .. MM] >>>>> "Kurt" == Kurt Hornik <Kurt.Hornik@ci.tuwien.ac.at> writes: >>>>> Peter Dalgaard BSA writes: >> Kurt Hornik <Kurt.Hornik@ci.tuwien.ac.at> writes: KH>>> While trying to write documentation for data.class(), I came

Excuse the long post, Chris Lattner wrote: > On Fri, 11 Mar 2005, Marc Ordinas i Llopis wrote: > >> Sorry if this is obvious. >> I'm trying to link LLVM-generated code with LLVM itself, and don't >> know how to do it. Just as a little test, I've tried compiling the >> example HowToUseJIT.cpp using llvm-g++, but I get tons of errors. >> >>

Consider this a Ticket for Icecast 2.4 ******************************************************************************** If you look at {{{ admin/stats.xml }}} on a Icecast-KH server (default setup) and an Icecast 2.4 server (default setup) the following is one of the things that the KH branch has as extra info. {{{ <listener id="3581"> <ID>3581</ID>

On Mar 10, 2006, at 2:57 PM, Martin Pärtel wrote: > I'm currently using the "make install"-ed version of LLVM in an > autoconf/automake project. Setting it up wasn't that bad really. > The .a > libraries can be statically linked with the -l flag and .o > libraries are > simply linked in as normal object files (without -l). All the > libraries got >

Hi, On 2 Sep 2024, at 12:19, Marek Dziembowski wrote: > Greetings icecasting amigos! > > > I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement. > > The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest