--==========B37CE910FEEE2885C1A2==========
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline



--On Samstag, Februar 07, 2004 14:44:52 -0800 walt <wa1ter@myrealbox.com>=20
wrote:

> Just yesterday after the CVS problem seemed to disappear I got my
> -CURRENT sources updated at last.  I rebuilt the system and rebooted,
> then updated pkgsrc.
>
> I now have multiple packages that won't upgrade because they abort
> during the 'config' stage with an error message that gcc is
> not able to make executables.  Just prior to that error there is
> another error that says 'cc1 cannot be found' or similar.  Of
> course cc1 is in libexec where it always is, but config can't find
> it for some reason.  Anyone know how config normally finds cc1?
>
> Anyone else seeing this today or yesterday?
Yes, see eg. pkg/24345. As a band aid you could revert mk/compiler/gcc.mk=20
to rev. 1.43.

HTH,
Marc
--==========B37CE910FEEE2885C1A2==========
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAJXHU7YQCetAaG3MRAs4+AJ4tG2U4DIOT3oIqVNGIFVIL3qTWogCfccqR
lxUNMLU/1+JnRjMrgBky7Y0=
=pnOt
-----END PGP SIGNATURE-----

--==========B37CE910FEEE2885C1A2==========--