make failed, uncaught signal 11 error when installing Jekyll - jekyll

make failed, uncaught signal 11
Gem files will remain installed in C:/Ruby26-x64/lib/ruby/gems/2.6.0/gems/http_parser.rb-0.6.0 for inspection.
Results logged to C:/Ruby26-x64/lib/ruby/gems/2.6.0/extensions/x64-mingw32/2.6.0/http_parser.rb-0.6.0/gem_make.out
Successfully installed bundler-2.1.4
Parsing documentation for bundler-2.1.4
Done installing documentation for bundler after 4 seconds
1 gem installed
C:\Users\ryan1>jekyll -v
'jekyll' is not recognized as an internal or external command,
operable program or batch file.

Sometimes, in the late hours of the night, the jekyll command is aliased to hyde. And of those times, sometimes it will respond to your request pleasantly and run as expected, but other times it can be quite unfriendly. When that happens, I usually wait until morning and then try again when it's behaving better.
That or the executable is missing from your path. Which is the case here? Who can say? But it's probably the first one.

Related

warn Package undefined has been ignored because it contains invalid configuration. Reason: Cannot find module 'undefined/package.json'

In my app.json folder, I have everything bundled nicely, but I have one undefined package at the bottom of the install list:
"undefined": "react-navigation/bottom-tabs"
I tried running an "npm install react-navigation/bottom-tabs" but it threw this error:
warn Package undefined has been ignored because it contains invalid configuration. Reason: Cannot find module 'undefined/package.json'
Has anyone encountered an issue like this before? I am running React-Native Version 5 on top of Expo.
EDIT: It turns out that it was supposed to be #react-navigation/bottom-tabs, so I installed that and made an adjustment; but now I am still stuck with the original undefined package in my app.json folder, and cannot get rid of it.
So, I forgot this post existed and I actually figured this out months ago. When you're dealing with:
A bad bundle,
the wrong version,
or there's just something wrong with your 'package.json' file, (the file that contains the list of your packages)
These steps should fix it:
Perform "npm uninstall 'package-name' " or "yarn remove 'package-name'"
Note: You do this instead of 'expo-uninstall' because 'expo-uninstall' does not exist. We use 'expo-install' instead of 'npm' or 'yarn' install to make sure you download the proper npm or yarn version associated with your version of expo.
Open the package.json file and see if the bad package you uninstalled is still present.
If the bad package is still there, select and delete it from the file, then save.
Run an "expo" "npm" or "yarn" install on the correct package name
This should fix it. This is best fixed when step 4 is executed with an 'expo install' as you likely have an incompatible version of the package, so this will prevent that from happening again.
In my case, I couldn't figure out why my terminal was telling me a specific package didn't exist, so I did a "sud" command to force download the package. This package didn't exist, because I had actually spelled it wrong.
try deleting your node modules and install them again and make sure your metro is closed
clear cache and you are good to go by the way it worked for me
npm install or yarn add
npm start --reset-cache

Aurelia bundle with gulp throws "TypeError: Path must be a string. Received undefined"

I'm using the skeleton-typescript aurelia skeleton-navigation package, when running gulp bundle it gives me an error that says path must be a string but was undefined
TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
at Object.basename (path.js:801:5)
at exports.writeOutputs (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\lib\output.js:137:23)
at C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\lib\builder.js:575:14
at tryCatcher (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\joaoe\Desktop\skeleton-navigation\skeleton-typescript\node_modules\systemjs-builder\node_modules\bluebird\js\release\promise.js:502:31)
All gulp related files can be found here since there are more than one.
Even the cloned package throw that.
I'm running Node 6.0.0 and tested with 5.9.1, on Windows 10.
There is some property that I need set to be that path ? Seems related to Aurelia pre built tasks, from comments could also be an environment problem.
As I tracked it down, the issues seems to be an ugly combination of node-gyp, Windows and node 6
So install all dependencies needed for node-gyp, following your OS steps as seen at official repo. Unfortunately for now if you are running Windows is likely that you need to install Visual Studio. Then run npm install on the repository and see if there is any error, should be no one now. Then try to gulp bundle it should work now. With downgraded node to 5.11 I was able to run again, I did not test with node 6 but feel free to try.

No response when trying to install instrument-control package in octave

I am running raspbian on a Raspberry-Pi 2 B. I am trying to install the instrument-control package in octave 3.6.2.Initially I got a mkoctfile missing error:
Installing octave package in ubuntu http://ubuntuforums.org/showthread.php?t=955385
With 'sudo apt-get install octave-pkg-dev' this problem was solved.
However, when I try to install the instrument-control package in octave with: 'pkg install -forge instrument-control' nothing is happening, the command prompt underscore is just flickering as if it is processing something, but nothing happens for at least half an hour (I didn't try longer). I tried running octave as superuser, but the same thing happened.
I would very much appreciate if someone could help me out on this.
NB This is my first post here, and am not a super-experienced computerist so please tell me if I need to provide more information in any form.
It turned out that it actually takes longer than 30 minutes to compile all the necessary files, so octave is actually doing something. You just have to wait longer. When using -verbose this becomes more clear.
The downloading process might be hanging.
As a workaround, you can download the instrument-control package there.
Put it in your directory on the raspberry.
And then, in octave launched from the same directory, issue
pkg install instrument-control-0.2.1.tar.gz

no mpicxx when compiling examples for NVIDIA CUDA 5

I installed the driver and toolkit for CUDA 5 in 64-bit RHEL 6.3 successfully.
However, when I tried compiling the CUDA 5 examples, I got the error message:
make[1]: Leaving directory `/root/NVIDIA_CUDA-5.0_Samples/0_Simple/cppIntegration'
which: no mpicxx
How can I fix this for the CUDA 5 examples to compile?
In order to build the simpleMPI example, you need some kind of MPI installed on your system. You can get around this and build most of the samples by doing:
make -k
this will attempt to go past errors in the make process and build all targets that can be built.
If you prefer, you can delete this directory:
/root/NVIDIA_CUDA-5.0_Samples/0_Simple/simpleMPI
perhaps with the following command, as root:
rm -Rf /root/NVIDIA_CUDA-5.0_Samples/0_Simple/simpleMPI
and relaunch your make. Personally I think the make -k option is simpler.
(the message about cppIntegration is just the last target that got successfully built)

CPAN error. How can I fix this?

This is driving me crazy- if you can be of assistance, I'd be much obliged. I am running Cygwin on Windows 7.
I have been attempting to write a Perl script to obtain and work with some JSON information. However, my cpan will not install some packages properly. If I try to execute
install CPAN
or
install JSON
It seems to be going well for a while, but then I get an error message over and over again:
0 [main] perl 3288 child_copy: loaded dll data write copy failed, 0x740D1000..0x740D27F0, done 0, windows pid 6600, Win32 error 487
Some people suggested executing ash from the DOS command prompt, and using rebaseall. I tried this, and dash, to no avail. The install still hangs, and when I start up cpan it displays
There seems to be running another CPAN process (pid 3764). Contacting...
Other job not responding. Shall I overwrite the lockfile '/home/me/.cpan/.lock'? (Y/n) [y] y
I have gcc and as many other possible dependencies installed as many online have suggested in my search for help. If you have any leads, I'd be most obliged. Thank you.
i had issues installing pretty much any cpan module - same 'cant move' error!!
just disabled McAfee and all resolved.
Check and disable your AV.
Re-run the cygwin installer to add the needed packages.