On 10/04/2013 07:43 PM, Paul Davey wrote:
Related to this discussion, it seems that gcc4 on a gcc2h system still searches /boot/system/develop/headers as a header search dir, is this intended or simply an oversight? If it is intended then merging common into system will mean gcc4 will see gcc2 library headers in headers.
Yes, this is intended. As you may have seen, the directory is listed after /boot/system/develop/headers/x86. This way, if you have installed gcc4 specific headers, those will be found first. If you have not installed them, then you haven't installed the gcc4 devel package for that library and linking will fail, since the library search paths are puristic.
The reason for including /boot/system/develop/headers is that often headers aren't architecture (and even less: compiler) specific. So, if they aren't, one can simply include them only in the devel package for the primary architecture (or in a separate package required by both primary and secondary devel package). That's how it's done for haiku_devel.
CU, Ingo
