Panos, thanks a lot.
Ralf
> On 29. Jun 2018, at 00:18, panagiotis merakos wrote:
>
> Hi all,
>
> This problem happened because some on-rev servers (Jasmine, Sage and Diesel)
> had only the 64 bit version of this library, while others (e.g. Tio) had both
> the 32 and 64 bit version.
>
> Rob
Hi all,
This problem happened because some on-rev servers (Jasmine, Sage and
Diesel) had only the 64 bit version of this library, while others (e.g.
Tio) had both the 32 and 64 bit version.
Robin has identified and fixed the problem, so the 32bit version of LC
Server 9 now does work on all on-rev
@Ralf,
I see the same error when trying to install LC 9 32 bit on Sage.
However the exact same setup is successful on Tio.
So I guess some of the on-rev servers do have this library, while others
don't. I will ask Robin about this.
Best,
Panos
--
On Wed, Jun 27, 2018 at 12:08 PM, Ralf Bitter v
Hi Matthias,
> On 26. Jun 2018, at 23:57, Matthias Rebbe via use-livecode
> wrote:
>
> Hm, On-Rev support told me that GLIBC 2.1.4 is needed to run Livecode Server
> 9 64bit on On-Rev. The 32bit version is working on On-Rev with the older one.
> They did not mention that this library is also
Hi Charles,
> On 27. Jun 2018, at 08:44, Charles Warwick via use-livecode
> wrote:
>
> Are you referring to asynchronous functions that are only available in the
> business edition? These will fail due to the same issue as tsNetGet and
> tsNetSendCmd, so no need to file a separate bug repor
Hi Matthias,
> On 27 Jun 2018, at 7:57 am, Matthias Rebbe via use-livecode
> wrote:
>
> Hm, On-Rev support told me that GLIBC 2.1.4 is needed to run Livecode Server
> 9 64bit on On-Rev. The 32bit version is working on On-Rev with the older one.
> They did not mention that this library is also
Hi Ralf,
> In a nutshell following the results of my tests:
>
> - There is bug 18961. An issue regarding tsNetSendCmd() is presumably
> related. Other Indy features work as expected.
The issue is that any asynchronous tsNet function will fail on LC server. I
have not yet had time to go back a
> Am 26.06.2018 um 20:12 schrieb Ralf Bitter via use-livecode
> :
>
> - On On-Rev using LC server 9 tsNet does not work at all because glibc needs
> to be upgraded as I was told by support.
> Custom directives in ~/.bashrc didn’t help, these seem to be ignored by
> Apache.
>
Hm, On-Rev supp
Panos, did tsNet tests only on localhost like you,
using 64-bit Ubuntu 16.04 and 64-bit Ubuntu 16.04 Server.
In a nutshell following the results of my tests:
- There is bug 18961. An issue regarding tsNetSendCmd() is presumably related.
Other Indy features work as expected.
- Although the busin
I have it working with LC Server 9 on an Ubuntu 16.04 64bit but only tested
on localhost. But if I remember correctly there are a couple of people
using tsnet with LC server on an actual server (Ralf maybe??)
Folks if you read this and use tsnet with LC Server could you share some
details about yo
Hi Panos,
thanks for the explanation.
And yes, i was asking about the tsNet/LC server issue. I am in urgent need to
get it working.
Btw., as it even does not work on your own hosting platform On-Rev/Livecode
Hosting, did someone at Livecode ever used tsNet with LC server successfully?
And if s
Hi Matthias,
Pending status means that the LC team needs to take action in order to
confirm (or not confirm) the bug. We usually set this status when a bug
requires a bit of setup to test. I assume you ask about the tsnet with LC
server issue.
Best,
Panos
On Mon, Jun 25, 2018, 18:32 Matthias Reb
Hi,
does anyone know what exactly the status “pending” in the LQCC does mean?
Regards,
Matthias
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
h
13 matches
Mail list logo
