Op zo 4 mrt. 2018 16:31 schreef Alajos Odoyle :
>
> On 2018-03-04 13:50, Guus Snijders via arch-general wrote:
> >
> > Just out of curiosity; could you try deleting the symlink and
> LD_preloading
> > /usr/lib/libtifinfo.so.5 ?
> >
> > The current replies on the ML are a
On 2018-03-04 13:50, Guus Snijders via arch-general wrote:
Just out of curiosity; could you try deleting the symlink and LD_preloading
/usr/lib/libtifinfo.so.5 ?
The current replies on the ML are a technically correct, though a bit blunt.
If the preload tricks actually works, we could advice
Op vr 2 mrt. 2018 12:18 schreef Alajos Odoyle :
> On 2018-03-02 11:38, Dan Haworth wrote:
> >
> > I had the same issue, seems to be related to the following bug
> > https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0 to
> > get things going again.
> >
> >
On 03/03/2018 11:56 AM, Alajos Odoyle wrote:
> On 2018-03-02 13:07, Levente Polyak via arch-general wrote:
>>
>> That's literally an incredibly stupid idea. Symlink
>> /usr/lib/libtinfo.so.5 to /usr/lib/libtinfo.so.6 does not magically
>> make it compatible for both, it is ABI incompatible that's
Op za 3 mrt. 2018 18:14 schreef Doug Newgard via arch-general <
arch-general@archlinux.org>:
> On Sat, 3 Mar 2018 17:56:52 +0100
> Alajos Odoyle wrote:
>
> > On 2018-03-02 13:07, Levente Polyak via arch-general wrote:
> > >
> > > [symlink lib version]
> >
> > It will do
On Sat, 3 Mar 2018 17:56:52 +0100
Alajos Odoyle wrote:
> On 2018-03-02 13:07, Levente Polyak via arch-general wrote:
> >
> > That's literally an incredibly stupid idea. Symlink /usr/lib/libtinfo.so.5
> > to /usr/lib/libtinfo.so.6 does not magically make it compatible
On 2018-03-02 13:07, Levente Polyak via arch-general wrote:
That's literally an incredibly stupid idea. Symlink /usr/lib/libtinfo.so.5 to
/usr/lib/libtinfo.so.6 does not magically make it compatible for both, it is
ABI incompatible that's the whole point of a soname bump. Anything linking to
On March 2, 2018 12:38:33 PM GMT+01:00, Dan Haworth wrote:
>On 02/03/18 11:17, Alajos Odoyle wrote:
>> On 2018-03-02 11:38, Dan Haworth wrote:
>>>
>>> I had the same issue, seems to be related to the following bug
>>> https://github.com/mono/mono/issues/6752. I downgraded
On 02/03/18 11:17, Alajos Odoyle wrote:
On 2018-03-02 11:38, Dan Haworth wrote:
I had the same issue, seems to be related to the following bug
https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0
to get things going again.
--dan
Thanks, that was quick! I also had to
On 2018-03-02 11:38, Dan Haworth wrote:
I had the same issue, seems to be related to the following bug
https://github.com/mono/mono/issues/6752. I downgraded ncurses to 6.0 to
get things going again.
--dan
Thanks, that was quick! I also had to install libtinfo5 (AUR) and
symlink
On 02/03/18 10:34, Alajos Odoyle wrote:
Hi all,
When trying to run OpenRA from the community repository or when
building the package myself (using the community PKGBUILD) I get Mono
exceptions like the one below [1]. At first I thought it could be an
upstream issue but sure enough it builds
Hi all,
When trying to run OpenRA from the community repository or when building
the package myself (using the community PKGBUILD) I get Mono exceptions
like the one below [1]. At first I thought it could be an upstream issue
but sure enough it builds just fine when using a clean chroot. As I
12 matches
Mail list logo