preliminary Linux support

Questions about the BASICtools and MakeItC
basicchip
Posts: 758
Joined: Fri Oct 19, 2012 2:39 am
Location: Lake Tahoe, CA
Contact:

Re: preliminary Linux support

Postby basicchip » Fri Jun 24, 2016 10:10 pm

olzeke51 wrote:.but the challenge!!!

Well start playing with the Tcl source

It all has to do with the execution of bpp and ARMbasic from Tcl. Something about the file system setup or paths is wrong for the way I am doing for Q4OS

It is only really a small part of the code. As Tcl is an interpreter so it is pretty easy to debug, though the syntax is kind of goofy

All the pieces are there, maybe for Q4OS some kind of an application can be put together.

olzeke51
Posts: 273
Joined: Sat May 17, 2014 4:22 pm
Location: South Carolina
Contact:

Re: preliminary Linux support

Postby olzeke51 » Thu Jun 30, 2016 2:40 pm

challenge accepted [but may not be completed- warning]
okay
can I get 32-bit versions of ARMbasic and bpp???
here is my info on the bpp:
olzeke51@q4compaq:~/Coridium$ file -p bpp
bpp: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=356a......., not stripped
olzeke51@q4compaq:~/Coridium$
'
'
error04 - 'firefox' is the scripted browser - I put in my own browser name
'
Later 'gator
Gary
Attachments
error04_resolution.txt
(213 Bytes) Downloaded 100 times

olzeke51
Posts: 273
Joined: Sat May 17, 2014 4:22 pm
Location: South Carolina
Contact:

Re: preliminary Linux support

Postby olzeke51 » Thu Jun 30, 2016 2:53 pm

in regards to one of my first posts - when starting the script or 'wish' from the CL, this would pop up
'
olzeke51@q4compaq:~$ BASICtools
olzeke51@q4compaq:~$ application-specific initialization failed: unknown color name "BACKGROUND"
Error in startup script: can't invoke "winfo" command: application has been destroyed
'
it turns out that the Xserver wasn't getting the color codes for its different elements.
'
with info from this trouble ticket" https://github.com/mate-desktop/mate-desktop/issues/134
'
I copied the below settings into a text file
Xdefaults-new-tcl.txt
no settings verified!! but it works
(6.44 KiB) Downloaded 108 times

then I used this command from my home directory
olzeke51@q4compaq:~/Coridium$ xrdb -load ~/Documents/Xdefaults-new-tcl
'
now I no longer get my 'BACKGROUND' error message
and the Window looks usable [in Q4os]
'****this has to be done everytime you reboot/login !!!! -- will work on scripting it

basicchip
Posts: 758
Joined: Fri Oct 19, 2012 2:39 am
Location: Lake Tahoe, CA
Contact:

Re: preliminary Linux support

Postby basicchip » Thu Jun 30, 2016 2:56 pm

I know very little about Linux internals.

Someone once told me that you could compile a C program on Linux to run in both environments, and I believe the make file for bpp does that.

But like I say I really don't know how that works and need help from the users.

If it really is a 32 vs 64 bit thing, you should be able to make bpp on your system.

olzeke51
Posts: 273
Joined: Sat May 17, 2014 4:22 pm
Location: South Carolina
Contact:

Re: preliminary Linux support

Postby olzeke51 » Thu Jun 30, 2016 3:26 pm

I too know very little of internals - but I'm learning.
32bit can be run on 32 or 64bit linux, but 64 needs a 64 environment -- per the Internet
okay - gary

basicchip
Posts: 758
Joined: Fri Oct 19, 2012 2:39 am
Location: Lake Tahoe, CA
Contact:

Re: preliminary Linux support

Postby basicchip » Thu Jun 30, 2016 5:29 pm

In Q4OS how do I tell if it is 32 or 64 bit that I loaded, can't remember and tossed the CD after the load.

I don't know when the last 32 bit machines were built, probably over 10 years ago, I have an ancient Toshiba laptop (maybe 20 years old, I'll see if it still boots). Might be worth picking up something newer on eBay

After you make bpp, post it here

olzeke51
Posts: 273
Joined: Sat May 17, 2014 4:22 pm
Location: South Carolina
Contact:

Re: preliminary Linux support

Postby olzeke51 » Fri Jul 01, 2016 11:32 am

okay - for a proof of concept - I took the bpp and ARMbasic [both 32bit] from the 'Linux work in Progress' link on the Tech Support page
and moved them to the /usr/local/bin/Coridium/ location.
'
It ran without errors - BUT there were other 'funnies' in the DEMO mode.
'
the linux command ' uname -a' will give a clue if it mentions i686 etc -->32 bit
if there is a 'x86-64' then .....
in answer to your question - Q4os comes in both 64 & 32 bit versions.
Yes, I have old computer resurrected-throw-aways - guess I ought to move into the 20-teens!!!
'
STILL not sure how I would build 'bpp'.
BTW - I put the original ARMbasic back in the soup and noticed no difference. DEMO mode though, same 'funnies'
Is ARMbasic used in DEMO mode? it doesn't appear to be.....
'
onward - the journey calls
Gary
UPDATE
okay - put the older ARMbasic back in the soup and got BLINKY to work !! with a real 1114
now I need to work on the 'default editor' - another step in the journey/challenge
Good Day y'all

basicchip
Posts: 758
Joined: Fri Oct 19, 2012 2:39 am
Location: Lake Tahoe, CA
Contact:

Re: preliminary Linux support

Postby basicchip » Fri Jul 01, 2016 3:38 pm

To build bpp, you do a make, which is pretty standard for building anything Linux

ARMbasic is used in demo mode as both compiler and emulator.

I compiled them on a 64 bit system, but set no specific settings, so they were compiled with whatever Ubuntu uses for default.


Return to “Software issues”

Who is online

Users browsing this forum: No registered users and 3 guests