I saw the new Linux distribution of GreatCowBasic and thought I would try to install in my Dell PC running Ubuntu 14.10. I have previously installed GCB three years ago and have FreeBasic-0.90.1-linux installed.
Downloaded GCB@Syn.rar fine. Then I had to find a RAR extracter. Extracted it first into the download directory and then I figured it out to extract into the /home/ directory.
Opened the README-LINUX-INSTALL.txt and followed instructions.
Went in and made the install.sh executable.
went to terminal and went to the /home/GreatCowBasic/ Sources/ directory. ls and it showed the install.sh
"
./install.sh build
-e
Compiling GCBASIC Version 0.95.006, Release 2016-01-24
error 77: Invalid command-line option, "i686"
"
Tried it with sudo before it and it did less.
"
/GreatCowBasic/Sources$ sudo ./install.sh install [sudo] password for mmotte:
gcbasic does not exist. Cannot install.
/GreatCowBasic/Sources$
"
Stopped there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not having any Linux experience I can't say if this will work for sure but
I would imagine that the "i686" parameter should read "i386".
Try changing it and reinstall to see if it helps.
Cheers
Chris
Last edit: Chris Roper 2016-02-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In a console at the command prompt, enter 'uname -m' or 'uname -p'. Please post back the result. And, if the result is "i686" then use the following command, while in the Sources directory, to do the build step:
fbc -exx -v -arch 686 gcbasic.bas
If that is successful, then go ahead and do './install.sh install' with root privileges (ie. using sudo).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for reporting the results of 'uname -m/-p'.
With "/opt/GCBASIC" in your path, gcbasic should run no matter what directory you are in.
It is weird that it would state its version as 0.9 22/9/2013. It should be 0.95 2016-01-24. Is it possible you still have the version installed from three years ago?
Executing '~/GreatCowBasic$ gcbasic /version' would not be using the one that you just compiled. It is probably finding your old installation. Try '~/GreatCowBasic$ ./gcbasic /version' and see what you get. Notice the "./" prepended to "gcbasic".
Please also post the results of:
'which -a gcbasic', and
'ls -l /opt/GCBASIC'
And, to work with directory and file names that have spaces, simply enclose the name in quotation marks, eg:
gcbasic "Demos/LED Solutions/LED - Toggle/BlinkLED using Toggle - mega328p.gcb"
The compiled ASM file will be placed in "Demos/LED Solutions/LED - Toggle".
Last edit: T. Lee Davidson 2016-02-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep, it's finding '/usr/bin/gcbasic' first in your path and so it is using that one. You can remove or rename it.
'sudo mv /usr/bin/gcbasic /usr/bin/gcbasic_v90' to rename it.
'sudo rm /usr/bin/gcbasic' to remove it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use gedit and have set up the tools for compiling and burning and someone had the highlighting file which works good.
Gedit works fine with the "space infested"demo filenames but when I hit F5 to compile, gcbasic complains it can't find the file. If I change the file name by scrunching then it works fine.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I use Geany with custom Build commands. Geany uses %f as a placeholder for the current filename. My compile command has %f inside double-quotes: makeasm.sh "%f". This eliminates problems with spaces in filenames.
Perhaps something like that would work for Gedit too. Like, maybe:
"$GEDIT_CURRENT_DOCUMENT_PATH" ? Just a thought.
Glad to hear it's working for you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I saw the new Linux distribution of GreatCowBasic and thought I would try to install in my Dell PC running Ubuntu 14.10. I have previously installed GCB three years ago and have FreeBasic-0.90.1-linux installed.
Downloaded GCB@Syn.rar fine. Then I had to find a RAR extracter. Extracted it first into the download directory and then I figured it out to extract into the /home/ directory.
Opened the README-LINUX-INSTALL.txt and followed instructions.
Went in and made the install.sh executable.
went to terminal and went to the /home/GreatCowBasic/ Sources/ directory. ls and it showed the install.sh
"
./install.sh build
-e
Compiling GCBASIC Version 0.95.006, Release 2016-01-24
error 77: Invalid command-line option, "i686"
"
Tried it with sudo before it and it did less.
"
/GreatCowBasic/Sources$ sudo ./install.sh install
[sudo] password for mmotte:
gcbasic does not exist. Cannot install.
/GreatCowBasic/Sources$
"
Stopped there.
Not having any Linux experience I can't say if this will work for sure but
I would imagine that the "i686" parameter should read "i386".
Try changing it and reinstall to see if it helps.
Cheers
Chris
Last edit: Chris Roper 2016-02-10
I searched in the install.sh script and all the other config files for
the "i686" but could not find it. Otherwise i agree that sounds logical.
Last edit: mmotte 2016-02-10
In a console at the command prompt, enter 'uname -m' or 'uname -p'. Please post back the result. And, if the result is "i686" then use the following command, while in the Sources directory, to do the build step:
fbc -exx -v -arch 686 gcbasic.bas
If that is successful, then go ahead and do './install.sh install' with root privileges (ie. using sudo).
Yes it was "i686" for either of the uname.
fbc compiled fine.
sudo ./install.sh install worked
Then I tried the version test but it did not work. Reading further...I should log out and back in.
I went to the sources directory because that is where we are doing all of this.
gcbasic /version still didn't work
checked the PATH
-GX260:~/GreatCowBasic$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/opt/GCBASIC
changed directory down one level to GreatCowBasic and version worked
GX260:~/GreatCowBasic$ gcbasic /version
Great Cow BASIC (0.9 22/9/2013)
Looks old! Is it using the old install?
Tried to change directory to the demos to try a compile. Terminal did not like the spaces in the directories and file names.
and version test would not work once you got there.
Copied a LEDDim.gcb file back to the GreatCowBasic directory and compiled
-GX260:~/GreatCowBasic$ gcbasic LEDDim.gcb
Great Cow BASIC (0.9 22/9/2013)
Compiling LEDDim.gcb ...
Done
mmotte@mo-OptiPlex-GX260:~/GreatCowBasic$ ls
chipdata January 16 Release List.txt messages-fr.dat
converters LEDDim.asm messages-it.dat
Demos LEDDim.gcb messages-tk.dat
Documentation LEDDim.html preprocess.awk
flash.sh makeasm.sh README-LINUX-INSTALL.txt
Yep, It worked!
Thank you for reporting the results of 'uname -m/-p'.
With "/opt/GCBASIC" in your path, gcbasic should run no matter what directory you are in.
It is weird that it would state its version as 0.9 22/9/2013. It should be 0.95 2016-01-24. Is it possible you still have the version installed from three years ago?
Executing '~/GreatCowBasic$ gcbasic /version' would not be using the one that you just compiled. It is probably finding your old installation. Try '
~/GreatCowBasic$ ./gcbasic /version' and see what you get. Notice the "./" prepended to "gcbasic".Please also post the results of:
'
which -a gcbasic', and'
ls -l /opt/GCBASIC'And, to work with directory and file names that have spaces, simply enclose the name in quotation marks, eg:
gcbasic "Demos/LED Solutions/LED - Toggle/BlinkLED using Toggle - mega328p.gcb"
The compiled ASM file will be placed in "Demos/LED Solutions/LED - Toggle".
Last edit: T. Lee Davidson 2016-02-11
No it really didn't work!
Version is wrong
Looked in the gcbasic.bas file
Should be:
Version = "0.95 2016-01-24"
Not
Great Cow BASIC (0.9 22/9/2013)
It used the old one. More work.
Mmotte, please post the results of the following command from a console:
which -a gcbasic
:~/GreatCowBasic$ ./gcbasic /version
0.95 2016-01-24
~/GreatCowBasic$ ls -l /opt/GCBASIC
total 5152
drwxr-xr-x 2 root root 32768 Feb 11 11:11 chipdata
drwxr-xr-x 3 root root 4096 Feb 11 11:11 converters
drwxr-xr-x 33 root root 4096 Feb 11 11:11 Demos
drwxr-xr-x 3 root root 4096 Feb 11 11:11 Documentation
-rwxr-xr-x 1 root root 3902 Feb 11 11:11 flash.sh
-rwxr-xr-x 1 root root 866564 Feb 11 11:11 gcbasic
-rw-r--r-- 1 root root 1227747 Feb 11 11:11 gcbasic.chm
-rw-r--r-- 1 root root 2965504 Feb 11 11:11 GCBASIC Help.sh5
drwxr-xr-x 2 root root 16384 Feb 11 11:11 Help
drwxr-xr-x 3 root root 4096 Feb 11 11:11 include
-rw-r--r-- 1 root root 40872 Feb 11 11:11 January 16 Release List.txt
-rwxr-xr-x 1 root root 2090 Feb 11 11:11 makeasm.sh
-rwxr-xr-x 1 root root 2089 Feb 11 11:11 makehex.sh
-rw-r--r-- 1 root root 5667 Feb 11 11:11 messages-br.dat
-rw-r--r-- 1 root root 11934 Feb 11 11:11 messages.dat
-rw-r--r-- 1 root root 9957 Feb 11 11:11 messages-de.dat
-rw-r--r-- 1 root root 5670 Feb 11 11:11 messages-es.dat
-rw-r--r-- 1 root root 11314 Feb 11 11:11 messages-fr.dat
-rw-r--r-- 1 root root 6635 Feb 11 11:11 messages-it.dat
-rw-r--r-- 1 root root 6658 Feb 11 11:11 messages-tk.dat
-rw-r--r-- 1 root root 5700 Feb 11 11:11 preprocess.awk
-rw-r--r-- 1 root root 1687 Feb 11 11:11 README-LINUX-INSTALL.txt
-rw-r--r-- 1 root root 1449 Feb 11 11:11 sample gcbasic.ini
-rw-r--r-- 1 root root 1195 Feb 11 11:11 SynToolbars.ini
-rw-r--r-- 1 root root 42 Feb 11 11:11 VersionRelease.txt
:~/GreatCowBasic$ which -a gcbasic
/usr/bin/gcbasic
/opt/GCBASIC/gcbasic
Looks like I have to get rid of the old one.
Thanks
Mike
Yep, it's finding '/usr/bin/gcbasic' first in your path and so it is using that one. You can remove or rename it.
'sudo mv /usr/bin/gcbasic /usr/bin/gcbasic_v90' to rename it.
'sudo rm /usr/bin/gcbasic' to remove it.
I renamed it.
Thank You for your help!!
Mike
You're welcome, Mike. It is good that you reported the issue.
I take it that it is working well now?
Yes, it is working.
I use gedit and have set up the tools for compiling and burning and someone had the highlighting file which works good.
Gedit works fine with the "space infested"demo filenames but when I hit F5 to compile, gcbasic complains it can't find the file. If I change the file name by scrunching then it works fine.
Thanks
That's good to hear, Mike.
I use Geany with custom Build commands. Geany uses %f as a placeholder for the current filename. My compile command has %f inside double-quotes: makeasm.sh "%f". This eliminates problems with spaces in filenames.
Perhaps something like that would work for Gedit too. Like, maybe:
"$GEDIT_CURRENT_DOCUMENT_PATH" ? Just a thought.
Glad to hear it's working for you.