Date: Sat, 24 Aug 2013 09:43:53 -0600 From: Warner Losh <imp@bsdimp.com> To: "Sam Fourman Jr." <sfourman@gmail.com> Cc: toolchain@freebsd.org, Boris Samorodov <bsam@passap.ru>, FreeBSD Current <current@freebsd.org>, Slawa Olhovchenkov <slw@zxy.spb.ru> Subject: Re: GCC withdraw Message-ID: <E0058AB2-5796-44F7-A6E1-6544AFCB5B98@bsdimp.com> In-Reply-To: <CAOFF%2BZ20SGE6pXh9KaQFdg7WzbrTwmYFA4Hu7ZJ2Jbc8yD-7Lg@mail.gmail.com> References: <20130822200902.GG94127@funkthat.com> <105E26EE-8471-49D3-AB57-FBE2779CF8D0@FreeBSD.org> <5217413A.9080105@passap.ru> <20130823111647.GT2951@home.opsec.eu> <521745F2.8050607@passap.ru> <CAOFF%2BZ3vbOgMO7T-BKZnhKte6=rFoGcdYcft5kpAgNH2my1JKg@mail.gmail.com> <20130824115158.GA88999@zxy.spb.ru> <CAOFF%2BZ20SGE6pXh9KaQFdg7WzbrTwmYFA4Hu7ZJ2Jbc8yD-7Lg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 24, 2013, at 6:11 AM, Sam Fourman Jr. wrote: >> In my opinion this just needs to happen, if ports break, we deal with = that >=20 >>> on a case by case basis. >>=20 >> Oh, I remember. mplayer on i386 can't be builded witch clang -- clang >> don't understand inlined asm. >>=20 >>=20 > Well, in this case, you would just have the mplayer maintainer = configure the > port to use gcc for the i386 build of mplayer... problem solved The problem is that there's a lot of cases in ports where this work = needs to be done. That work is ongoing, but isn't done yet. The ports = people have indicated that in the 10 time frame may be a bit = optimistic... Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0058AB2-5796-44F7-A6E1-6544AFCB5B98>