Displaying 8 results from an estimated 8 matches for "onsist".
Did you mean:
insist
2005 May 30
1
[LLVMdev] [Cygwin] onsistant error building LLVM
I have done another test and it seems to be my cygwin development
environment :(
I cannot seem to reproduce my previous Cygwin environment on which we got
LLVM and the frontend tested.
Oh well I'll try again. It just seem such a long development cycle to test.
When I am ment to be testing my instillation instructions !
Try, try again...
Aaron
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.
2005 May 30
0
[LLVMdev] [Cygwin] onsistant error building LLVM
Perhaps Aaron has some local edits, possibly with a cut and paste error?
On Mon, 2005-05-30 at 10:50 -0700, Jeff Cohen wrote:
> 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
2005 May 30
1
[LLVMdev] [Cygwin] onsistant error building LLVM
Here's the instructions as I have them so far :-
http://angray.members.beeb.net/llvm/MakingLLVM.html
I was wondering whether you could look them over to see if I am doing
something obviously wrong.
Thanks,
Aaron
2005 May 30
0
[LLVMdev] [Cygwin] onsistant error building LLVM
Sure, but not right now. I need to go out for a bit. I'll look at them
tonight.
Reid.
On Mon, 2005-05-30 at 20:41 +0100, Aaron Gray wrote:
> Here's the instructions as I have them so far :-
>
> http://angray.members.beeb.net/llvm/MakingLLVM.html
>
> I was wondering whether you could look them over to see if I am doing
> something obviously wrong.
>
>
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 `/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...
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_T...
2004 Dec 27
3
how to debug frame slips?
Hi, I'm running into issues receiving faxes which, from what I have read,
may be caused by frame slips. While I can find many posts saying to
investigate it, I can't find any that describe *how* to debug the problem.
Tried searching this list as well to no avail.
Any pointers would be greatly appreciated.
FYI, I'm running wbel, AMP 1.04, spandsp 2pre4. Faxing to a pstn on a