Can't run GO script anywhere but imagick-master - go

Trying to use the https://github.com/gographics/imagick magickwand library to identify original file types (ex:png to jpeg I want to know it was a png)
If I try to run the script from the local directory I get the error on the rightside terminal
undefined reference to `mingw_initltsdrot_force' collect2.exe: error: ld returned 1 exit status (exit status 2)
although if I run it from c:\imagick-master, I get the expected result which is the script actually running as shown on the left terminal (I know theres an error on the left "correct" terminal but I can fix that) https://imgur.com/a/oxdS1A4
I figured because of the directory playing a part in running or not, including on vscode, that it was a path issue, so I added C:\imagick-master to my path and I'm still getting the error.
I could do all my coding within the C:\imagick-master directory to have it run, but this is not sustainable as I can not use VScode this way plus it seems a little bit too bad practice to always run in that directory and not the local scripts directory
Ive included photos to the errors I'm getting, the left terminal is exactly what I expect and hope to recieve but the issue is I cant run it in the local directory which is where vscode will run from, making me unable to use an IDE. Have not been able to find anyone with the same error..

Related

Windows 10 golang setup. Error, Not in an environment

I am running into issues setting up go for the first time on a Windows 10 machine.
I followed the instructions from the install. https://golang.org/doc/install?download=go1.10.windows-386.msi
When I CD to my project E:\goProjects\goWebApp\src and run go build, I receive the following error.
C:\windows\system32>go version
Not in an environment
C:\Users\MyUser~1\AppData\Local\Temp\go_there.bat' is not recognized as an internal or external command,
operable program or batch file.
My system variables are as follows:
GOPATH=E:\goProjects\goWebApp
GOROOT=C:\Go
PATH=C:\Go\bin
If I run go version from C:\Go\bin everything works fine. Running go command from anywhere outside of this directory does not work. I have also tried restarting my cmd prompt and restarting my computer. Still no luck. Has anyone else ran into this issue? Or know what I might have done wrong?
Turns out I had two go locations in my PATH (sort of). When I ran the command where go from command prompt two paths were returned.
Something like this..
C:\tools\devTools\bin
C:\Go\bin\go.exe
There apparently was a bat file in devTools\bin called go.bat. This was unrelated to golang itself, just coincidental naming unfortunately.This was executing instead of the go binary, which in return was throwing the random error with the Not in an environment message.
To fix the issue I just removed the devTools path from my PATH variable for now.

XCode 7 Otool failing to copy file during build

[OSX 10.10.5, XCode 7.0.1]
I'm getting an error during my build stating that Otool can't copy a file:
error: otool: can't open file: /usr/local/opt/llvm/lib/libclang.3.6.dylib: (No such file or directory)
The two lines before the error (and what I think is causing it, because there are no other error indications) are:
cp -p /usr/local/opt/llvm/lib/libclang.3.6.dylib /Users/me/Library/Developer/Xcode/DerivedData/MiCASE-asvgjysohljplretlamgcpgnxgiq/Build/Products/Debug/MiCASE.app/Contents/Frameworks
cp -p /usr/local/opt/llvm/lib/libclang.3.6.dylib: /Users/me/Library/Developer/Xcode/DerivedData/MiCASE-asvgjysohljplretlamgcpgnxgiq/Build/Products/Debug/MiCASE.app/Contents/Frameworks
When I manually perform the command in a terminal, it works fine. I've set the permissions of the dynamic library to me:admin 777, so the file definitely exists. Thus I don't understand why I am getting the error.
This leads me to believe there is something else that is failing but the build log isn't showing it.
I'm also getting this error at the end of the script, but I think it's due to the above:
Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure
Solution
#trojanfoe, thanks for the info.
The problem was that as part of the build, a script was being run. In the script otool was being used to extract dependencies, and filtering of its output was done incorrectly. Fixing the filtering resolved the issue.

Need some help creating an audiosprite through cygwin/node.js on Windows 7

I'm trying to make an audiosprite, but somehow I'm overlooking some basic thing somewhere, and I can't for the life of me find out what it is, googling around on the error I'm getting gets me 100's of unrelated results, so I'm sorta hoping somebody here can help me along.
I'm running on 64bit Windows 7 Pro, I've just installed the latest Cygwin (1.7.32) and Node.JS (0.10.32) for 64bit half an hour ago, and now I'm trying to actually use them, but I'm running into issues.
At first I thought (hoped) a simple restart would resolve things, but sadly it doesn't, I've also checked the PATH variable, and it has npm listed, so that's not it either.
here's what I'm doing, and getting:
olivier#MV-VFX-01 ~
$ cd audiosprite-stuff/
olivier#MV-VFX-01 ~/audiosprite-stuff
$ audiosprite *.mp3
cygwin warning:
MS-DOS style path detected: C:\Users\olivier\AppData\Roaming\npm/node
Preferred POSIX equivalent is: /cygdrive/c/Users/olivier/AppData/Roaming/npm/node
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)
olivier#MV-VFX-01 ~/audiosprite-stuff
$
So first I'm browsing to a directory (inside home/olivier) that has the mp3's I want to bake an audiosprite with.
After that I simply try the most basic possible audiosprite cmd, that should create an audiosprite from all mp3's in the current directory.
Overlooking the warning (least of my worries atm, and I can always fix that later) the return message from audiosprite is
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1001:11)
at Process.ChildProcess._handle.onexit (child_process.js:792:34)
The issue is that I really don't know what to make of the above, like I said when I googled on (parts of) the error, I got completely random results, none related to audiosprite, and the ones that did relate to Cygwin had fixes for specific pieces of code, but not a general fix, which is kind of what I'm needing.
Does anybody have any clue what I'm missing here? do I need to add more stuff to my PATH variable perhaps? (at the moment it only mentions npm in the PATH variable, nothing else)
I've already tried some obvious things like running cygwin as administrator and even tried using 'command prompt' instead of cygwin, and while it does support all the cmds, I get the exact same errors there.
Actually, im just incredibly stupid..
I forgot to install FFMPEG, so ofc it couldnt make an audiosprite, durrrrr.
Resolved :)

Highlight errors in Terminal

I had a problem with Terminal a Jekyll install but I didn't spot the site being not-uploaded to the server by rsync because I didn't see an error in the output. So, I was wandering:
Is there any way to make Terminal detect errors and give them a specific color?
My error here was:
rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [sender=2.6.9]
It had other things, but if this line was highlighted, I would have spotted it way earlier.
Generally speaking, color output is a responsibility of a program and not a terminal.
For example, clang compiler produces colorful error and warning messages.
If the application you are using does not support this, the only option is to create a wrapper and parse its output, highlighting errors in different color. This approach is taken by colorgcc, for instance, to make GCC compiler output in colors.
Perhaps you can grab that script and adjust it for your needs? Check it out here - https://github.com/colorgcc/colorgcc
Also, if there are errors, the app should probably exit with non-zero exit code. It might be a good idea to check it and write an even bigger and noticeable message upon exit in case of errors.
Hope it helps.
Good luck!
You can enable highlighting of errors for one command with the hilite utility. It only works for commands you type hilite for – it isn’t enabled globally – but it’s still useful if you know or suspect that a command outputs errors and you want to locate them. So when you build with jekyll, you could do any of the following:
Change jekyll … to hilite jekyll … in your build script
Try to remember to always type hilite before jekyll
Run jekyll normally, but if its output or exit code makes you suspect you got errors, run it again with hilite to locate them
On OS X, you can install hilite with Homebrew using brew install hilite.

Trying compiling in minix3

I'm using minix3 on VMware Player and i'm having trouble compiling a system call.
I actually tried to see if i can add a simple command in a system call just to see that working and i put a simple printf("my message"); in protect.c file which it is on usr/src/servers/vfs.
I saved it, and tried to compile it with make command while i am on vfs directory.
It says that protect.c is up to date.
I try change a file's owner (protect.c has the chown mode code in it) and i'm waiting as a result my message. Instead it's just run the command correctly without printing my message.
I assume that i did something wrong with compiling and i'm searching for hours over the internet trying to fix it. But the only command that cames repeatedly is make hdboot. I know that this command it's not gonna work because i'm using minix3 as a virtual OS, but i tried it just to confirmed it and as i said didn't work.
Is anyone know anything about compiling in minix3?
IF your problem is indeed with compilation and you've implemented your system call correctly then after making any edits in /usr/src you should call "make install" from /usr/src/releasetools and then call "reboot" to restart minix

Resources