aboutsummaryrefslogtreecommitdiff
path: root/libgfortran/m4
diff options
context:
space:
mode:
authorNathan Sidwell <nathan@acm.org>2020-12-08 06:31:31 -0800
committerNathan Sidwell <nathan@acm.org>2020-12-08 06:31:31 -0800
commit0bd4fecbea3b3da9befe24906f699d63fb28ed71 (patch)
treefa6703f6a6c098172dd8168d7eb333e71c386b22 /libgfortran/m4
parent210d143dbc575f293affbd55417505bcb8257d74 (diff)
downloadgcc-0bd4fecbea3b3da9befe24906f699d63fb28ed71.zip
gcc-0bd4fecbea3b3da9befe24906f699d63fb28ed71.tar.gz
gcc-0bd4fecbea3b3da9befe24906f699d63fb28ed71.tar.bz2
c++: Fix MODULE_VERSION breakage
Adding includes to module.cc triggered the kind of build failure I wanted to check for. In this case it was MODULE_VERSION not being defined, and module.cc's internal #error triggering. I've relaxed the check in Make-lang, so we proviude MODULE_VERSION when DEVPHASE is not empty (rather than when it is 'experimental'). AFAICT devphase is empty for release builds, and the #error will force us to decide whether modules is sufficiently baked at that point. gcc/cp * Make-lang.in (MODULE_VERSION): Override when DEVPHASE not empty. * module.cc: Comment.
Diffstat (limited to 'libgfortran/m4')
0 files changed, 0 insertions, 0 deletions