Closed Daoenti closed 3 years ago
TL;DR
Try with the following command instead. (--with-libyaml
added)
brew install --HEAD universal-ctags/universal-ctags/universal-ctags --with-libyaml
Details
I saw a line indicating libyaml
is an optional dependency.
https://github.com/universal-ctags/homebrew-universal-ctags/blob/841bdf137939c293c0a26a068c0bbc0e5be3fc1a/universal-ctags.rb#L11
Optional dependencies are disabled by default.
When you want to enable them, libyaml
for example, you need respective options like --with-libyaml
.
brew info
will show you the list of such options.
I'll close this issue then. I was under the impression that optional dependencies would be enabled if the dependency was already present, I didn't realize that additional steps had to be taken. As a note though, it would be nice if this was mentioned in the README.md somewhere.
I installed the homebrew package using the tap as documented on this page:
brew install --HEAD universal-ctags/universal-ctags/universal-ctags
I am running MacOS Big Sur, however that upgrade was VERY recently (about two hours ago) and this was also ran earlier today on Catalina with the same results. FYI, usernames have been obfuscated to protect the innocent.
After completing the install above it does not have support for languages requiring libyaml.
As one of the major reasons I was moving to Universal ctags was AnsiblePlaybook support I was a little stumped by this. I do have libyaml installed via brew:
Verbose build log through brew:
To troubleshoot I downloaded universal ctags straight from the github at
https://github.com/universal-ctags/ctags
and ran the following to build and install it:This left me with a version of universal ctags that works completely normally and has libyaml support as can see by the inclusion of AnsiblePlaybook:
Full output of hand build:
The major thing I can see between the verbose output of both builds is:
checking for yaml-0.1... no
checking for yaml-0.1... yes
Now I've obviously fixed my personal issue by just using my hand compiled version, however I wanted to report it and will happily help troubleshoot the issue. As an aside, languages requiring libxml support are also working fine in the hand compiled version however I did see the issue that had been opened and saw that libxml support is excluded with
option "without-xml"
in the build file.