search for: init_cmd

Hi Jack, On Jan 25, 2009, at 10:00 AM, Jack Howarth wrote: > Doing that changes the error messages into a bus > error on the darwin linker. Pl. file bugzilla report (or radar) with a reproducible test case so that we can investigate this linker crash. As you know, one way to control symbol visibility is to use gcc's (inherited by llvm-gcc) visibility support. GCC supports, 1)

...l of pymol with -fvisibility=hidden using gcc 4.4 or llvm-gcc-4.2 with only a single header change... --- pymol-1.1/layer4/Cmd.h.orig 2009-01-30 18:58:58.000000000 -0500 +++ pymol-1.1/layer4/Cmd.h 2009-01-30 19:00:17.000000000 -0500 @@ -18,7 +18,8 @@ #include"os_python.h" -void init_cmd(void); +void init_cmd(void) +__attribute__((visibility("default"))); extern PyObject *PM_Globals; One of the advantages of running as a python module I guess. I was also able to build pymol with -O4 using the llvm 2.5 libLTO.dylib so that full Link Time Optimizations were performed....

On Sun, Jan 25, 2009 at 11:38:48AM +0100, Jean-Daniel Dupas wrote: > > Le 25 janv. 09 à 06:01, Jack Howarth a écrit : > > > After trying the recommended use of -O4 -fvisibility=hidden to > > compile xplor-nih with full LTO optimizations, I discovered three > > symbols become undefined... > > > > llvm-gcc-4 -O4 -fvisibility=hidden -o xplor xplor.o \ >