I'd like to remove several packages that I've installed. When I invoke package-list-packages, I notice that there is a 'd' (mark for deletion) command and an 'x' (execute). However, it seems like this simply removes the package name/description from the list and not the actual files under ~/.emacs.d/elpa. What am I doing wrong or missing? Surely there must be some way to remove installed packages.
The command package-menu-mark-delete (key 'd') followed by package-menu-execute (key 'x') worked for me.
Also here is very good introduction: Package management in emacs - The good, the bad and the ugly
I've noticed that all the installed packages end up at the bottom of the list. If a new version of the package you want to uninstall is available, it will occur twice in the *Packages* buffer, once for the new version, listed as available, and a second time, listed as installed, for the old version. Only the version listed as installed can be marked for deletion using d and subsequently removed using x, answering yes to the question in the mini-buffer. That removes the actual files in the elpa directory for me.
It happened on me when the update crack. It ends up with both new and old packages in elpa directory. You can not install or delete in emacs package management. You can just delete the package under elpa directory directly. Then the emacs package works again.
Related
After retagging a git commit I'm no longer able to fetch the package, because SP Manager uses some cache which I can't find and clean. Getting error:
Revision 30c16cab9c718416fee2191ff2ac0b6f91eeb511 for base
remoteSourceControl https://github.com/myUser/myRepo version 1.0.0
does not match previously recorded value
I cleaned all known to me places: local .build folder, SPM caches in Home and Library/Caches folders, DerivedData, removed Package.resolved.
Using Swift 5.7, trying to generate via swift package generate-xcodeproj.
Does anyone know where this cache is?
This one solves the issue for me.
rm -rf ~/Library/Caches/org.swift.swiftpm
rm -rf ~/Library/org.swift.swiftpm
From https://blog.todosobreios.com/solucionar-problemas-de-swift-pacakge-manager-spm/
It depends on whether you're building via Xcode, or directly via swift build.
Xcode keeps its packages in ~/Library/Developer/Xcode/DerivedData/<your project>/SourcePackages/checkouts/.
SPM keeps them in .build/checkouts of the project folder.
In general, you should never change the commit a version tag points to, for precisely the reasons you experienced. The version numbers form the identity of a package version (not a commit hash, hash of the files, or anything like that). All the systems that are made to work with package rely on the notion that equal version number means they're identical. You're invalidating this assumption, and you'll cause bugs all over. Release a new minor version with your fix, instead.
I have clang-format version 3.8.0 (tags/RELEASE_380/final) in my ~/bin folder on a Fedora machine with no root privileges. It works, but it is very old and I'd like to upgrade. I just want the clang-format tool, so I would like to avoid going through the full installation process for LLVM or clang if I can avoid it. I assume I can avoid it, since my old clang-format works without either of those installed. I don't remember how clang-format got in my ~/bin directory, and I can't figure out how to update it.
The first thing I tried was following this post which said I should be able to download a prebuilt binary from this page (I tried http://releases.llvm.org/6.0.0/clang+llvm-6.0.0-x86_64-linux-gnu-Fedora27.tar.xz), then just set up a symlink to bin/clang-format. This did not work for me. When I type /path/to/bin/clang-format --help I get the error error while loading shared libraries: libtinfo.so.6: cannot open shared object file: No such file or directory.
The next thing I tried is downloading the clang source code and compiling that with
mkdir build && cd build && CC=$(which gcc) CXX=$(which g++) cmake ..
but when I did I got the error
CMake Error at CMakeLists.txt:36 (message):
llvm-config not found -- LLVM_CONFIG-NOTFOUND
Which I guess means I'd need to install the LLVM to go this route?
Any help getting an updated clang-format (vesion 5.0 at minimum) without root access would be appreciated. Bonus points for minimal installation (i.e. no clang or llvm).
=== EDIT ===
By downloading a bunch of different versions of prebuilt binaries, I've discovered that older versions (<4.0) have clang-formats that work out of the box, but at 4.0 and up give the same error about libtinfo. I guess that means I'll have to live with older versions unless I want to go through a painful installation process.
When you download llvm 6.0, make sure the directory structure is as follows:
llvm
|-->tools
|----->clang
|----> tools
|----> extra
If you just want to build clang-format, then you can cd into
llvm-build-dir/tools/clang/tools/extra/clang-format and then execute make -j8 all
later you can make a symbolic link in your /bin folder
I'm trying to use libffi in one of my projects, but I can't seem to compile for iOS (or macOS, for that matter). Here is one of the various errors I've encountered while building for the iOS Simulator:
bash: src/arm/gentramp.sh: No such file or directory
Update 1: Since the question remains unanswered, I've decided to open an issue at the official repository as well.
Update 2: Question has been answered and the issue has been closed!
If you check the repository you will see that the file you require was deleted in this commit. You can find the last version of this file here.
generate-darwin-source-and-headers.py and the libffi.xcodeproj need to be updated to include all currently relevant source files.
The gentramp.sh script is not needed anymore and the current upstream xcodeproj is not up to date either with compilation settings and to be included source files for 64-bit on iOS. A patched fork can be found at https://github.com/ksjogo/libffi
sh autogen.sh
python generate-darwin-source-and-headers.py --only-ios
open libffi.xcodeproj
select scheme libffi-iOS and device Generic iOS Device
click "Product - Build"
If success, you would see a "Product/libffi.a" in the side bar, you can right click it to get the lib in the finder.
Please make sure you are following the installing libffi instructions released on the TBD or git project: https://github.com/libffi/libffi
Here some of the main Highlights:
First you must configure the distribution for your particular
system. Go to the directory you wish to build libffi in and run the
"configure" program found in the root directory of the libffi source
distribution.
If you're building libffi directly from version control, configure won't
exist yet; run ./autogen.sh first.
You may want to tell configure where to install the libffi library and
header files. To do that, use the --prefix configure switch. Libffi
will install under /usr/local by default.
If you want to enable extra run-time debugging checks use the the
--enable-debug configure switch. This is useful when your program dies
mysteriously while using libffi.
Another useful configure switch is --enable-purify-safety. Using this
will add some extra code which will suppress certain warnings when you
are using Purify with libffi. Only use this switch when using
Purify, as it will slow down the library.
For iOS builds, the 'libffi.xcodeproj' Xcode project is available.
Configure has many other options. Use "configure --help" to see them all.
Once configure has finished, type "make". Note that you must be using
GNU make. You can ftp GNU make from ftp.gnu.org:/pub/gnu/make .
To ensure that libffi is working as advertised, type "make check".
This will require that you have DejaGNU installed.
To install the library and header files, type "make install".
Alternatively, try merging one of the following git projects to your project in order to include the missing files. Please make sure the files are not outdated before merging.
1 https://github.com/pandamonia/libffi-iOS
2 https://github.com/influitive/libffi-iOS
3 https://github.com/landonf/libffi-ios
I downloaded the latest version of CodeKit (trial version 2.0 (16828)). It starts fine on my Mac Mini, but as soon as I try to download a component using Bower, it fails with the error: "Bower Error / Bower could not determine which components are installed in this project. Make sure you're connected to the Internet and try again." Repeated attempts (either clicking "Retry" or clicking "OK" and trying to download the component again) continue to fail.
The app completes the "Downloading Bower component list" without error. The error occurs when it is "Scanning For Installed Components..."
I'm connected to the Internet just fine.
When I try to install a Bower component, it fails with this message:
Why am I getting these errors and how can I fix CodeKit?
Thank you!
Turns out that Bower continued to fail, which prevented CodeKit from working.
Tolga Akyuz's answer to Siddharth's problem was the fix - I had a ~/.cache file which was preventing Bower from adding files to ~/.cache/
When I renamed the ~/.cache file (e.g. to ~/.cache-orig) and created a ~/.cache/ directory, Bower began working properly - and so did CodeKit.
It turns out that this behavior can be caused by several things. Another user fixed it and shared this with me:
I installed xcode and still had issues. After a bit of research, I found a post that said installing the command line tools in Xcode might solve the problem. I did that and the problem is now solved.
From what I can see, there is a appears to be an issue with the $PATH getting messed up with systems that have been upgraded from Lion (and Snow Leopard) that did not ship with git. In the questions and answers listed on the page linked below, there were several terminal command options given, but I was unsure of which to choose so I went with the Xcode route.
https://apple.stackexchange.com/questions/18470/why-is-git-not-found-after-installing-os-x-lion
I had the same issue.
Check console messages (mac)
Delete faulty library. I had one.
Should be all good now.
good luck
If it's still relevant. In my case it was Google Maps AMD Loader Plugin. All fixed after removing it.
In my case the problem was with path to the project folder – it contains "!" symbol that makes bower crazy. To check is it Bower or CodeKit problem try to cd in terminal to your project folder and run "bower list".
zhaba$ bower list
bower EINVALID Name must be lowercase, can contain digits, dots, dashes, "#" or spaces
With corrected project folder path CodeKit works.
I had the same problem running CodeKit2 with El Capitan, and an old version of Xcode. Updating Xcode fixed the problem.
I'm trying to build Firefox from source and I'm getting hung up on some of the requirements.
I'm trying to build libIDL, which requires glib. I got glib built and installed to /usr/local, but when I try and configure libIDL, I get a failure at:
checking for LIBIDL... configure: error: Package requirements (glib-2.0 >= 2.4.0) were not met:
No package 'glib-2.0' found
I used the very latest version of glib that I can find, ftp://ftp.gtk.org/pub/glib/2.20/glib-2.20.3.tar.gz
However, I've also been searching around and am seeing references to libglib-2.0 such as at http://packages.debian.org/search?keywords=libglib2.0-dev
Are there 2 divergent branches of Glib, like a v1 and v2?
You need to install glib-devel in order to have the glib headers exist on your system. Without the headers, autoconf will mark the library as missing.
You installed glib from source which should have worked. The actual problem was most likely with the paths you chose to install into. The autoconf script may not be looking for glib where you installed it, or it may be looking into another directory first and finding an old version.