This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
Re: adding 'g++-v3/cshadow' to cpp search path...
- To: stdc++ <libstdc++ at sourceware dot cygnus dot com>
- Subject: Re: adding 'g++-v3/cshadow' to cpp search path...
- From: brent verner <brent at rcfile dot org>
- Date: Wed, 23 Aug 2000 00:37:46 -0400
- References: <20000822221720.B24998@rcfile.org>
On 22 Aug 2000 at 22:17 (-0400), brent verner wrote:
| Greetings,
|
| I didn't have time to dig more into sorting out the real cshadow
| problem, so I decided I could at least be productive by hacking the
| gcc build to have cpp search 'g++-v3/cshadow' for includes first.
success!! kinda :)
(my) g++ is now pulling includes from:
${prefix}/include/g++-v3/cshadow
${prefix}/include/g++-v3
I'll submit a patch tomorrow (night), after I install the 'approved'
maintainer tools -- I can't verify the work until I regenerate,
which leads to a question:
when submitting a patch that modifies configure.in, should the
diff include the regenerated configure, or just the changes to
configure.in?
should this patch be sent to gcc-patches since it modifies
gcc/configure.in? or would it be best to kick it around
here (review) it here for a bit first?
TIA for your input.
cheers.
brent
--
Damon Brent Verner o _ _ _
Cracker JackŪ Surprise Certified _o /\_ _ \\o (_)\__/o (_)
brent@rcfile.org _< \_ _>(_) (_)/<_ \_| \ _|/' \/
brent@linux1.org (_)>(_) (_) (_) (_) (_)' _\o_