On Thu, Jul 1, 2010 at 4:42 PM, Ruben Van Boxem <[email protected]> wrote: > Hi, > > Following up on a recent discussion on the bug tracker, I'd like to know > what came of this discussion on the gcc list: > http://gcc.gnu.org/ml/gcc-patches/2010-01/msg01114.html > > Is there a need to open a new bug report, is it fixed somewhere upstream,
No, it is not. > should I annoy the devs with spam about this? ;) > > How about the whole /mingw directory, is there a way to fix this or have gcc > people already refused that? > Well, with our builds, gcc includes its own headers first and then the system provided headers, that's where the problem is. As for a solution no one agreed upon anything, nor did they openly refused anything. > And last but not least, how are things on the runtime dll naming scheme? And > the support for /lib32 and /lib64 vs /lib? If I need to bug the gcc list, > I'll be glad to :) (pun intended). > Kai would answer that better. > Ruben > -- Ozkan ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
