Основные предупреждения при запуске Brew Doctor
Я побежал brew doctor
и получил несколько предупреждений, которые, я думаю, я знаю, какие действия предпринять, чтобы исправить, но хочу посмотреть, нахожусь ли я на правильном пути. Вот список предупреждений, которые я получил:
Warning: /usr/local/lib/pkgconfig isn't writable.
This can happen if you "sudo make install" software that isn't managed by
by Homebrew. If a formula tries to write a file to this directory, the
install will fail during the link step.
You should probably `chown` /usr/local/lib/pkgconfig
Warning: Some directories in /usr/local/share/man aren't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew. If a brew tries to add locale information to one of these
directories, then the install will fail during the link step.
You should probably `chown` them:
/usr/local/share/man/mann
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 .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
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
libyaml
Для первого случая, я должен бежать chown <user>/usr/local/lib/pkgconfig
Warning: /usr/local/lib/pkgconfig isn't writable.
This can happen if you "sudo make install" software that isn't managed by
by Homebrew. If a formula tries to write a file to this directory, the
install will fail during the link step.
You should probably `chown` /usr/local/lib/pkgconfig
затем chown <user>/usr/local/share/man/mann
для следующего сообщения
Warning: Some directories in /usr/local/share/man aren't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew. If a brew tries to add locale information to one of these
directories, then the install will fail during the link step.
You should probably `chown` them:
/usr/local/share/man/mann
Не уверен, что делать для этих предупреждений об удалении файлов. (???)
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 .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
Наконец запустить brew link libyaml
?
Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
libyaml
2 ответа
Чтобы исправить проблемы с разрешениями, вы можете chown -R your_username /usr/local
рекурсивно изменить владельца всего в /usr/local.
Вам следует brew link libyaml
,
Предупреждения о dylibs говорят о том, что у вас есть библиотека Tcl/Tk, установленная в /usr/local. Если вы знаете, как он туда попал, и знаете, что он вам не нужен, вы можете удалить его. Если вы не знаете, как он туда попал, вы можете переименовать его файлы, чтобы сборки не забрали его (и вы можете вернуть их обратно, если обнаружите, что что-то от них зависит). Вероятно, хорошо оставить его на месте, если и до тех пор, пока что-то не сломается в связи с Tk; возможно, это никогда не доставит вам неприятностей.
Я решил проблему, запустив sudo chown <user>/usr/local/lib/pkgconfig
, sudo chown <user>/usr/local/share/man/mann
,
Затем я удалил рекомендованные файлы и запустил brew link libyaml
и все было хорошо.