What's the big deal about fixing illumos? Please, if at all possible, do not ship fix-includes. It would actually be preferable for you to patch your illumos tree with whatever fix you want than to do that.
-- Rich 2013/6/3 Andrzej Szeszo <[email protected]> > My cheeky plan was to get someone to "fix" the headers in illumos itself. > > Alternative is to ignore the issue and include the fixed-includes > contents in the gcc package. > > Alexander, feel free to add "fixed-includes" to the gcc package. My > initial gcc package is getting rid of the directory in the Makefile > altogether. > > We can look at fixing illumos headers at later time. > > Andrzej > > On 3 June 2013 15:56, Alexander Pyhalov <[email protected]> wrote: > > On 06/03/2013 17:46, Alexander Pyhalov wrote: > >> > >> Hello, everyone... > >> Maybe I'm wrong, but, for example, OpenCSW gcc 4.8 package contains a > >> big set of fixed includes. Why doesn't our g++ 4.7 package include any? > > > > > > Compare, for example, > > > http://pkg.omniti.com/omnios/release/manifest/0/developer%2Fgcc47%404.7.2%2C5.11-0.151006%3A20130429T221114Z > > and > > > http://pkg.openindiana.org/hipster/manifest/0/developer%2Fgcc-47%404.7.3%2C5.11-0.151.1.8.1%3A20130518T182047Z > > . > > > > > > -- > > Best regards, > > Alexander Pyhalov, > > system administrator of Computer Center of Southern Federal University > > > > _______________________________________________ > > oi-dev mailing list > > [email protected] > > http://openindiana.org/mailman/listinfo/oi-dev > > _______________________________________________ > oi-dev mailing list > [email protected] > http://openindiana.org/mailman/listinfo/oi-dev >
_______________________________________________ oi-dev mailing list [email protected] http://openindiana.org/mailman/listinfo/oi-dev
