I tried running pod install and this is what I received.
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html
[IMPORTANT]
Don't forget to include the Crash Report log file under
DiagnosticReports directory in bug reports.
zsh: abort pod install
(base) tazar#Tazs-Air ios % [NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html
[IMPORTANT]
Don't forget to include the Crash Report log file under
DiagnosticReports directory in bug reports.
. What am I doing wrong? Id really appreciate the help.
Related
We have been getting an error in exporting an archive since the release of Xcode 13.2.1, and are also seeing it in 13.3. (13.1 works great)
The error is:
Reached end of file while looking for: Mach-O slice.
I get this when exporting on our jenkins/fastlane server as well on my development machine.
Curious if anyone has found a solution for this?
It can be an internal issue with malformed library files, try to reload it.
You can try: export_xcargs: "-allowProvisioningUpdates"
I have downloaded and installed a Windows native compiled OpenFOAM from here. But when I try to run any of the OF commands (e.g., blockMesh, foamDictionary, ...) in the MSYS2 terminal I get the message:
path/to/folder/v2106/msys64/home/ofuser/OpenFOAM/OpenFOAM-v2106/platforms/win64MingwDPInt32Opt/bin/blockMesh.exe: error while loading shared libraries: libstdc++-6.dll: cannot open shared object file: No such file or directory
and in the cmd terminal, I get the error message:
System Error The code execution cannot proceed because msmpi.dll was not found. Reinstalling the program may fix this problem.
From here, I see that I might have to reinstall OpenFOAM in admin mode, which I don't have on this work machine. so I tried installing MSMPI using pacman -S msmpi as I used to do here. But I get the error message:
error: target not found: msmpi
My goal is to install and use the OpenFOAM software, doesn't matter which release, on this Windows machine without admin privileges. I would appreciate it if you could help me know how can I fix the above problems, or find another way around.
P.S.1. Searching the installation directory, I see that the libstdc++-6.dll file is in the path\to\folder\v2106\msys64\home\ofuser\OpenFOAM\OpenFOAM-v2106\platforms\win64MingwDPInt32Opt\bin. So I wonder I get the first error message. Maybe OF is not compiled properly against the library? Should I try removing the path\to\folder\v2106\msys64\usr\lib\gcc\x86_64-pc-msys\7.4.0\libstdc++.dll.a as suggested here?
P.S.2. I had written this post ages ago about different ways to install OpenFOAM on Windows. Sadly it is still a big effort to get it up and running.
P.S.3. A follow-up on this issue here on the MSYS2 Discord server.
P.S.4. Opened a new issue here on the OpenFOAM repository.
With OpenFOAM-v2112 it is now possible to install without windows admin permissions.
The original problem will still be evident with older OpenFOAM versions since they relied on installing msmpi separately.
Keep seeing this error log from the terminal when pushing to git repo lately. I think it is due to fact that I updated to Xcode 9.2 or macOS High Sierra.
2017-11-29 07:49:30.580 xcodebuild[1558:49212] [MT] DVTPlugInManager: Required plug-in compatibility UUID C3998872.. for KSImageNamed.ideplugin (com.ksuther.KSImageNamed) not present
Any idea what it means and how to resolve this?
It sounds like you have an old Xcode plugin installed. I had this same error and I found the old plugin located in
~/Library/Developer/Xcode/Plug-ins/
The file name was KSImageNamed.ideplugin
I'd recommend deleting the file.
Problem
Hi, whenever I try to install an extension in VSCode the installation is canceled without any error message showing up.
Before installation
During Installation
VSCode jumps back into this state
Question
How can I figure out any details about what the problem is? Is there some hidden error log or anything?
A Wild Guess
Im currently on a machine where my administration rights or the proxy configuration may be insufficient. This may be the cause of the problem. Installing an extension manually into the VSCode installation folder, worked.
Solution: Installation via Command Line
Installing extensions using the terminal gives at least some error message:
C:\some\path>code --install-extension some-publisher.some-extension
Found 'msjsdiag.debugger-for-chrome' in the marketplace.
Installing...
Error: socket hang up
at TLSSocket.onHangUp (_tls_wrap.js:1117:19)
...
Finding out some-publisher.some-extension
The publisher and extension can easily be copied from the extension details:
I just installed LLVM (3.0) successfully, and got the Hackage bindings (3.0.0.0). However when I try to use it, I get the following linker error:
Loading package llvm-base-3.0.0.0 ... can't load .so/.DLL for: (dlopen(lib.dylib, 9): image not found)
There is no name after "for: ", which makes this frustrating, because I don't know what it can't find. I know there isn't much information to go on, but does anyone have any idea why this could be happening?
I am running Mac OS X, in case it matters.
It's a bug in the llvm bindings installer. I had it patched locally and just sent a pull request to bos, hopefully it will get merged soon.
To fix your problem without the patch, find the llvm-base package config file. Mine is located here:
~/.ghc/x86_64-darwin-7.4.1/package.conf.d/llvm-base-3.0.0.0-*.conf
Locate this line and delete it:
extra-ghci-libraries: ""
Then run: ghc-pkg recache --user