aboutsummaryrefslogtreecommitdiff
path: root/reproduce/software/bash/bashrc.sh
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2020-01-31 20:29:02 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-01-31 20:29:02 +0100
commit50832921ab5eac62350855955d3af3f6f0766bbf (patch)
tree73d1814e25d91739bae54ee837d5928466a40b66 /reproduce/software/bash/bashrc.sh
parentf37005b729065f0e4ff6bfa99e5410ebb210cd60 (diff)
Architecture-specific C headers on Debian-based OSs now accounted
Rencely the building of GCC was allowed on Debian-based systems that have their basic C library in architecture-specific directories, like `/usr/lib/x86_64-linux-gnu'. However, these systems also have their headers in non-standard locations, for example `/usr/include/x86_64-linux-gnu' and this caused a crash on a new Ubuntu system. /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory 27 | #include <bits/libc-header-start.h> | ^~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. The reason it didn't cause problems on other Ubuntus that we tested before was historic: In the old days, we would ask Ubuntu systems to install multilib features to have GCC. Because they had installed those features, this problem didn't show up! But this wasn't mandatory! With this commit, the `CPATH' environment variable is set (similar to how `LIBRARY_PATH' was set) and this fixed the problem on a clean Debian virtual machine. This bug was reported by Sebastian Luna Valero.
Diffstat (limited to 'reproduce/software/bash/bashrc.sh')
0 files changed, 0 insertions, 0 deletions