This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/17991] New: [4.0 Regression] Two-process fixincludes broken: pz_mn_name_pat undefined
- From: "aaronavay62 at aaronwl dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Oct 2004 07:04:21 -0000
- Subject: [Bug other/17991] New: [4.0 Regression] Two-process fixincludes broken: pz_mn_name_pat undefined
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
This patch appears to have broken two-process fixincludes:
<http://gcc.gnu.org/ml/gcc-patches/2004-08/msg02301.html>. When attempting to
link applyfix.exe, link fails because pz_mn_name_pat is undefined.
The two-process mode is only used for MS-DOS and BeOS, which is probably why
noone noticed. I noticed because it appears that, other than this and some
other soon-to-be-fixed problems, two process fixincludes also works for
Windows.
The problem is that mn_name_pat was made into an environment variable, which
are only defined in fixincl.c, which is only included in the fixincl
executable. However, it is used in fixlib.c, which is included in the
applyfix executable in a two-process build.
As I'm not really familiar with fixincludes, I can't say how this should be
fixed. It can be worked around by copying the environment variable
definitions and initializations from fixincl.c to the SEPARATE_FIX_PROC
section of fixfixes.c, but I'm not sure this is appropriate as applyfix
doesn't need any of these environment variables otherwise. Perhaps just this
single environment variable could be defined.
--
Summary: [4.0 Regression] Two-process fixincludes broken:
pz_mn_name_pat undefined
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: aaronavay62 at aaronwl dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i?86-*-mingw32, i?86-*-msdosdjgpp, *-*-beos*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17991