Subject: Re: Report on broken packages, gcc3 on sparc64
To: Frederick Bruckman <email@example.com>
From: Martin Husemann <firstname.lastname@example.org>
Date: 07/17/2003 20:53:11
On Thu, Jul 17, 2003 at 10:52:46AM -0500, Frederick Bruckman wrote:
> There's nothing wrong with gcc-3* in that regard. It's well
> documented, and modern autoconf systems allow for it, using "gcc -E"
> for the C-preprocessor.
All fine with me, but then our src/tools tree is broken.
> export CPP='/usr/pkg/gcc-3.3/bin/cpp -gcc'
Uhm, that's what I would call a hack. How will things be once gcc3.3.x is
integrated into the main source tree? Will you still have to set CPP to
"/usr/bin/cpp -gcc"? Will bsd.*.mk take care of it?