Why do we have the -rpath option on by default?
It creates a serious problem for us. Say we build
a Winelib application for customer X. By default,
that app is built with -rpath=/usr/lib/wine.
However, that app relies on specific library versions
of Wine. Even if I start my app with
LD_LIBRARY_PATH=/opt/x/wine/lib, the X application
will actually use the /usr/lib/wine shared objects.
I would like to submit a patch to disable rpath
by default, and add a '--enable-rpath[=DIR]' configure
options. Objections?
Jer
