similar to: [LLVMdev] Problem with Hello World Pass

Dear Nick and LLVM-DEV, This morning I commited changes to both the prerelease-10 branch and mainline. These changes fix the bug found on Solaris where constructors of static global variables are not executed when a dynamic library is dlopened(). The fix updates libtool to 1.5 and modifies it so that it always selects the -G option when linking on Solaris with GCC. Makefile.common has

Hi John, Please see below, too >From: John Criswell <criswell at cs.uiuc.edu> >Date: Tue, 27 Jul 2004 14:57:02 -0500 > >Henrik Bach wrote: >>Hi, > >Please see below. > >> >>I get this error: >>------------------ >>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) >>ToolRunner.cpp:396: error: (Each

Solved. Short version: You don't need to change DynamicLinker.cpp at all. dlopen() should just work, except that the defaults for libtool are to produce the wrong kind of shared object. On OS X, libtool needs to be passed the -module option to create dlopen-able objects: % diff Makefile.rules.old Makefile.rules 326c326 < Link := $(LIBTOOL) --mode=link $(CXX) --- > Link

On Sat, 19 Jun 2004, Michael McCracken wrote: > I used the following short code to test loading the .dylib, and dlopen > works fine, but dlsym is less pretty - on OS X, it automatically > prepends an underscore to the symbol, which means that if you are > looking for main(), you ask for "main" and it looks for "_main", which > is how the symbols are named in

OK, seems like I've got some more looking to do. From what I can find, the only difference with OS X and dynamic libraries is that you can't depend on the order of calling static constructors, but not that you can't depend on them getting called. :) If I find that library handling in LLVM needs changes to work with OS X, I'll send a patch. Thanks, -mike On Jun 19, 2004,

Forgot to reply to the list. -- John T. -------- Original Message -------- Subject: Re: [LLVMdev] MAJOR API CHANGE: Pass initialization without static constructors Date: Fri, 8 Oct 2010 15:05:21 -0500 From: John Criswell <criswell at illinois.edu> To: Owen Anderson <resistor at mac.com> On 10/8/10 1:29 PM, Owen Anderson wrote: > Hello fellow LLVM-ers, > > As

On Oct 8, 2010, at 1:37 PM, John Criswell wrote: > On 10/8/10 3:15 PM, Owen Anderson wrote: >> >> On Oct 8, 2010, at 1:05 PM, John Criswell wrote: >> >>> On 10/8/10 1:29 PM, Owen Anderson wrote: >>>> Hello fellow LLVM-ers, >>>> >>>> As those of you who follow llvm-commits have probably noticed, I've been hard at work

On 2011-08-09 16:48, John Criswell wrote: > On 8/9/11 6:49 AM, Bjorn Reese wrote: >> I have an optimization pass (FunctionPass) where I need to add global >> constructors. >> >> For cleaness sake I decided to add these in my own module. My module >> is created in my FunctionPass constructor: > > This is not how I would do it. A FunctionPass has

Greetings on A.N. Kolmogorov's 100th birthday: I am sure that this is a resolved problem, certainly it has been raised in R help several times before, but I can't seem to find the right clue. I've recently upgraded a G4 to OS 10.2.5 and I thought I would have another go at installing R from source, after failing to accomplish this in 10.1. So with 1.7.0 from CRAN configure seems to

Hi John, Thank you for your advice. LIBS and LDFLAGS work for the configure script, but they gave errors in the make stage for apache and mysql. I used either of the following ones with other flags: - export LIBS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" - export LDFLAGS="-L/home/sangmin/Dropbox/Falcon/bin/ -ldummy" Here are the error messages: Compile error (apache):

On 8/9/11 9:15 AM, Bjorn Reese wrote: > On 2011-08-09 16:48, John Criswell wrote: >> On 8/9/11 6:49 AM, Bjorn Reese wrote: >>> I have an optimization pass (FunctionPass) where I need to add global >>> constructors. >>> >>> For cleaness sake I decided to add these in my own module. My module >>> is created in my FunctionPass constructor:

On Thu, Mar 30, 2006 at 04:27:55PM +0530, Pratik Mehta wrote: > I have made few attempts to compile some software packages with llvm. > My approach is to define Make variables as follows : > > export AS=llvm-as > export LD=llvm-ld > export AR=llvm-ar > export CXX=llvm-g++ > > and then run configure and make. > > This approach works with very small code bases

Dear yueqiang, I tracked this down this morning, and it is a bug with our Python code that runs the tests. Essentially what is happening is that the code is finding the temporary directory it created the first time it ran the tests and believes that there are tests inside of it which it needs to run. It then gets confused and quits. This bug only shows up when the source tree and the

Unfortunately it's not that easy, although I'd love to fix it if I can figure out how. OS X 10.3 does have dlfcn.h and dlopen() - for 10.3, they added the dlcompat library that uses the OS X NSLink* stuff to support dlopen and dlsym. configure seems to pick that up fine. It seems like the code that's there already should work fine, so I'm not sure where else to look. I'm

Hi, I get this error: ------------------ ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function) ToolRunner.cpp:396: error: (Each undeclared identifier is reported only once for each function it appears in.) ------------------ And the config.log shows that configure has detected that ld on my platform (Interix) doesn't support shared libraries: ------------------

Thanks for your valuable input. By the way, I am exporting CC=llvm-gcc and RANLIB=llvm-ranlib for projects that use it. It was a mistake not to write it in the post as apache indeed uses gcc. If you see the error message, you would see llvm-gcc being used. I would try to investigate further on the lines you have mentioned. However, the question that stands is how to best handle failure to compile

Sean Peisert wrote: > John, > > I may be missing something here, but if I the compilation docs, I need > to build LLVM first and the C frontend second. But doing this, I > get: > > **llvm-gcc/llvm-g++ was not found, > > (obviously -- it wasn't installed, right?) You do need to build LLVM first before building llvm-gcc. This may seem a bit weird, but

I have done that. I have defined createMyAnaPass() in Passes.h and it is defined in MyAna.cpp and used in LinkAllPasses.h But still the error : /home/ambika/llvm/llvm-obj/tools/opt/Release/opt.o: In function `global constructors keyed to opt.cpp': opt.cpp:(.text+0x1e89): undefined reference to `llvm::createMyAnaPass()' I dont understand whats the problem. Jianzhou Zhao wrote: >

HI Duncan, Your understanding of the problem is correct. However, the XYZ class is not inside an anonymous name space. Also, all the XYZ methods are defined in the .cpp file. Looking at the error message: opt: symbol lookup error: path/to/pass.so: undefined symbol: _ZN12DataTransferD1Ev Where DataTransfer is the class name. Maybe I am missing certain type of constructors? Thanks, Welson On

Package: src:blktap Version: 2.0.90-1 Severity: important Tags: sid jessie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.8 The package fails to build in a test rebuild on at least amd64 with gcc-4.8/g++-4.8, but succeeds to build with gcc-4.7/g++-4.7. The severity of this report may be raised before the jessie release. tapdisk-logfile.c:166:23: error: argument to 'sizeof'