Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Dec 2011 11:51:14 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Ed Schouten <ed@80386.nl>
Cc:        svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Andreas Tobler <andreast@FreeBSD.org>
Subject:   Re: svn commit: r228955 - head/include
Message-ID:  <20111229195114.GA48308@troutmask.apl.washington.edu>
In-Reply-To: <20111229192359.GM1895@hoeg.nl>
References:  <201112291441.pBTEfI8l060127@svn.freebsd.org> <4EFCA6A6.6080103@FreeBSD.org> <20111229183213.GK1895@hoeg.nl> <20111229184934.GA47885@troutmask.apl.washington.edu> <20111229192359.GM1895@hoeg.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 29, 2011 at 08:23:59PM +0100, Ed Schouten wrote:
> Hi Steve,
> 
> * Steve Kargl <sgk@troutmask.apl.washington.edu>, 20111229 19:49:
> > Are you going to submit a bug report to GCC?  Because, as of now,
> > you've broken my ability to do development work on bleeding edge
> > freebsd and bleeding edge gcc.
> 
> Here you go:
> 
> 	http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51705

Thanks.

> In the future, could you write such bug reports yourself? I am really
> not that interested in GCC's development process.

I'll try, but I don't know C11 or C++11.  While you may have
no interest in GCC developement, the ports collection uses
GCC.  I can also see this type of problem leading to 3rd
part software developer dropping support for FreeBSD because
they need to work around issues with FreeBSD headers.  

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111229195114.GA48308>