Open Office wants the files to be in /usr/local, but you can make /usr/local/include/dlfcn.h a symbolic link to /usr/include/dlfcn.h, and /usr/local/lib/libdl.dylib a symbolic link to /usr/lib/libdl.dylib.
--
Alexander K. Hansen
Levitated Dipole Experiment
http://www.psfc.mit.edu/LDX


On Jan 20, 2004, at 6:13 PM, Lincoln Peters wrote:

I do have OpenOffice, and I do have the Dl_info files you described. Does this mean that I can trash /usr/local/include/dlfcn.h and /usr/local/lib/libdl.dylib without causing problems in OpenOffice?

On Jan 19, 2004, at 5:31 AM, Peter O'Gorman wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthias Ringwald wrote:

| .... or...
|
|
| like the last time...
| the developer tools are not up to date. (2001...)
| update them.

No, all of these problems with Dl_info are from people who have installed
openoffice. Openoffice's installer ships, or at least used to ship,
/usr/local/include/dlfcn.h and /usr/local/lib/libdl.dylib. Problem being
that the version of dlcompat that they are shipping is old/different, and
does not include support for dladdr, thus when something wants to use
dladdr, it finds the function available in libSystem in it's configure
script, then when the actual code #includes <dlfcn.h> it gets
/usr/local/include/dlfcn.h, rather than /usr/include/dlfcn.h where dladdr
and Dl_info are defined.


It is the fault of openoffice for shipping a header that they do not even
need to ship. Application installers really should not install headers.






------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to