On 10/15/2015 08:41 AM, Giulio Camuffo wrote:
The fact that it finds my xwayland.so file in ~/install, but cannot find the
Xwayland executable in ~/install bothers me a lot, however. It obviously
figured out where xwayland.so is from the --prefix arg to configure and this
really should match.
2015-10-15 18:36 GMT+03:00 Bill Spitzak :
> On 10/15/2015 12:24 AM, Pekka Paalanen wrote:
>>
>> On Wed, 14 Oct 2015 22:21:31 -0700
>> Bill Spitzak wrote:
>>
>>> It seems like /usr/bin/Xwayland is hard-coded into xwayland.so. This
>>> makes it not run local installed versions of Xwayland. I could n
On 10/15/2015 12:24 AM, Pekka Paalanen wrote:
On Wed, 14 Oct 2015 22:21:31 -0700
Bill Spitzak wrote:
It seems like /usr/bin/Xwayland is hard-coded into xwayland.so. This
makes it not run local installed versions of Xwayland. I could not get X
programs to work under wayland without doing "sudo
On Wed, 14 Oct 2015 22:21:31 -0700
Bill Spitzak wrote:
> It seems like /usr/bin/Xwayland is hard-coded into xwayland.so. This
> makes it not run local installed versions of Xwayland. I could not get X
> programs to work under wayland without doing "sudo ln -s
> ~/install/bin/Xwayland /usr/bin"
It seems like /usr/bin/Xwayland is hard-coded into xwayland.so. This
makes it not run local installed versions of Xwayland. I could not get X
programs to work under wayland without doing "sudo ln -s
~/install/bin/Xwayland /usr/bin".
I noticed this because I had no /usr/bin/Xwayland, but I am c
