Puppy Linux Discussion Forum

[jafadmin]

4.2

when I try to execute a compiled program from geany using F5 it fails to execute and the window hangs. It turns out that the permissions that are set on the geany_run_script.sh file are everything but execute. WT

Can someone please tell me how to fix this? I have no idea how geany sets the permissions on that file.

[Bruce B]

It doesn't need to be executable

Proof make a little text file and write the command
echo hello world as the file's text

Then

. filename
source filename
sh filename
bash filename

See for yourself if it runs the command echo hello world

[jafadmin]

We're talking 4.2 here.

1. Only "sh filename" and "bash filename" work as you say.
2. Geany automatically generates the script file
3. It don't work.

The topic isn't about how you or I can make a script execute, it is about what we can do to make geany's script work right.

In 4.12 the generated script has execute permissions and works properly. you can invoke the script from the command line using the ./ method and it works.

In the 4.2 distro the geany_run_script.sh doesn't execute. It fails with a "permission denied" I know how to make a script execute. We all do. Geany in 4.2 doesn't. That's my point. It's a bug.

Can someone please point me in the right direction on how to patch this in geany?

[WhoDo]

[jafadmin]

Ok. I was afraid of that.

Thanks.

[SOLVED] in this thread: http://www.murga-linux.com/puppy/viewtopic.php?t=40666

[Bruce B]

I compiled my own Geany. What I noted was the
default location came later in the path than the
Puppy version. So I deleted the Puppy version.

As far as this not working . . .

. filename
source filename

It always work in a terminal emulator - until ???,
if a change? May be installing Pizzasgood's GTK did it.

Not important, if I note anything significant I'll be back.
I've not looked into it. I was surprised to read it didn't
work.

[technosaurus]

I have ID'd a couple things on this in the new bug tracker here:
http://code.google.com/p/puppy-development/issues/detail?id=4

[r__hughes]

In pup4.2+ geany has a problem being a c-runtime-environment.
It will compile & build but NOT run a c-program

In the meantime the solution is to edit the geany preferences
edit/preferences/Tools/Terminal/ to read

[sfoster]

Hi,
I'm having a problem executing code in Genie using the Freebasic compiler. I installed the Freebaic.pet package from the repository, but instead of sitting there, the bash window came up and shut down so fast that I hardly had time to see it. As to the solution r_hughes offered, I couldn't mimicked the file path because there doesn't seem to be anything labeled xterm in the x11R7/bin. I don't think the configuration is the same (I'm running lucid puppy 5.0), but I still tried inserting the line

[don570]

There's a new version of geany that has been released with
a lot of bug fixes. I made a pet package.
Available at www.esnips.com/web/lupu

[sfoster]

I will definitley try it and let you know how it goes. Thanks in advance.
-yours
S

[sfoster]

Okay,
I tried installing the new copy of Geany last night, but unfortunately there doesn't seem to be much progress in that area. If you are installing a new copy of Geany, do you have to uninstall the old one first? Another thing I thought of has to do with the code behind the execute command. I noticed a section somewhere in the preferences menu that had to do with setting special options for the execute command and it had what looked like a binary execute command followed by the letters fbc (the compiler name). Could freebasic be requiring some special options needed to execute? Also, the status of the compile button seems to have deteriorated. Before, I could press it, and the compiler window at the bottom of the screen would give me an error message about not finding a necessary file. Now the button is completely ghosted. I'm not sure, but could this have anything to do with trying to install over the old Geany incorrectly? One other thing happened that leads me to this conclusion. When I go to create a new file, there used to be a whole bunch of templates. The templates, it appears, have been shifted into a submenu called old templates, or something like that. It kind of looks to me like the program overwrote some things without overwriting others.
If anyone is reading this post before the next couple hours, I will try to get on puppy again and fill in some of the details I might have not clarified very well. Thanks again to don570 for the link.
Yours,
-S

[npierce]

[don570]

If you want to see what code you've installed
and where you've installed it
the command in puppy is

[sfoster]

I ended up busier than I thought I would be (I would have clarified the error message sooner) but I did try compiling code from inside the terminal just to see if the problem was Freebasic's (from earlier), and that worked. It made a binary just fine. Sorry to keep the details waiting.
I should also clarify that I havent tried the -e bash -c command together with the new install of Geany yet. They were separate attempts, so trying the two together might yield new results.
Hang, on Im going to load a copy in ram and repost on the error message details, because due to a very stupid mistake on my part, I forgot to test the new version of Geany in ram before installing it to my pup-save file.
Oh, I should also mention before I sign off that the file was actually named hi.bas. I think bash just didn't print the file extension for some reason when it was relaying the message back to me. I think the new version does recognize .bas files because in one of the lower windows immediately below the editing pane, it says "file type: Freebasic." I will check again just to make sure.