Re: CURRENT: lang/gcc fails to build on CURRENT with error:
--=-wtJ6LF3otrgdSdsxdIa7
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
On Mon, 2013-03-11 at 17:29 +0100, Dimitry Andric wrote:
> On 2013-03-11 14:15, Niclas Zeising wrote:
> > On 03/11/13 14:13, Steve Kargl wrote:
> ...
> >> No. Here's my make.conf.
> >>
> >> KERNCONF=3DSPEW
> >> CPUTYPE?=3Dopteron
> >> FFLAGS+=3D -O2 -pipe -march=3Dnative -mtune=3Dnative -funroll-loops -f=
tree-vectorize
> >> MALLOC_PRODUCTION=3D"YES"
> >> WITHOUT_LIB32=3D"YES"
> >> WITHOUT_MODULES=3D"YES"
> >> WITHOUT_NLS=3D"YES"
> >> WITH_BSD_GREP=3D"YES"
> >> WITH_PROFILE=3D"YES"
> >> WITH_PKGNG=3Dyes
> >> PRINTERDEVICE=3Dps
> >> #
> >> # Crap for ports.
> >> #
> >> DISABLE_MAKE_JOBS=3D"YES"
> >> WITH_GHOSTSCRIPT_VER=3D8
> >> #
> >> # added by use.perl 2013-02-19 12:45:06
> >> PERL_VERSION=3D5.12.4
> >>
> >
> > This is most likely due to a incompatibility between bsd grep and gnu
> > grep. Try to switch to gnu grep, and the problem will most likely go a=
way.
>=20
> Yes, this is definitely due to a BSD grep bug. The depcomp tests
> create a file sub/conftest.Po, containing:
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> sub/conftest.o: sub/conftest.c sub/conftst1.h sub/conftst2.h \
> sub/conftst3.h sub/conftst4.h sub/conftst5.h sub/conftst6.h
>=20
> sub/conftst1.h:
>=20
> sub/conftst2.h:
>=20
> sub/conftst3.h:
>=20
> sub/conftst4.h:
>=20
> sub/conftst5.h:
>=20
> sub/conftst6.h:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Then it runs "grep sub/conftest.o sub/conftest.Po", which fails with BSD
> grep, and succeeds with GNU grep.
>=20
> BSD grep does something very strange here:
>=20
> $ echo 'foo.bar' | grep foo.bar
> foo.bar
> $ echo 'foo.barx' | grep foo.bar
> foo.barx
> $ echo 'sub/foo.bar' | grep sub/foo.bar
> sub/foo.bar
> $ echo 'sub/foo.barx' | grep sub/foo.bar
> $ echo $?
> 1
>=20
> So why does it not match in the last case? GNU grep works:
>=20
> $ echo 'sub/foo.barx' | gnugrep sub/foo.bar
> sub/foo.barx
After disabling WITH_BSD_GREP and rebuild of the system, it seems that
the machines in question now build lang/gcc.
--=-wtJ6LF3otrgdSdsxdIa7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)
iQEcBAABAgAGBQJRPg0WAAoJEOgBcD7A/5N8FLUIALEtSvCZEhbbVtHpHGo5Ds0K
RoeCyN++Z2MgPIRKoSIrEnoGAJ2D3WM69eIRlp6Ha68w/uUW3TqaVJ5vE24aCUuO
X4huHIeNDSj+CCUOYVKLBX90UdYGHrrXyToTnXW+aClsBCJbFo7KIk6ZM4GDvse4
1vCkhRRS9IZQZrKlivZNseSjERg5YUWcvXV+jK5rWJ7KxgGr4mAwMG3Dvdbymthh
W11pHcwcHGnew1aXO6Xp6wfeYQnGkBCzMEUcEv045oWDT2U25BlEoL7PWTx1B08o
zV7aDMkFwk4/V72ccszqliXCz2nlZi9DNyUiLMORFMi1WSdAuaimLKHojixJ3nY=
=gHqj
-----END PGP SIGNATURE-----
--=-wtJ6LF3otrgdSdsxdIa7--
討論串 (同標題文章)
完整討論串 (本文為第 8 之 9 篇)：