similar to: [LLVMdev] [Cygwin] 'make tools-only' configuration error

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] [Cygwin] 'make tools-only' configuration error"

2005 Jun 01
1
[LLVMdev] [Cygwin] 'make tools-only' configuration error
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/../../..
2005 Jun 01
0
[LLVMdev] [Cygwin] 'make tools-only' configuration error
'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
2005 May 30
4
[LLVMdev] [Cygwin] onsistant error building LLVM
Consistant error building LLVM on Cygwin from CVS :- make[2]: Entering directory `/usr/build/llvm/tools/llc' llvm[2]: Compiling llc.cpp for Debug build llvm[2]: Linking Debug executable llc /usr/build/llvm/Debug/lib/LLVMX86.o(.text+0x30506): In function `_GLOBAL__D__ZN7 6_GLOBAL__N__usr_src_llvm_lib_Target_X86_X86ISelPattern.cpp_9D2164D3_DD38501517X
2005 May 30
0
[LLVMdev] [Cygwin] onsistant error building LLVM
If you look in X86JITInfo.cpp, you'll find CompilationCallback. I'm not sure about CompilationCallback2. In any event, the code is conditionally compiled and that might be tripping things up on Cygwin. Reid. On Mon, 2005-05-30 at 17:17 +0100, Aaron Gray wrote: > Consistant error building LLVM on Cygwin from CVS :- > > make[2]: Entering directory
2005 Aug 30
1
[LLVMdev] X86ISelPattern.cpp:73: undefined reference to `X86CompilationCallback
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
2005 Oct 25
2
[LLVMdev] newbie llc build problem: BreakCriticalEdges.cpp:44: undefined reference to `llvm::LoopSimplifyID'
Hi, 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: In function `(anonymous namespace)::BreakCriticalEdges::getAnalysisUsage(llvm::AnalysisUsage&) const':
2005 May 30
4
[LLVMdev] [Cygwin] onsistant error building LLVM
Also, this error: /usr/src/llvm/lib/Target/X86/X86ISelPattern.cpp:73: undefined reference to `X86CompilationCallback2' doesn't make sense. X86CompilationCallback2 is not visible outside of X86JITInfo.cpp, and line 73 of X86ISelPattern.cpp is in the middle of a comment block.
2006 Sep 08
2
[LLVMdev] build broken on linux/amd64
Compiling llvm on a linux/amd64 box produces: home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `_X86CompilationCallback': (.text+0x316fe): undefined reference to `_X86CompilationCallback2' /home/rafael/dev/llvm/build/Debug/lib/LLVMX86.o: In function `llvm::X86JITInfo::getLazyResolverFunction(void* (*)(void*))': /home/rafael/dev/llvm/cvs/lib/Target/X86/X86JITInfo.cpp:219:
2006 Aug 01
15
[LLVMdev] Building llvm under cygwin
> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at
2006 Aug 03
0
[LLVMdev] Building llvm under cygwin
Hello Anton Thu, 3 Aug 2006 12:38:54 +0400 you wrote: > I've updated it yesterday and rebuilt - llvm built fine. But when > building llvm-gcc4 (also updated yesterday from new /trunk > directory) it fails with the same error. You might easily get llvm-gcc4-mingw32 binaries from "prerelease" directory. Since stdcall, fastcall & dllimport stuff is unsupported right now,
2008 Feb 21
2
[LLVMdev] llvm 2.2 install and ocaml bindings
I've run into a problem with the ocaml bindings and the jit. It builds fine without the jit, but when I try to include it it tries to use the c object files from the build location, instead of the install location: > llvm-config --libdir --libfiles engine /opt/local/lib /opt/local/lib/LLVMX86.o /opt/local/lib/libLLVMSelectionDAG.a /opt/local/lib/libLLVMCodeGen.a
2006 Aug 03
0
[LLVMdev] Building llvm under cygwin
Hello Anton Thu, 3 Aug 2006 15:06:56 +0400 you wrote: > here it is in the attachment :) Ok. Could you also send LibDeps.txt file? It should be in /obj/tools/llvm-config directory -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
2004 Sep 01
0
[LLVMdev] POSIX compliance
/lib/System/platform/Path.cpp is not compilable under Cygwin (although it was motivated to be for Cygwin...): ----------------------------------- Compiling Path.cpp In file included from Path.cpp:37: platform/Path.cpp: In static member function `static llvm::sys::Path llvm::sys::Path::GetTemporaryDirectory()': platform/Path.cpp:41: error: `mkdtemp' undeclared (first use this function)
2005 Oct 15
1
Hiccup in installing R 2.2.0
Yesterday I downloaded R-2.2.0.tar.gz, gunzipped and untarred, and did the usual ./configure and make. Everything seemed to go smoothly until it got to the bit about installing recommended packages. It got past ``spatial'' but turned up a fatal error in respect of the ``boot'' package. Here is some of what appeared on the screen:
2005 Oct 21
1
[LLVMdev] Release Branch for llvm-gcc
On Fri, Oct 21, 2005 at 12:10:12AM +0100, Aaron Gray wrote: > I thought I should warn you the Cygwin Release (ENABLE_OPTIMIZED=1) build > fails due to 'ld/collect2' assertion failure. > > This is really a Cygwin problem that I thought would be fixed with time by > now but is still present with GCC 3.4.4 and binutils 2.16.91. Is there a version of Cygwin that _does_ build
2008 Aug 13
2
[LLVMdev] LLVM build problem
Checking out LLVM from svn and building, I get: llvm[2]: Linking Release executable ModuleMaker (without symbols) /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMX86.o(.eh_frame); no .eh_fr ame_hdr table will be created. /usr/bin/ld: error in /home/aph/llvm/Release/lib/LLVMInterpreter.o(.eh_frame); n o .eh_frame_hdr table will be created. /usr/bin/ld: error in
2007 Sep 18
1
[LLVMdev] 2.1 Pre-Release Available (testers needed)
> LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. I am trying with llvm-gcc-4.2 from svn. Aaron
2005 Jun 01
0
[LLVMdev] [Cygwin] 'make tools-only' configuration error
On Tue, 2005-05-31 at 23:56 +0100, Aaron Gray wrote: > Reid, > > I did look on eBay for you for replacement 2.5" harddisks but they > were expensive and in short supply :( LOL. > > >That all sounds right to me. Must be the "new" version of Cygwin. Go > >to /usr/include and do this: > > > >find . -name '*.h' -exec grep mkdtemp {} \;
2004 Dec 28
2
[LLVMdev] Re: Starting with LLVM-GCC on Cygwin
Henrik Bach wrote: > > You should download and install in the first shot: > > a.. LLVM source code (3.5M) > f.. GCC Front End Source Code (30.0M) > > Then follow the items listed in > http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html for Cygwin. > [snip] <QUOTE from http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html#cygwin> It has been found that the GCC
2005 Jan 10
1
[LLVMdev] Cygwin build is still broken
Hi Reid, >> I've just updated to the latest CVS version and cygwin port >> is still broken. When building full llvm: > > Any ideas? Has anybody been able to replicate this issue? > > GNU assembler 2.15.91 20040725 > > gcc (GCC) 3.4.1 (cygming special) > > Cygwin builds just fine for me. It looks like you're using > the wrong tools. Please read: