I am trying to install git-annex using homebrew. After installing brew, when i typed
brew install git-annex
in the commandline, it showed
"git-annex: no bottle available!".
I also want to download datalad, after following the steps on datalad handbook, it appeared the same problem as installing git-annex
brew install datalad
"Error: datalad: no bottle available!"
git-annex and datalad don't have bottles for M1 Macs right now. The following pages will say "Apple Silicon Big Sur" under the section "Bottle (binary package) installation support" when the bottles are added, but at the time of writing, they only have bottles for Intel Big Sur.
https://formulae.brew.sh/formula/git-annex
https://formulae.brew.sh/formula/datalad
Maybe try running brew install --build-from-source git-annex and see if it installs successfully on your machine.
As of now (and some time already), there are bottles for both git-annex and datalad for Big Sur on M1.
See:
https://formulae.brew.sh/formula/git-annex
https://formulae.brew.sh/formula/datalad
Related
Using: MacOS Monterey v12.2, Apple M1 Pro chip.
After installation of homebrew and using it to install miniconda with this command 'brew install --cask miniconda' on the mac terminal, it states that conda is not found.
Yet, if i key the command 'brew list' on mac terminal, miniconda is seen in the casks.
(Q1) How to resolve the above i.e. make miniconda work via this homebrew download method? (Also, it seems like unlike in intel MacOS, miniconda is stored in this directory -> "opt/homebrew/Caskroom/miniconda/base" in M1 MacOS)
(Q2) Alternatively, i downloaded the miniconda installer (from https://docs.conda.io/en/latest/miniconda.html). This miniconda installer works and it seems to reside in a different path -> "/Users/xxxx/opt/miniconda3" (refer to Image 1). Concern that there might be conflict if there are two miniconda in my macOS. So then, how can i remove the miniconda which i downloaded earlier via homebrew? The command 'brew uninstall miniconda' or ''brew uninstall --cask miniconda' did not work? (refer to Image 2)
I kept running into these kinds of problems with python on my M1 Mac until I went completely to Rosetta on the command line wrt python. For that, I did the following:
Update Rosetta:
In a Terminal type:
softwareupdate --install-rosetta
In Finder, type ⇧⌘G and go to /Applications/Utilities. Then duplicate Terminal:
Rename the second Terminal to "Rosetta" (or whatever you like) and have it execute in Rosetta by checking "Open using Rosetta" in the "Get Info" dialogue:
Open a Rosetta Terminal and make sure it shows i386 when you issue the command arch:
In that terminal, install homebrew (per the homebrew homepage):
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
Once homebrew has been installed, install miniconda using homebrew:
brew install --cask miniconda
Create a conda environment, for instance here a python 3.9 env named py39:
conda create -n py39 python=3.9
Activate the environment:
conda activate py39
From here on out, you have a fully functioning i386 Python system. This has resolved all problems that I had with Numpy, Pandas, Azure, etc. on my M1 Mac.
I just got a new Macbook and did the migration from my old one. It looks like the homebrew executables have a bad CPU type and don't work. Things are a bit stuck right now and I'm not sure how to move forward.
Even my ls is mapped to lsd and I can't list files.
Do I have to manually uninstall brew and related executables by deletion and start over?
DISCLAIMER: I didn't test this myself.
If you don't want to alwasy use Rosetta2, you have to manually remove the Intel version of Homebrew, then install the M1 version.
You can save the list of your Intel installed package with:
brew list > myHomebrewPackages.txt
You will then have to reinstall them on the M1 version.
To remove the Intel version, download the uninstall script from the official Homebrew github repository. Make it executable with:
chmod +x uninstall.sh
and run it with:
./uninstall.sh --path=/usr/local
Then install the M1 version with:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
The M1 version of Homebrew will be installed under /opt/homebrew.
I'm trying to install Wine on my Mac via Brew. I'm using Catalina and just updated brew, installed XQuartz and have Xcode installed. When I type the command "Brew install wine" it returns the following:
Error: No available formula with the name "wine"
==> Searching for a previously deleted formula (in the last month)...
Warning: homebrew/core is shallow clone. To get complete history run:
git -C "$(brew --repo homebrew/core)" fetch --unshallow
wine was deleted from homebrew/core in commit 82bd38bc:
wine: delete
To show the formula before removal run:
git -C "$(brew --repo homebrew/core)" show 82bd38bc^:Formula/wine.rb
If you still use this formula consider creating your own tap:
https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
I'm following this tutorial: https://www.davidbaumgold.com/tutorials/wine-mac/
When I run Brew doctor I get the following:
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7-config
/Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7m-config
/Library/Frameworks/Python.framework/Versions/3.7/bin/python3-config
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected dylibs:
/usr/local/lib/libtcl8.6.dylib
/usr/local/lib/libtk8.6.dylib
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/fakemysql.h
/usr/local/include/fakepq.h
/usr/local/include/fakesql.h
/usr/local/include/itcl.h
/usr/local/include/itcl2TclOO.h
/usr/local/include/itclDecls.h
/usr/local/include/itclInt.h
/usr/local/include/itclIntDecls.h
/usr/local/include/itclMigrate2TclCore.h
/usr/local/include/itclTclIntStubsFcn.h
/usr/local/include/mysqlStubs.h
/usr/local/include/odbcStubs.h
/usr/local/include/pqStubs.h
/usr/local/include/tcl.h
/usr/local/include/tclDecls.h
/usr/local/include/tclOO.h
/usr/local/include/tclOODecls.h
/usr/local/include/tclPlatDecls.h
/usr/local/include/tclThread.h
/usr/local/include/tclTomMath.h
/usr/local/include/tclTomMathDecls.h
/usr/local/include/tdbc.h
/usr/local/include/tdbcDecls.h
/usr/local/include/tdbcInt.h
/usr/local/include/tk.h
/usr/local/include/tkDecls.h
/usr/local/include/tkPlatDecls.h
Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected .pc files:
/usr/local/lib/pkgconfig/tcl.pc
/usr/local/lib/pkgconfig/tk.pc
Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected static libraries:
/usr/local/lib/libtclstub8.6.a
/usr/local/lib/libtkstub8.6.a
I'm not sure these warnings has something to do with it.
Thanks in advance!
I was able to build Wine 64 bit from source on macOS Catalina and successfully run Notepad++ 64 bit on it.
My steps were more or less something like that:
Download Wine 4.20 from https://dl.winehq.org/wine/source/4.x/wine-4.20.tar.xz
Extract it
In terminal go to extracted directory
Run: ./configure --enable-win64
It showed that it cannot find some library (I do not remember what exactly) so I installed it with macports (sudo port install name_of_missing_package reported by ./configure)
After I was able to run ./configure --enable-win64 succesfully without errors in terminal run: make
It compiled after more than 30 minutes.
I run it with: ./wine start
It opened windows console and here I was able to cd to Notepad++ 64 bit directory (downloaded from https://notepad-plus-plus.org/repository/7.x/7.0/npp.7.bin.x64.zip note that newest version did not work and throwed some errors about some dll's)
I typed notepad++ to run exe file
It showed some errors about freetype fonts so I installed them with macports and I had to copy them from /opt/X11/lib to /usr/local/lib before wine detected them
After fixing freetype fonts problem I was able to run notepad++
Also you might want to run: sudo spctl --master-disable to disable gatekeeper if you will see some system alerts about loading app from unknown developer.
Also note that instead of ./wine start you can run ./wine explorer for graphical file manager instead of console
Those steps might not be exactly precise, as I'm not sure if I did not miss something but hope it will help someone.
Also note that obviously wine on macOS Catalina will be able to run only some 64 bit windows apps and all 32 bit windows app will not work. I also tested it with IrfanView 64 bit (https://www.fosshub.com/IrfanView.html?dwl=iview453_x64_setup.exe) and it also works fine.
In case you wanted to get wine working for purpose of running 32 bit games then unfortunately it will not work with wine but you can try with virtualbox. You can check https://www.youtube.com/watch?v=3AO8dF0vviQ for some performance improvements tips.
Wine hast been removed from homebrew due to the incompatibility to Macos Catalina
https://discourse.brew.sh/t/issue-with-wine/6188/3
Try using wine64 to run your .exe files after installing wine. The manuals and references don't seem to mention this explicitly.
More Info
I followed the guidance in the wine manual to install using home-brew. After install, I got an error when trying to test the installation like it says in the quickstart.
Install wine-stable using homebrew
brew tap homebrew/cask-versions
brew install --cask --no-quarantine wine-stable
After install, test by opening notepad
wine notepad
zsh: bad CPU type in executable: wine
While uninstalling wine, I noticed one of the linked libraries was called wine64. I immediately reinstalled and tried again using wine64 as the call, as I am using wine on an M1 Mac. This was successful!
You can also use winehelp to get access to more commands that will work with 64bit processor.
Based on https://github.com/Homebrew/homebrew-core/pull/46556#issuecomment-559938873 you can do brew cask install wine-stable on newer version of OS X. And works with recent versions of homebrew since the source version was moved :(
How to install wine on Mac OS Catalina with brew
install homebrew with
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
install xquartz to install wine using brew
brew cask install xquartz
install wine using brew
brew install homebrew/cask-versions/wine-devel
run wine and check the version
wine64 --version
As of Wine 5.0 there is no 32bit support on mac in the official version, but you are able to achieve it via the
Unofficial Wineskin Winery
You can download it from github releases here. And then create a Wineskin with WS11WineCX[64/32]bit19.0.[0/1]. All WS11 versions support Catalina. To use it you also need to turn off the no32exec boot argument. You theoretically can do it by typing:
sudo nvram boot-args="no32exec=0"
into the Terminal while you're logged in but it didn't work out for me, so if you'll have the same problem, reboot into the Recovery mode, in the menubar pick Utilities -> Terminal and type just:
nvram boot-args="no32exec=0"
(without sudo).
Example
To be more exact, to install eg. Steam 32bit, you would:
Install the Unofficiall Wineskin Winery from the provided link
Turn on the 32bit execution boot argument by going into Recovery Mode and entering nvram boot-args="no32exec=0" into the terminal
Open Wineskin, click the '+' sign and scroll down to find the WS11WineCX64bit19.0.1 (the newest version with 64 and 32 bit support, at the time of writing)
Click update/install under the Wrapper Version.
Click Create New Blank Wrapper, name it and click through installation of mono and gecko.
Launch the Wrapper App from Finder. Click Install Software, choose setup executable, and proceed through installation. Then pick the executable from a menu. (In case of steam, Steam.exe)
Note: If you get the "No windows app to open the file"(Like I did) error, click advanced -> configuration and set the Windows EXE to the path to the installer. Then find the place that it has installed in and set that as Windows EXE. Then you can run by clicking Test Run.
Enjoy your windows app, as an .app file!
Hope I helped!
Up until iOS 11, i've been using the idevice** binaries to extract information from iPhones ranging from models 6 to X via idevicediagnostics.exe on Windows OS via idevicediagnostics ioreg AppleARMPMUCharger.
However, with the release of iOS 12, everything stopped working. What once was a lively file (converted to JSON) i get to export from this command is now an empty xml document. Now i do this because of our Company's Business. We extract battery information as insurance, proof, and history that batteries are as good as they can be. Also to track the Battery Serial and SOH Value while at it.
I've downloaded several updated idevice** binaries and even updated iTunes and Apple drivers but as i'd expect, its broken now. Now, i am looking for alternative ways to do this, are there any other API out there that can do the same job as AppleARMPMUCharger once did? I'm thinking of working on a small iOS Application that will export the data from within the iPhone itself and send it to an FTP or REST API maybe? However, i do not know which registry or namespace to hook it up to.
It's worth noting that CoconutBattery - a MacOS Application that also reads battery information from iPhone still works as expected. Leaving me wonder, how they do it, or what API they are looking at.
Looking for positive responses, cheers.
PS: links routes to the actual files exported when the command is ran.
I had one similar problem which was solved finally by reinstalling the libmobiledevice. I found the instructions from this Github issue. I am posting those instructions here as well for convenience.
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies ideviceinstaller
brew uninstall --ignore-dependencies usbmuxd
sudo rm /var/db/lockdown/*
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install --HEAD ideviceinstaller
If you do not have brew installed in your machine, please follow the instruction from this website.
Hence, finally, the reinstallation of libmobiledevice solved the problem.
Can you try to get information using the AppleSmartBattery key instead? See libimobiledevice#823
I am unable to install apg via homebrew in OSX. I tried brew install apg but I got No available formula with the name "apg".
Tried looking around but no success so far.
The apg formula for homebrew has been removed because the upstream software doesn't seem to be maintained anymore. The home page of the apg software is not reachable and even on other OS, like Debian, the package will probably be discontinued soon (see the notice at the bottom of the description). That's the reason why a brew install apg is not working for you.
That being said, if you look closely at the discussion around the removal from homebrew, you'll find that someone is now maintaining an updated formula in its own homebrew tap. You can then install apg by first adding his tap:
brew tap jzaleski/homebrew-jzaleski
brew install apg