Re: Alexandre Julliard : configure: Use --rpath if supported when building binaries to point to
We need a --disable-rpath option in configure for rpath disable. Rpaths is not useful when WINE building for distribution. Will I add --disable-rpath of there is a better suggestion?
В сообщении от 20 февраля 2006 14:40 Alexandre Julliard написал(a): ...
configure: Use --rpath if supported when building binaries to point to the relative location of the wine libraries.
Vitaly Lipatov lav@etersoft.ru writes:
We need a --disable-rpath option in configure for rpath disable. Rpaths is not useful when WINE building for distribution.
Why is it not useful?
В сообщении от 24 февраля 2006 20:53 Alexandre Julliard написал(a):
Vitaly Lipatov lav@etersoft.ru writes:
We need a --disable-rpath option in configure for rpath disable. Rpaths is not useful when WINE building for distribution.
Why is it not useful?
Sorry for my English. It is useful when we run wine from the source tree.
To be strictly, there is no needs in rpath using if libwine placed in standard place as /usr/lib
I got follow broken requires when build rpm package:
/usr/bin/../lib/libwine.so.1(WINE_1.0) /usr/bin/../lib/libwine_unicode.so.1(WINE_1.0)
and find any methods to disable new feature with rpath when I build package.
Vitaly Lipatov lav@etersoft.ru writes:
To be strictly, there is no needs in rpath using if libwine placed in standard place as /usr/lib
I got follow broken requires when build rpm package:
/usr/bin/../lib/libwine.so.1(WINE_1.0) /usr/bin/../lib/libwine_unicode.so.1(WINE_1.0)
and find any methods to disable new feature with rpath when I build package.
It sounds like rpm needs a good whack on the head if it is unable to cope with this. Anyway, you could always build with make LDEXERPATH="".
On Friday 24 February 2006 21:23, Alexandre Julliard wrote:
Vitaly Lipatov lav@etersoft.ru writes:
I got follow broken requires when build rpm package:
/usr/bin/../lib/libwine.so.1(WINE_1.0) /usr/bin/../lib/libwine_unicode.so.1(WINE_1.0)
and find any methods to disable new feature with rpath when I build package.
It sounds like rpm needs a good whack on the head if it is unable to cope with this. Anyway, you could always build with make LDEXERPATH="".
Thank you for the solution. Anyway --disable-rpath is more common way for it :)
To be strictly, there is no needs in rpath using if libwine placed in standard place as /usr/lib
I got follow broken requires when build rpm package:
/usr/bin/../lib/libwine.so.1(WINE_1.0) /usr/bin/../lib/libwine_unicode.so.1(WINE_1.0)
Is that an error during building of the rpm, or during installing it? Could you post the exact message and the .spec file used to build it? I reckon there's other software out there that does the same thing and somehow rpm handles it fine . . . Interesting.
Kuba
On Fri, 24 Feb 2006 21:11:39 +0300, Vitaly Lipatov wrote:
Sorry for my English. It is useful when we run wine from the source tree.
It's useful for people distributing Wine binaries as well. Not every feature is there for the distros you know ... also asking developers to disable rpath because RPM cannot cope with it is remarkably poor form IMO, just fix RPM!
В сообщении от 1 марта 2006 17:23 Mike Hearn написал(a):
On Fri, 24 Feb 2006 21:11:39 +0300, Vitaly Lipatov wrote:
Sorry for my English. It is useful when we run wine from the source tree.
It's useful for people distributing Wine binaries as well. Not every feature is there for the distros you know ... also asking developers to disable rpath because RPM cannot cope with it is remarkably poor form IMO, just fix RPM!
Dear Mike, I asked Alexandre to add _option_ to configure for disable rpath but to remove rpath using. It is poor way to make comments about distros and RPMs as your one.
On Wed, 2006-03-01 at 20:50 +0300, Vitaly Lipatov wrote:
Dear Mike, I asked Alexandre to add _option_ to configure for disable rpath but to remove rpath using.
I understand the request, but the question remains - why are you asking every single upstream author to add complexity to their build systems, when you could just fix RPM?
thanks -mike
В сообщении от 1 марта 2006 21:25 Mike Hearn написал(a):
On Wed, 2006-03-01 at 20:50 +0300, Vitaly Lipatov wrote:
Dear Mike, I asked Alexandre to add _option_ to configure for disable rpath but to remove rpath using.
I understand the request, but the question remains - why are you asking every single upstream author to add complexity to their build systems, when you could just fix RPM?
Did you mean fix rpm spec? You are about workaround explained by Alexandre? Build system in ALT Linux has strict requires to use rpath and last changes in wine conflicts with it. I guess I do not understand where is problem in RPM you told about.
Now I think there is bug somewhere. I see in ps strange paths after ran any program: /usr/lib/../bin/wine-preloader /usr/lib/../bin/wine-kthread notepad.exe /usr/lib/../bin/wineserver
On Wed, 2006-03-01 at 22:21 +0300, Vitaly Lipatov wrote:
Did you mean fix rpm spec?
No, fix RPM the program. If the RPM software can't cope with a simple use of RPATH then it is buggy and should be patched.
You are about workaround explained by Alexandre?
The workaround is fine for Wine, but it's the general principle I have a problem with. If you asked me to add a --disable-rpath switch to software I maintained I'd say no, because this is not a bug in my software but rather with RPM itself.
Now I think there is bug somewhere. I see in ps strange paths after ran any program: /usr/lib/../bin/wine-preloader /usr/lib/../bin/wine-kthread notepad.exe /usr/lib/../bin/wineserver
Looks OK to me. A bit ugly maybe ...
Vitaly Lipatov lav@etersoft.ru writes:
Now I think there is bug somewhere. I see in ps strange paths after ran any program: /usr/lib/../bin/wine-preloader /usr/lib/../bin/wine-kthread notepad.exe /usr/lib/../bin/wineserver
That's not a bug, it's a feature. Binaries are now located relative to the library path, so if you move your Wine install somewhere else it still works, without having to set environment variables.
-
Alexandre Julliard -
Kuba Ober -
Mike Hearn -
Vitaly Lipatov