--sdtB3X0nJg68CQEu
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 28, 2011 at 09:37:28AM +0900, NARUSE, Yui wrote:
> 2011/10/28 Aaron Patterson <tenderlove / ruby-lang.org>:
> > On Thu, Oct 27, 2011 at 10:46:10AM +0900, nagachika wrote:
> >> Which compiler did you use to build ruby?
> >
> > [aaron@higgins ruby (08b3d47...)]$ gcc -v
> > Using built-in specs.
> > Target: i686-apple-darwin11
> > Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/src/co=
nfigure --disable-checking --enable-werror --prefix=3D/Developer/usr/llvm-g=
cc-4.2 --mandir=3D/share/man --enable-languages=3Dc,objc,c++,obj-c++ --prog=
ram-prefix=3Dllvm- --program-transform-name=3D/^[cg][^.-]*$/s/$/-4.2/ --wit=
h-slibdir=3D/usr/lib --build=3Di686-apple-darwin11 --enable-llvm=3D/private=
/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/dst-llvmCore/Developer/usr/local --=
program-prefix=3Di686-apple-darwin11- --host=3Dx86_64-apple-darwin11 --targ=
et=3Di686-apple-darwin11 --with-gxx-include-dir=3D/usr/include/c++/4.2.1
> > Thread model: posix
> > gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.=
00)
> >
> >> Though I can't reproduce in my environment, I guess it is related to
> >> deleted workaround for llvm at r33408.
> >> Could you try with reverting r33408?
> >
> > The problem started happening at revision r33419. =A0However, if I reve=
rt
> > r33408, everything works again. :(
> >
> > I will revert r33408 and commit.
>=20
> llvm-gcc is not supported because it is too buggy and no future.
> (This is the last release to support the llvm-gcc frontend
>  http://llvm.org/releases/2.9/docs/ReleaseNotes.html#additionalinfo )
> Please use GNU GCC or try LLVM/Clang.

If we're not going to support llvm-gcc, can we make the configure script
not use it?  My system has both llvm/clang *and* llvm-gcc.  It seems
strange that configure would choose the compiler we don't support ;-)

--=20
Aaron Patterson
http://tenderlovemaking.com/

--sdtB3X0nJg68CQEu
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iQEcBAEBAgAGBQJOrvuwAAoJEJUxcLy0/6/GPFcH+waBVHjQHX9yKa8CRfJ7RbJb
ozJmChTozXJFbdOn+z1MYhdqhTrfQ1YO9cW8wTAs9KDGa85+Sc/5QUh/fH+cgMPC
kjkbli5ZVXy5tZuo7wy2s4SWiROn0CBH1JdKj/5udreBWNkvSQ949jE0XHCzGZ0q
X8uIUPLdqxOWLtRcstB8dkomdjmMiWD+2gxVDWTcWuAvw10ZyfOjs74f8wULAq9k
LzK1y3f3bL6h2NSsVp0xgFZrPGZbZERRoJ6Wg5P67XFE3JRwR5D3MWqhJgfFGiig
rJHrVBde/8APdHU4e5v1ekmC8ro8kWNA0mEI8rr8Nl4nF4nMUwik9UNFNhII4Mk=
=upYg
-----END PGP SIGNATURE-----

--sdtB3X0nJg68CQEu--

On Fri, Oct 28, 2011 at 09:37:28AM +0900, NARUSE, Yui wrote:
> 2011/10/28 Aaron Patterson <tenderlove / ruby-lang.org>:
> > On Thu, Oct 27, 2011 at 10:46:10AM +0900, nagachika wrote:
> >> Which compiler did you use to build ruby?
> >
> > [aaron@higgins ruby (08b3d47...)]$ gcc -v
> > Using built-in specs.
> > Target: i686-apple-darwin11
> > Configured with: /private/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/src/co=
nfigure --disable-checking --enable-werror --prefix=3D/Developer/usr/llvm-g=
cc-4.2 --mandir=3D/share/man --enable-languages=3Dc,objc,c++,obj-c++ --prog=
ram-prefix=3Dllvm- --program-transform-name=3D/^[cg][^.-]*$/s/$/-4.2/ --wit=
h-slibdir=3D/usr/lib --build=3Di686-apple-darwin11 --enable-llvm=3D/private=
/var/tmp/llvmgcc42/llvmgcc42-2335.15~25/dst-llvmCore/Developer/usr/local --=
program-prefix=3Di686-apple-darwin11- --host=3Dx86_64-apple-darwin11 --targ=
et=3Di686-apple-darwin11 --with-gxx-include-dir=3D/usr/include/c++/4.2.1
> > Thread model: posix
> > gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.=
00)
> >
> >> Though I can't reproduce in my environment, I guess it is related to
> >> deleted workaround for llvm at r33408.
> >> Could you try with reverting r33408?
> >
> > The problem started happening at revision r33419. =A0However, if I reve=
rt
> > r33408, everything works again. :(
> >
> > I will revert r33408 and commit.
>=20
> llvm-gcc is not supported because it is too buggy and no future.
> (This is the last release to support the llvm-gcc frontend
>  http://llvm.org/releases/2.9/docs/ReleaseNotes.html#additionalinfo )
> Please use GNU GCC or try LLVM/Clang.

If we're not going to support llvm-gcc, can we make the configure script
not use it?  My system has both llvm/clang *and* llvm-gcc.  It seems
strange that configure would choose the compiler we don't support ;-)

--=20
Aaron Patterson
http://tenderlovemaking.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iQEcBAEBAgAGBQJOrvuwAAoJEJUxcLy0/6/GPFcH+waBVHjQHX9yKa8CRfJ7RbJb
ozJmChTozXJFbdOn+z1MYhdqhTrfQ1YO9cW8wTAs9KDGa85+Sc/5QUh/fH+cgMPC
kjkbli5ZVXy5tZuo7wy2s4SWiROn0CBH1JdKj/5udreBWNkvSQ949jE0XHCzGZ0q
X8uIUPLdqxOWLtRcstB8dkomdjmMiWD+2gxVDWTcWuAvw10ZyfOjs74f8wULAq9k
LzK1y3f3bL6h2NSsVp0xgFZrPGZbZERRoJ6Wg5P67XFE3JRwR5D3MWqhJgfFGiig
rJHrVBde/8APdHU4e5v1ekmC8ro8kWNA0mEI8rr8Nl4nF4nMUwik9UNFNhII4Mk=
=upYg
-----END PGP SIGNATURE-----