Building on Haiku generates libstdc++.so and libsupc++.so in system locations?

[stippi]

Building a target on Haiku for target platform "haiku", in the case that system headers are newer than some headers in the tree, seems to generate the C++ libs in system locations:

Link /boot/develop/lib/x86/libstdc++.so 
Link /boot/develop/lib/x86/libsupc++.so 
SetType1 /boot/develop/lib/x86/libsupc++.so 
MimeSet1 /boot/develop/lib/x86/libsupc++.so 
SetVersion1 /boot/develop/lib/x86/libsupc++.so 
Chmod1 /boot/develop/lib/x86/libsupc++.so 
[...]
SetType1 /boot/develop/lib/x86/libstdc++.so 
MimeSet1 /boot/develop/lib/x86/libstdc++.so 
SetVersion1 /boot/develop/lib/x86/libstdc++.so 
Chmod1 /boot/develop/lib/x86/libstdc++.so 

Possibly helpful related information: When I build a fresh installation from Linux to my partition, the clock will be set to Locale time and one hour behind the real time. This will then cause these libs to be generated over and over, and more often than not, they will fail to link, causing the build to stop. That last bit is probably unrelated, but the modification time of the system headers having to do with the problem might be a clue.

[bonefish]

Fixed in hrev35396.