Issue 24558 - Old dlcompat header install breaks Fink compatability (which affects quite a few thousand user)
Summary: Old dlcompat header install breaks Fink compatability (which affects quite a ...
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.3
Hardware: Mac Mac OS X, all
: P4 Trivial with 2 votes (vote)
Target Milestone: OOo 1.1.2
Assignee: finkproject
QA Contact: issues@installation
URL: http://article.gmane.org/gmane.os.app...
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-01-19 13:48 UTC by finkproject
Modified: 2006-04-04 20:50 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description finkproject 2004-01-19 13:48:37 UTC
My name is David Höhn. I am the project public relations manager. A serious
issue with Fink and OpenOffice interoperatability exists. Fink serves around 36
000 Mac users in installing and checking over Unix packages. The problem below
has been described by the autor of dlcompat, now used by Apple in 10.3

Peter O Groman wrote:

"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. "

I would be very interested in resolving this issues as it affects more and more
of our users and they complain to us, not you guys :)

Thank you.
Comment 1 Olaf Felka 2004-01-19 14:44:23 UTC
of @ mh: Is this something for you?
Comment 2 Martin Hollmichel 2004-01-19 15:38:27 UTC
reassigned.
Comment 3 terryt 2004-01-20 09:33:25 UTC
Added oooqa keyword.

Thanks for bringing the issue to our attention.

The OOo v1.0.3GM Installer uses a pre-configured dlcompat Installer package, 
that has a software license that probably requires the package to be 
distributed in its entirety.

I checked the standalone "dlcompat-1050X.pkg" (by Christoph Pfisterer - APSL 
license), and it does NOT install any header files, just the static and dynamic 
libs. This package was probably the version of dlcompat installed for OOo 
1.0.1.

I checked the standalone "DLCompat-20020913-10.2.pkg" (by Chris Roberts - MIT 
license, comments by Peter O'Gorman), and it DOES install header files, as well 
as the static and dynamic libs. This package was probably the version of 
dlcompat installed for OOo 1.0.3.

This is something we can probably fix for the OOo 1.1.x Installer.
Comment 4 finkproject 2004-01-20 09:52:02 UTC
Thank you for looking into this terry. However this poses a huge issues to us, 
since many people do use OpenOffice and Fink together on their Mac OS X 10.3 
installs. Naturally they tend to complain to us, thus it would be nice if you 
coukld put a big fat warning about this up for the mac os X 10.3* people on 
your web-site.

The point is, that with 10.3* Apple took over dlcompat from Peter and 
integrated it directly into the base system. I am not sure if the headers are 
installed as well by Apple, but I guess so. The next questionw ould be, why are 
you installing the headers anyways? Why are they installed in the system's 
default search path? This is always bound to cause trouble :)
I would suggest you install such additional things either in the app bundle or 
in /opt

THank you once more for the swift answer. I appreciate your cooperation.
Comment 5 khendricks 2004-03-24 14:49:51 UTC
Hi,

I think this problem has already been fixed in OOo 1.1.1 which is about to be released.  There are now 
patches intended for OOo 1.1.2 that will incorporate dlcompat into the OOo CVS build tree and deliver 
just the library, NOT the headers during isntallation for MacOSX 10.2 (Jaguar) users only.  It will not be 
included at all for 10.3 (Panther) users since the libdl functions have been incorporated into libSystem 
under 10.3.

So when the OOo 1.1.1 for MacOSX goes live (hopefully within a week or so), people will start to 
upgrade to it and we will no longer be installing any dlcompat headers.

That still leaves the installed base with old headers in /usr/local/include but I am not sure what we can 
do about that now.   Perhaps a README that explains how to remove them might help.

My 2 cents,

Kevin
   
Comment 6 Martin Hollmichel 2004-04-28 06:58:28 UTC
please comment on kevin statements ?!
Comment 7 Martin Hollmichel 2004-04-28 07:03:00 UTC
feel free to reopen if there are any issue left to resolve.
Comment 8 Martin Hollmichel 2006-04-04 20:50:53 UTC
close issue.