I've Googled this a thousand times and I cannot, for the life of me, get VIM to work on my Minix 3. For the record, I am running on a Windows machine with Minix 3 working on Oracle's VM VirtualBox.
I've tried typing,
# pkgin up && pkgin in vim
but I get the error:
pkgin: Can't open database /usr/var/db/pkgin/pkgin.db: unable to open database file: No such file or directory
I then try to do pkgin search git to search for a package, but I get the same error. Could this be some kind of Internet connection issue? I'm incredibly confused.
If you haven't already, download the binary package from here:
ftp://ftp.minix3.org/pub/minix/packages/3.3.0/i386/editors/
Change "i386" to your correct architecture, if different.
As you're probably already familiar, this page tells you how to install binary packages for Minix:
http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages
As far as your "pkgin" errors, here are two possible solutions:
http://osdir.com/ml/minix3/2011-03/msg00244.html
How to install vim into Minix3?
I asked on the Minix 3 Google Groups Forums and they solved my problem. If anyone else has trouble, I'm pasting a response by Lionel:
Switch to http downloads by editing "/usr/pkg/etc/pkgin/repositories.conf" and comment out the line:
ftp://ftp.minix3.org/pub/minix/packages/$osrelease/$arch/All
and add the following:
http://www.minix3.org/pkgsrc/packages/$osrelease/$arch/All
Then do shutdown, boot, pkgin update and then install your desired packages.
Related
How to install tclsh on windows 10 ?
I am not well versed on Linux/Unix packages but there is a check list I am having to follow for a tutorial on how to do ATAK plug-in development on the Android Development Studio.
The prerequisite stepms include installing and/or downloading tclsh.
I understand that tclsh is a shell program. I think it runs Tcl commands. I found this on stack overflow:
How to install packages in Tcl? which is responses to the question, “How to install packages in Tcl?”. Is this the same thing? Is tclsh part of Tcl?
I don't think so because one of the answers to this post is:
“Yes, there are some directories. To list them, execute tclsh ...”
So this post implies that telsh is already on the system.
There are other posts on stackoverflow which mention tclsh but they all in the context of the anser and mentioned in a way that it is part of a soluton such that it is already installed.
How to install tclsh on windows 10 ?
As a result of a question I wrote a little earlier I person was kind enough to write an answer. He suggested installing iisnode to fix a problem where node.js was in the path but docker couldnt find it.. However, on his suggestion I downloaded iisnode for iis 7.x(x64) and proceeded to run it... and with the luck I am having I got the following error..
There was a problem with this Windows Install package. A script required for this install to complete could not be run. Contact your support personnel or package vendor.
I have no idea how to solve this.. any ideas.. I have entered docker for this as I suspect this problem has occured for others when they tried to run a dotnet core SPA project...
Sorry my bad English!
I had this issue while i was working with "Plesk" but maybe my solution works for you or others.
First you should go to "C:\Windows\System32\inetsrv\config".
Make a backup of "applicationHost.config" somewhere.
Then remove every line that contains "iisnode" in that file.
Then try to install "iisnode" again. if it does not work, restart your OS and try again.
If it does not work again, restore your backup and restart your OS and i don't know how you can fix it, Sorry :((
Today I tried to install and start Docker 1.5. It works at the beginning. Then after about 1 hour, I cannot access autofs directories on the host any more. Get error "Too many levels of symbolic links.". And I cannot do unlink and relink autofs directories for some reason. So no way out now.
$ cd /usr/local/packages/
/usr/local/packages/: Too many levels of symbolic links.
Anyone get similar issue?
And I used Docker version 1.3.3 for several months. It works perfectly. So any change after 1.3.3 may causing this issue?
BTW, I cannot find a older version Docker rpm. If you have one, please let me know. Thanks.
I'm a homebrew newbie (broob?). Trying to build ngspice I encounter the error described in the title. Before I get into that though, it turns out I actually don't even really want/need X11 support at the moment. I'm such a newbie I don't even know how to tell brew to leave out X. In the formula I see:
option "with-x", "Build with X support"
But if I build "--without-x" I still see the same error. How do you say "not --with-x"?
OK, on to the compile trouble:
I can see the file is really there in the X11 directories:
$ find /opt/X11/ -name IntrinsicP.h
/opt/X11//include/X11/IntrinsicP.h
But somehow homebrew is not seeing that include path. What the best way to alert brew to the location of this file? I tried:
ln -s /opt/X11/include/X11 /usr/local/include/X11
which works, in the sense that the include problem goes away, but it produces a linker problem:
ld: library not found for -lXaw
Again, I found some Xaw libs in /opt/X11, but I've not sorted out how to educate homebrew enough to actually link to them. ;-(
$ find /opt/X11/ -name "*Xaw*"
/opt/X11//include/X11/Xaw
/opt/X11//include/X11/Xaw/XawImP.h
/opt/X11//include/X11/Xaw/XawInit.h
/opt/X11//include/X11/Xaw3d
/opt/X11//include/X11/Xaw3d/Xaw3dP.h
/opt/X11//include/X11/Xaw3d/XawImP.h
/opt/X11//include/X11/Xaw3d/XawInit.h
/opt/X11//lib/libXaw.6.dylib
/opt/X11//lib/libXaw.7.dylib
/opt/X11//lib/libXaw.8.dylib
/opt/X11//lib/libXaw.dylib
/opt/X11//lib/libXaw3d.8.dylib
/opt/X11//lib/libXaw3d.dylib
/opt/X11//lib/libXaw6.6.dylib
/opt/X11//lib/libXaw6.dylib
/opt/X11//lib/libXaw7.7.dylib
/opt/X11//lib/libXaw7.dylib
/opt/X11//lib/libXaw8.8.dylib
/opt/X11//lib/libXaw8.dylib
/opt/X11//share/doc/libXaw3d
/opt/X11//share/man/man3/Xaw.3
Thanks for any suggestions!
-steve
I could reproduce this. This reflects an inconsistency in ngspice's configure that was not accommodated by the Homebrew formula. ngspice needs --without-x in configure to stop trying to link to X even though it needs --with-x to actually build X support.
This will be fixed once this pull request is accepted.
Homebrew welcomes these kinds of issues at the Github issue tracker; maintainers don't come around here much. Following the troubleshooting advice that brew recommends ("READ THIS: https://github.com/Homebrew/homebrew/wiki/troubleshooting") will make diagnosing problems easier in any venue. :)
I've directly downloaded the tar file from here onto my desktop for Mac OSX (which is what I'm using) and extracted its contents. Now I've read the following instructions on how to set it up, but honestly they're a bit too cryptic for me. I was wondering if anyone could please break down these instructions into simpler, bite size pieces for someone who typically has trouble configuring new things...
I'd truly appreciate any help! Thanks!
Btw, my end goal is to set this up for the Paperclip plugin.
The first step would be to install MacPorts if you don't have it already. Once MacPorts is installed it should be fairly straightforward based on the instructions listed at the link you provided.
sudo port install ImageMagick
For others interested in this topic, I might look into installing homebrew instead of MacPorts.