Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-20 Thread Gerald Pfeifer
On Mon, 19 Dec 2011, Steve Kargl wrote: Not sure why you need confirmation before committing if it works for you, because anything has to be better than the current state. Well, I prefer not having to follow up with further patches later (and luckily my full testing uncovered another small

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-19 Thread Steve Kargl
On Mon, Dec 19, 2011 at 04:09:02PM +0900, Gerald Pfeifer wrote: As usual, Brendan is right on target. :-) If you guys would like to test the attached patch for lang/gcc, it does allow that port to build on a FreeBSD 10 system for me, and if I get independent confirmation in the next three

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-18 Thread Gerald Pfeifer
On Sat, 17 Dec 2011, b. f. wrote: Fixes have already been implemented upstream, at Gerald's request, and are in lang/gcc46. But these fixes were introduced after the last stable release of gcc 4.6, which corresponds to lang/gcc. When a new version of gcc 4.6 is released, and the port is

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-16 Thread Xin LI
Hi, Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? Cheers, -- Xin LI delp...@delphij.net https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-16 Thread Mark Linimon
On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? My guess? We should rip out the [123] and [23] strings entirely. If anyone

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-16 Thread Steve Kargl
On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? There are probably a few different ways to workaround the problem. This

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-16 Thread b. f.
Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (gerald at FreeBSD.org) by the way? My guess? We should rip out the [123] and [23] strings entirely. If anyone is running ports on FreeBSD 1, they have more

Re: [PATCH] lang/gcc -- Fix build on freebsd-current

2011-12-16 Thread Steve Kargl
On Fri, Dec 16, 2011 at 09:15:06PM -0600, Mark Linimon wrote: On Fri, Dec 16, 2011 at 06:09:08PM -0800, Xin LI wrote: Actually you can add a dot (.) to these matches, e.g. freebsd[123]* - freebsd[123].*, etc... Have you contacted the maintainer (ger...@freebsd.org) by the way? My guess?