Re: [Pljava-dev] Mac OS X expertise needed

I wrote:

> https://github.com/tada/pljava/issues/63
>
> ... I am sure it must be something
> simple about the options being passed to the OS X build toolchain -
> the linker is complaining about what looks like every single symbol
> being unresolved *including those defined in the PL/Java code
> itself*!

I was mistaken about that last part, not reading the verbose linker
messages correctly. The only undefined symbols it was complaining about
were, well, everything defined in PostgreSQL.

When I build on linux, the linker just happily creates a .so file with
all those symbols listed as undefined, and they get hooked up to the
real things in PostgreSQL at the time the backend loads the library.

So what would be making the OS X linker think it has to resolve them all
at link time? Is there an extra option it needs telling it "relax, leave
things undefined, you're building a dylib"? It is already being passed
the -dynamiclib option. Do all the extern symbols need some special extra
annotation in OS X?

-Chap
_______________________________________________
Pljava-dev mailing list
Pljava-dev(at)lists(dot)pgfoundry(dot)org
http://lists.pgfoundry.org/mailman/listinfo/pljava-dev