Paolo Bonzini replied: > > If using "cc -D__EXTENSIONS__ -I/opt/csw/include" does not work on Solaris, > > but "cc -D__EXTENSIONS__" works, there is no need for gnulib to support > > "cc -D__EXTENSIONS__ -I/opt/csw/include". > > What if the package depends on something else in /opt/csw/include?
Where would be getting if gnulib would have to include workarounds for every non-standard add-on package on the world? gnulib has enough to do, working around the vendor bugs in /usr/include. The difference between /usr/include and /opt/csw/include is that the latter is maintained by an active group of developers and it does not take a major OS release for them to publish their fixes. Therefore it makes sense if they fix the bugs in their software, rather than having gnulib work around it. Like the Haiku and MiNT communities, for which gnulib does not provide workarounds either. If a package depends on something else in /opt/csw/include, it can just install what it needs, but not install the broken <getopt.h>. That contents is structured in the form of packages, see http://www.opencsw.org/packages Bruno
