On Wed, 9 Jul 2003, Misha Brukman wrote:> > Also, I don't have a Debug subdirectory like the tutorial said I would - I > > have Release instead. > > 1. What version of LLVM are you using (i.e., when did you get a tarball, > or if you are using anonymous CVS, are you up to date)?I use CVS and I updated a couple days ago.> 3. If you are using a version of LLVM that is new enough to have a > 'configure' script in the top-level directory, how did you run > 'configure'? You may have specified './configure --enable-optimized' > or the like, with the save effects as in #2.Yes, that's it. I should probably disable optimized builds for now anyway.> I'm assuming that the file `hello.so' does in fact exist.Not that I saw. 'libhello.so' does exist though. It's a link to 'libhello.so.0.0.0' in the same directory. Also, 'libhello.so.0' in the same directory is a link to 'libhello.so.0.0.0'. There is also 'libhello.a', 'libhello.la', and 'hello.o'.> Did you register your optimization pass with OPT by using something > along the lines of > > RegisterOpt<Hello> X("hello", "Hello World Pass"); > > as is mentioned in the `Basic code required' section?I used lib/Transforms/Hello/Hello.cpp provided in the CVS tree. It has exactly the line of code you require. I also used the Makefile there. If you think of anything else, please let me know... - Nick
Dear Nicholas, I've compiled both optimized and debug builds on Linux, and both seem to work as described in the documentation. Are you compiling on Sparc or x86? I'd like to know in order to try to reproduce your error. Also, can you send us a copy of the bytecode file that you are using as input to opt? One thing that I found odd is that opt cannot use a library name unless it is an absolute or relative path. For example, opt -load ./libhello.so works, but opt -load libhello.so does not (although it seems to give an error message instead of failing quietly). If you could send us the above information, that'd be great. Thanks. -- John T. -- ********************************************************************* * John T. Criswell Email: criswell at uiuc.edu * *********************************************************************
On Wed, 9 Jul 2003, John Criswell wrote:> Dear Nicholas,You can call me Nick. :)> Are you compiling on Sparc or x86? I'd like to know in order to try to > reproduce your error.Sparc. (Solaris 5.8).> Also, can you send us a copy of the bytecode file that you are using as > input to opt?Sure - I don't think it's of any use though - I don't even get a description of the "Hello" transformation in the text generated by opt -load ... -help> One thing that I found odd is that opt cannot use a library name unless > it is an absolute or relative path. For example, > > opt -load ./libhello.so > > works, but > > opt -load libhello.so > > does not (although it seems to give an error message instead of failing > quietly).I've tried both absolute and relative paths, and they fail quietly. When I mistyped the path, opt gave an error saying the load failed because the library file could not be found. Thanks, - Nick -------------- next part -------------- A non-text attachment was scrubbed... Name: dumb.bc Type: application/octet-stream Size: 1068 bytes Desc: URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20030709/3834ba13/attachment.obj>