understanding the output of brew doctor #5673
Replies: 1 comment 5 replies
-
What $ echo | gcc -xc -E -v -
[...]
/usr/lib/gcc/x86_64-linux-gnu/11/cc1 -E -quiet -v -imultiarch x86_64-linux-gnu - -mtune=generic -march=x86-64 -fasynchronous-unwind-tables -fstack-protector-strong -Wformat -Wformat-security -fstack-clash-protection -fcf-protection -dumpbase -
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/11/include-fixed"
ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/11/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-linux-gnu/11/include
/usr/local/include
/usr/include/x86_64-linux-gnu
/usr/include
[...] Notice that So, to answer your question: it makes sense for
|
Beta Was this translation helpful? Give feedback.
-
Output of
brew config
Output of
brew doctor
Description of issue
running homebrew on asahi linux here, and using one of the older kernels ie.
6.6.x6.9.x so i get zfs support going on this box for various backup reasons. homebrew seems to work reasonable well on this setup, but something i am noticing and have noticed in the past is the warnings withbrew doctor
output.for this particular homebrew setup i have homebrew setup in the below dir.
output
does it make sense for
brew doctor
to warn about files in/usr/local
when that isn't even my prefix for my homebrew installation?Beta Was this translation helpful? Give feedback.
All reactions