I wanted to set up my own Cardano Node and followed the steps on this page https://developers.cardano.org/docs/get-started/installing-cardano-node. Has everything also more or less worked but at this point I get no further I get this error again and again Terminal Cabal All Errors
I think it has something to do with the M1 Chip, but it would be very kind if someone can help me
Related
I'm on a big problem in my actual project. Everytime when I try to run iOS simulator this error appear in my log. I tried chance Xcode version, delete all pods, change zshrc file, but nothing happens.
Anyone to help? If I create a new project and run npx react-native run-ios works to me but on this specific project dont run anything.
Infos:
RN Version: 0.64.0
oS infos: Macbook Air M1 big Surr
Node version: v14.0
Follow the error:
objc[24913]: Class AMSupportURLSession is implemented in both /usr/lib/libauthinstall.dylib (0x1edc1bbc8) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x118130318). One of the two will be used. Which one is undefined.
** BUILD FAILED **
The following build commands failed:
PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/viniciusachterberg/Library/Developer/Xcode/DerivedData/AgrinessPresence-aatyymmaxydmoqfhtgtytzoqepin/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/FBReactNativeSpec.build/Script-48ABC94909B35DCD398CB750635A0D8D.sh
(1 failure)```
I am working with tensorflowjs in node. when i run the code, "const tf = require('#tensorflow/tfjs-node');" it throw an error "zsh: illegal hardware instruction node app.js".
i am using macbook air M1 chip.
Official #tensorflow/tfjs-node does not support Apple's M1 CPU just yet
There are unofficial ways to make it work (by using M1 build of tensorflow.so and rebuilding NodeJS bindings), but that is anything but trivial
UPDATE: as requested, a bit more info
there is Apple's port of Tensorflow that works on M1, but Apple stopped developing it and last update is from ~2 years: https://github.com/apple/tensorflow_macos
and there are several 3rd party ports, for example https://towardsdatascience.com/installing-tensorflow-on-the-m1-mac-410bb36b776
also, suggest going through TF's GitHub for M1 issues: https://github.com/tensorflow/tensorflow/issues?q=M1
in either case, once you have tensorflow, you still need to manually rebuild #tensorflow/tfjs-node so it binds to it which is non-trivial.
In submitting my R job to a cluster using the Rscript myscript.R command, I keep getting an error message saying the packages I have asked to load do not exist. However I have installed these packages onto a library on my profile. Do I have to set the working directory into the same pathway as the where the R packages are contained? I am genuinely puzzled by how to fix this error.
Thanks
Nikhail
try to add directly the install.packages command in your script. Like that, you're sure it will install properly:
for example add that at the beginning of your script (of course change "pacman;" for your real package and add one line per package):
if (!require("pacman")) install.packages("pacman")
I had this kind of problem before when the shell didn't call the good R for me (other version than the one I thought or 32 bits vs 64 bits). Don't know if it's your problem however...
I have created a new angular project in Visual Studio 2017 in my work laptop, I'm getting the Node invocation exception error when I run the program.
I had the same issue in my home laptop but it was resolved after I installed the latest version of node.js.
I have installed the same nodejs version in my work laptop but the issue still persists. when I run the node - v command in my work laptop instead of the version number I'm getting a different name.
Could someone please help with this.
Exception messageNode and NPM version
I found that we have CA node installed in my office laptop so it was showing 2 nodes. I updated the environment variable path to list the node.js in up front so it takes the priority, this issue has been resolved now.
I wanted to install The Gimp on my mac. It's not in the HomeBrew tree, so I decided to install it with MacPorts, which I've never used before, and installed today just to build The Gimp. I used the command recommended at http://alemani.com/installing-the-gimp-with-macports/ namely
sudo port -v install gimp +quartz +animation +python27 -x11
After more than 5 hours, I got this:
---> Activating gimp #2.8.14_0+quartz
x ./
x ./+COMMENT
x ./+CONTENTS
x ./+DESC
x ./+PORTFILE
x ./+STATE
x ./opt/
x ./opt/local/
x ./opt/local/share/
x ./opt/local/share/gimp/
x ./opt/local/share/gimp/2.0/
x ./opt/local/share/gimp/2.0/themes/
x ./opt/local/share/gimp/2.0/themes/Nodoka/
x ./opt/local/share/gimp/2.0/themes/Nodoka/gtkrc
---> Cleaning gimp
---> Removing work directory for gimp
Error: Port + not found
and the job stopped. Now, The Gimp is installed, and it seems to be working, although I haven't done any real testing. But the verification that the website above indicates will happen never took place.
What does the error message mean? Is there a way I can use MacPorts to audit if the build was successful, and perhaps to repair it? Or, can I fix whatever was wrong and resume the build? (I'm not willing to wait another 5 and half hours to get to this point, though.) Or can I say to hell with it, and uninstall The Gimp and MacPorts? How do I do this? (I know there are pre-built binaries out there, and I would have grabbed one if I'd known the build was going to take so long.)
I really don't want to invest any time in learning MacPorts, since I'm happy with HoneBrew, so if someone can lead me by the hand, I'd be grateful.
The error message indicates you had a space between + and one of the variant names in the command line you invoked. That likely means gimp was not installed with the variants you chose – you can check which variants were used by running port installed gimp.
Anyway, if GIMP is running as you expect it to, you don't need to do anything at this point. You can force the check you were missing by running sudo port rev-upgrade (and it will also look a little different from the output mentioned on the website), but it's really just a sanity check that should not find any problems.