[Gambas-user] Problems with gbs

[Jussi Lahtinen]

This problem is now "solved".
I'm going to do distribution update, and because of that I temporarily
change my fstab:
/tmp            ext4    relatime,nosuid,noexec        0       2
-->
/tmp            ext4    defaults        0       2

So, looks like even when gbs3 is not executed in /tmp, it is enough that
compiled byte code is in /tmp... it's marked as executable.
Is it possible to change this behaviour? Isn't byte code just read for
interpreter, and not executed by itself..?
Or maybe there could be alternative path for byte code (example
~/.gambastmp) that would be automatically cleared when
execution ends?

Jussi





On Wed, Apr 6, 2011 at 20:13, Jussi Lahtinen <jussi.lahtinen at ...626...>wrote:

> Hi!
> I tried to run the benchmarks. But I couldn't run gambas script.
>
> $ gbs3 -v -c ./testscript
> gbs: Main procedure not defined, create it
>
> OK, then I added "Sub Main()" and "End" to the script.
>
> $ gbs3 -v -c ./testscript
> gbs: Main procedure not defined, create it
> MMain.module:42: error: 'Main' already declared
>
> # Gambas Project File 3.0
> Title=Gambas Script
> Startup=MMain
> ...
>
> If I run it just with "./testscript" I won't get any errors, nor any
> indication that program was ran or not.
>
> Gambas 3 rev 3735 @ Ubuntu 10.10 64bit
>
> Jussi
>