Displaying 4 results from an estimated 4 matches for "idontwork".
2003 Dec 09
3
[LLVMdev] Linking Errors?
...earth would I get a runtime error of:
Type.cpp:132: const llvm::Type* llvm::Type::getForwardedTypeInternal()
const: Assertion `ForwardType && "This type is not being forwarded to
another type!"' failed.
Aborted
For the line of code:
MyModule = new Module( std::string("IDontWork"));
> -----Original Message-----
> From: llvmdev-admin at cs.uiuc.edu [mailto:llvmdev-admin at cs.uiuc.edu] On
> Behalf Of Reid Spencer
> Sent: Tuesday, December 09, 2003 8:36 PM
> To: Kevin Gibbs
> Cc: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] Linking Errors?
>...
2003 Dec 09
0
[LLVMdev] Linking Errors?
...> Type.cpp:132: const llvm::Type* llvm::Type::getForwardedTypeInternal()
> const: Assertion `ForwardType && "This type is not being forwarded to
> another type!"' failed.
> Aborted
>
> For the line of code:
>
> MyModule = new Module( std::string("IDontWork"));
I was getting these recently when we made the switch from -fshort-enums
to -fno-short-enums in the toplevel Makefile. The solution is to
blow *everything* away with a "gmake clean" and rebuild -- basically,
-fshort-enums and -fno-short-enums code do not mix.
--
gaeke at uiuc....
2003 Dec 09
0
[LLVMdev] Linking Errors?
You'll need to include the "support" library to resolve these
LeakDetector symbols. You can do this by either placing the path to
"support.o" or -lsupport on your link line (in your Makefile). Note
that if you use the -l option, you'll likely need to use -L<path> as
well to tell the linker where to find "libsupport.a" (file included by
the
2003 Dec 09
2
[LLVMdev] Linking Errors?
Can anyone help with these crazy linking errors??
/home/kgibbs/CS321/CVS/llvm/lib/Debug/vmcore.o(.gnu.linkonce.t._ZN4llvm12Lea
kDetector16addGarbageObjectEPKNS_5ValueE+0xd): In function
`llvm::LeakDetector::addGarbageObject(llvm::Value const*)':
/usr/include/c++/3.2.1/bits/stl_pair.h:148: undefined reference to
`llvm::LeakDetector::addGarbageObjectImpl(llvm::Value const*)'