Replies: 3 comments 1 reply
-
Can you share the output of |
Beta Was this translation helpful? Give feedback.
-
Here it is...
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the clarification of my first question. The user account I've been using is very old, probably since 19.x and upgraded to currently 20.10, with many things loaded and unloaded (via .bashrc). And I've noticed this rather odd experience of things won't compile because they can't find the right libraries. (I've been commenting out Brew lines in .bashrc temporarily to get a compile). I thought I'd try the other way round and I created a brand new user account with only Brew additionally loaded, and behold the compile problem goes away.
I'd also removed "/home/linuxbrew/" as well and reinstalled. |
Beta Was this translation helpful? Give feedback.
-
Hello
I seem to get a problem if I try Brew on my Ubuntu 20.10 desktop...
After install, and when I run brew doctor, I get references to
Unexpected '.pc' files and Unexpected static libraries, which references to /usr/local/lib/
Most likely source stuff I've downloaded from the Internet and compiled myself, but I don't recognise any of the filenames.
(possibly before I installed Brew)
Also,
If I download a something.tar.gz from the Internet and try to run ./configure, I usually find that this package can't find dependency libraries that are correctly installed by apt-get and are already on my pc. If I look and the ./configure output, I can see the configure process was looking at a library path modified by Brew
I must be using Brew incorrectly.
Can someone explain...
Should I make a separate account on my pc, without Brew, just for the purpose of compiling Internet stuff?
Beta Was this translation helpful? Give feedback.
All reactions