Hi,
I have a BlackBerry KeyOne running Debian using Termux. I undergo risky open heart surgery soon and have setup on my lappy scripts and basic program to send off mass SMS, faxes and emails using command line programs and operations for alerting friends and if needed final wishes. I want to bring this all to my BB KeyOne.
Suggestions? If ARM64 deb does not exist, can you guide me to how I would compile it from what source?
Surgery next week.
ARM64 Deb?
-
- Posts: 21
- Joined: May 06, 2019 17:34
- Location: Chicago
- Contact:
-
- Posts: 21
- Joined: May 06, 2019 17:34
- Location: Chicago
- Contact:
Re: ARM64 Deb?
Please test this:
https://drive.google.com/drive/folders/ ... cW-qKCrNdQ
https://drive.google.com/open?id=1xHLbd ... gy_qwaA6mP
It is a new build of FreeBASIC-1.06.0 packed to .deb
install:
uninstall:
It would be great if you or anybody could test it! And give me feedback!!!
https://drive.google.com/drive/folders/ ... cW-qKCrNdQ
https://drive.google.com/open?id=1xHLbd ... gy_qwaA6mP
It is a new build of FreeBASIC-1.06.0 packed to .deb
install:
Code: Select all
sudo dpkg -i fbc_1.06.0_arm64.deb
sudo apt install -f -y
Code: Select all
sudo dpkg -P fbc
sudo apt autoremove -y
Last edited by sgaba on Mar 07, 2023 8:15, edited 2 times in total.
Re: ARM64 Deb?
Tested it on Debian on Termux on FlymeOS (Android 6.0) Runs and compiles code fine, But If/When the compiled program tries to create a window, it segfaults. Console only programs seem fine
I'm pretty sure I have all the dependencies, So I'm a little at a loss. Shouldn't the compiler error if there was something wrong?
I'm pretty sure I have all the dependencies, So I'm a little at a loss. Shouldn't the compiler error if there was something wrong?
Re: ARM64 Deb?
The ubuntu-mate Raspberry Pi 3 windows work fine. Maybe there's a problem with Linux on Android.
You have all the dependencies because if you don't have all the dependencies compiler (linker) give error like:
ld: cannot find -lX11
Do you use: Screen or ScreenRes?
Did you test old Stw build?
http://users.freebasic-portal.de/stw/builds/_manual/
You have all the dependencies because if you don't have all the dependencies compiler (linker) give error like:
ld: cannot find -lX11
Do you use: Screen or ScreenRes?
Did you test old Stw build?
http://users.freebasic-portal.de/stw/builds/_manual/
Re: ARM64 Deb?
If you want to check for "run-time" errors, you'll have to compile with (at least)Manpcnin wrote:But If/When the compiled program tries to create a window, it segfaults.
-exx compiler switch (on CLI calling fbc).
I'm usually using: -exx -w pedantic (for a debug build).
Once the code is "fixed", you simply compile it again, without those switches.
-
- Posts: 606
- Joined: Nov 28, 2012 1:27
- Location: CA, USA moving to WA, USA
- Contact:
Re: ARM64 Deb?
It has been a very long time, but I have had the circumstance that programs compile OK but faulted out on execution - graphics only. I did have a missing lib without that message. Now, after an install, I have a suite of programs that catches this.The missing was one part of a graphics lib --- xcb or something. Each Linux distribution may package library sets as they choose. The PI organization may desire to be transparent, but they just don't have the resources to document all that they do to make everything work. And, Broadcom has NO desire to be transparent.
*IF* a lib is missing after compile - in Linux - use
ldd <exename>
This should list dependencies with a flag on what is missing.
Much more likely is an array error. Most likely a string operation.
If the error isn't obvious and -exx gives you no better information to chase:
(install gdb if not already loaded)
compile with -g
gdb <exename>
r
you should have a little more info, now.
I have several rPI versions with no problems.
(All are run headless, but all still serve up the graphics fine.)
david
*IF* a lib is missing after compile - in Linux - use
ldd <exename>
This should list dependencies with a flag on what is missing.
Much more likely is an array error. Most likely a string operation.
If the error isn't obvious and -exx gives you no better information to chase:
(install gdb if not already loaded)
compile with -g
gdb <exename>
r
you should have a little more info, now.
I have several rPI versions with no problems.
(All are run headless, but all still serve up the graphics fine.)
david