2011/8/21 Dagobert Michelsen <[email protected]>:
> Where does it look for the file? You can try truss or opensnoop to find
> if gcc looks at the wrong location.
Looking at the truss output, gcc tries to locate the header in wrong places:
22203:
stat64("/opt/csw/lib/gcc/sparc-sun-solaris2.10/4.6.1/include/iosfwd.gch",
0xFFBFF038) Err#2 ENOENT
22203: open64("/opt/csw/lib/gcc/sparc-sun-solaris2.10/4.6.1/include/iosfwd",
O_RDONLY|O_NOCTTY) Err#2 ENOENT
22203: stat64("/opt/csw/gcc4/include/iosfwd.gch", 0xFFBFF038) Err#2 ENOENT
22203: open64("/opt/csw/gcc4/include/iosfwd", O_RDONLY|O_NOCTTY) Err#2 ENOENT
22203:
stat64("/opt/csw/lib/gcc/sparc-sun-solaris2.10/4.6.1/include-fixed/iosfwd.gch",
0xFFBFF038) Err#2 ENOENT
22203:
open64("/opt/csw/lib/gcc/sparc-sun-solaris2.10/4.6.1/include-fixed/iosfwd",
O_RDONLY|O_NOCTTY) Err#2 ENOENT
22203: stat64("/usr/include/iosfwd.gch", 0xFFBFF038) Err#2 ENOENT
22203: open64("/usr/include/iosfwd", O_RDONLY|O_NOCTTY) Err#2 ENOENT
My theory is that gcc was confused by the explicit --includedir setting.
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.
