From 4d76adee11c3c1efefc1a3f025e8dedb890872d4 Mon Sep 17 00:00:00 2001
From: David Hendriks <davidhendriks93@gmail.com>
Date: Wed, 13 Jan 2021 21:58:02 +0000
Subject: [PATCH] updated readme

---
 README.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index ef75d4e7e..5eecc43d4 100644
--- a/README.md
+++ b/README.md
@@ -52,11 +52,17 @@ See examples/ dir for some working examples
 
 When you try to `import binary_c_python_api` and python complains about it not existing, but you are sure that you correctly included the necessary pythonpaths, then you probably need to rebuild the package.
 
-
-
 FAQ:
 --------------------
 
+Building issues with binary_c itself: 
+- see the documentation of binary_c (in doc/). 
+- If you have MESA installed, make sure that the `$MESASDK_ROOT/bin/mesasdk_init.sh` is not sourced. It comes with its own version of some programs, and those can interfere with installing.  
+
+Pip install failed:
+- Run the installation with `-v` and/or `--log <logfile>` to get some more info
+- If gcc throws errors like `gcc: error: unrecognized command line option ‘-ftz’; did you mean ‘-flto’?`, this might be due to that the python on that system was built with a different compiler. It then passes the python3.6-config --cflags to the binarycpython installation, which, if done with gcc, will not work. Try a different python3.6. I suggest using `pyenv` to manage python versions. 
+
+
 
-pip install failed:
 if pip installation results in `No files/directories in /tmp/pip-1ckzg0p9-build/pip-egg-info (from PKG-INFO)`, try running it verbose (`-v`) to see what is actually going wrong. 
-- 
GitLab