I am looking to install Freebasic on a Raspberry Pi. I have already looked at the Freebasic forum - but it seems from a lot of posts that others have found that following the steps shown no longer end up working.
Other Pi forums have said that a working installation can be difficult to achieve.
I am trying to find a way to get the freebasic compiler running on an otherwise virgin installation, starting from Noobs.
At first I thought it was too difficult for me, but even some serious pi-enthusiasts who were going to help me have ended up stumped.
This link has a step by step that can be considered simple, as long as attention is paid to the directories and first step, installing some necessary packages.
I followed steps 1 through 5 and installed it on my Raspberry.
From what is reported there, "part of the problem is that FreeBASIC is written primarily in FreeBASIC, so you need a working compiler to initialize the latest version".
Therefore, you need to install an "old version" (step #2), clone the latest version and compile it with the old version (step #3). Uninstall old version (step #4) and install new version (step #5).
In step #3 I used the make -j4 command. I have a Raspberry Pi 3 model B.
In my case, I used fbc_linux_armv6_rpi_0365_2020-01-12.zip as "old version". I tested the installation by compiling and running a program and it was OK, working perfectly.
Related
I installed Scilab 5.5.2 on Windows 10, and then installed the Scilab Code Generator toolbox.
However, when I start Scilab, the following message appears and I can't use the toolbox. This problem occurs for every toolbox.
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
atomsLoad: An error occurred while loading 'xcos_code_generator-0.9.20190122':
File "C:\Users\光\AppData\Roaming\Scilab\SCILAB~1.2\atoms\x64\XCOS_C~1\09E129~1.201\macros\names" does not exist or read access denied.
(光 is my username.)
I suppose the problem comes from "\Scilab\SCILAB~1.2" in the middle of the file path. In my computer, the only folder in "Scilab" is "scilab-5.5.2", so indeed the software cannot find the file it's looking for.
Does anyone have any ideas?
I need to use the toolbox at work soon, so any help is greatly appreciated. Thank you in advance.
Note: I'm not using the latest Scilab 6.0.2 because it fails to work on my computer. It closes immediately after I open it.
I solved the problem by myself.
It was my user name "光" that caused the problem. I found people saying that user names in full-width characters such as Japanese sometimes cause problems like this.
The solution is to create another user account with a name in half-width characters and install Scilab in that account. (Just changing the full-width user name doesn't work because it doesn't change the filenames that already exist.)
I couldn't find the solution until today because I was searching for solutions only in the context of Scilab, not in the context of software in general.
I hope this answer helps someone.
I'm not sure why you are using an outdated version of Scilab. The latest version is 6.0.2 on Windows. If the newer version doesn't work properly then that's the problem you need to fix first. To test your Scilab installation you may run it in the terminal. Find the installation folder. For me, it is C:\Program Files\scilab-6.0.2\bin the on cmd go to the path and run Scilex.exe. If not uninstall everything and install it in a proper way. My recommendation is to uninstall the old Scilab you already have. Then:
Install Chocolatey package manager
Open PowerShell as Admin and run choco update all -y, once in a while update your packages this way.
run choco install Scilab -y
then open the Scilab software
run the atomsInstall("xcos_code_generator") in the console
runt the atomsLoad("xcos_code_generator") to make sure your package is installed properly. You should see this as a result:
--> atomsInstall("xcos_code_generator")
Scanning repository http://atoms.scilab.org/6.0 ... Done
ans =
!xcos_code_generator 0.9.201901 user SCIHOME\atoms\x64\xcos_code_generator\0.9.201901 I !
--> atomsLoad("xcos_code_generator");
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
Load help
Load demos
When I run apt install r-base it provides me with a slightly out-dated version of R. When I tried to look up how to get a newer version, much of what I found did something to the file /etc/apt/source.list. The content of this file is
#deb cdrom:[Linux Mint 18.3 _Sylvia_ - Release amd64 20171124]/ xenial contrib $
Most instructions suggest appending something like
deb http://cran.rstudio.com/bin/linux/debian wheezy-cran3/
But none of the various suggestions I've read have worked--presumably either because they were for non-Mint distros or they were for outdated versions of Mint. I tried taking something that I found, like
http://cran.ma.imperial.ac.uk/bin/linux/ubuntu trusty/
and editing it with the codename that I found elsewhere which seems to be the most recent, hence making it
http://cran.ma.imperial.ac.uk/bin/linux/ubuntu sylvia/
But when I ran the update it couldn't find the repo, presumably because places that have Trusty don't necessarily have Sylvia--although maybe it didn't work for some other reason. (And I notice the UK address which probably is bad for me to be using in America, but I don't really get how I'm supposed to find an address that will have the right files.)
Since I see a number of times when this question has been asked and solutions always seem to be short-lived, applying only so long as that particular version is hosted by that particular address and is the latest version--can I ask something where the answer might have a little more longevity: In general, how do you find the right thing to add to your /etc/apt/source.list file to make this work? How do you find the right repo source (same thing as a mirror?), the current codename, and so on? (It would also be nice to have a generalized procedure for how to solve this, because I basically ran into the same problem on my old computer with a 32-bit architecture, and would like to have R running on that too without having to ask the question a second time--but presumably the specific thing and place I'll have to download for that is different.)
i was trying to build "brackets sprint 40" from source code (by following #jasonsanjose instructions look #4816 and the official wiki's page here) in my 32bit Wheezy, Using CEF3 (Verion 3.1547.1406_linux32_release with glibc 2.13) and everything was OK .
when i ran grunt build and grunt installer the output was: Running "build" task
Running "build-linux" task
Done, without errors.
and when i installed .deb package and executed it in the terminal , this error has been thrown:brackets: libcef_dll/wrapper/libcef_dll_wrapper.cc:120: int CefExecuteProcess(const CefMainArgs&, CefRefPtr): Assertion `false' failed.
Aborted
I did rebuild it many times, but the problem persist.
And this is where i stopped, i don't know where the problem lies.
some help will be appreciated, thank you in advance.
There's a duplicate of this question with longer discussion posted here - https://github.com/adobe/brackets/issues/8170.
Note: This problem shouldn't affect a "vanilla" brackets-shell build on Linux -- it's specific to a hack some people have developed to support an older version of Debian than Brackets officially supports. This requires swapping in a newer version of the CEF library, which is not always easy to do since they are not usually backwards-compatible.
I wanted to do something with qtjambi. I installed version 4.6.3. I can run the examples, but when I want to compile for example ArthurFrame, I get:
ArthurFrame.java:47: package com.trolltech.qt.core does not exist
When searching for help, it looks everything is dead. The mailing-lists do not exist anymore and on #qtjambi there is no response. Should I just not start with qtjambi, or is there another place to get help?
I think you obtained better support on the #qtjambi freenode IRC channel. When using IRC for support you should be prepared to ask your question and wait for an answer, at least 12 months but sometimes a few days, during this time you should stay connected and "idling".
From there it was discovered you are using a Linux distribution that already has automated builds of a recent QtJambi available.
Ubuntu: https://launchpad.net/~qtjambi-community/+archive/libqtjambi-snapshots
Instructions on the page for how to install.
openSuSE, SuSE, Fedora, RHEL, CentOS: https://build.opensuse.org/package/show?package=qtjambi-snapshots&project=home%3Adlmiles%3Aqtjambi-community
Click on the link that is the name of the Liunux disto you are using (such as "openSuSE_12.2").
Click on the link that says "Go to download repository".
Click on the file *.repo to download and save on the local system. Such as "home:dlmiles:qtjambi-community.repo"
Install this file as 'root' into /etc/yup.repos.d/home:dlmiles:qtjambi-community.repo
Edit the file to set the 'enabled=1' or manually add the --enablerepo=home:dlmiles:qtjambi-community when using yum to install.
Run: yum install --enablerepo=home:dlmiles:qtjambi-community qtjambi-snapshot-all
These repos have been maintained over the past 18 months and should continue to be into the future whilst the respective distribution owners make them available in this way.
Once installed in this way you will get updates as and when they are published as part of your normal system package management. So is has historically been about every 3 months.
I am trying to compile Rcpp_0.9.7 from source on sparc-sun-solaris2.10. I am getting the following error when I try to use install.packages:
sh: make: not found
ERROR: compilation failed for package 'Rcpp'
From research on the internet, it appears others have had similar problems with solaris. Unfortunately I do not know very much about which compilers I should or should not be using. One thing I am beginning to realize, however, is that solaris seems to be a sub-optimal environment for running R (in terms of performance as well as convenience).
Solaris can mean different things: it could be Solaris on x86, or Solaris on Sparc.
According to the Rcpp build results page on CRAN, Rcpp does now build on x86 Solaris (thanks to a recent patch by Martyn Plummer) but not Sparc Solaris. We were just discussing that this week on the rcpp-devel list.
As for your error, you are lacking critical components, namely the make tool. You likely lack more. Your conclusion is correct, though. Depending your level of Unix knowledge, you may be best off to simply install Ubuntu and enjoy tens of thousands of pre-built packages, including R and well over a hundred related packages.
Not really a solution but too long for a comment.
First of all get a decent environment for your testing of building Rccp on Solaris. Personally I use VirtualBox on my Windows workstation. This way I have an environment that I can control myself and do not depend on any grumpy SysAdmin. Best of all: there's no cost involved! When you are confident with your build you can either (1) move the binaries over to your target host or (2) replicate the build setup on your target host.
Secondly you can use these instructions to set up a proper build host on Solaris. (you seem to be lacking some crucial tools!). Remember to use gmake when building as per the instructions in the posting.
As Dirk mentioned, you're lacking the make command. If you're running Solaris 10
or earlier, then you need to find your installation media and pkgadd SUNWsprot.
If you're running Solaris 11 or later, then
pkg install developer/build/make
will get you that utility. You probably need the system headers as well, which are in pkg://solaris/system/header for Solaris 11 and later, or SUNWhea in earlier releases.
I see that you mention sparc-sun-solaris2.10 in your question - is there any opportunity for you to update to Solaris 11 or later? The developer environment is muchmuch nicer in the newer releases. Certainly easier to get a copy of a compiler....