提交 8bc0147f 编写于 作者: R Richard Levitte

Build files: when using $(CPP), use the C flags alongside the CPP flags

The reason for this is that some of the C flags affect built in macros
that we may depend on.
Reviewed-by: NAndy Polyakov <appro@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/5436)
上级 1af563e3
...@@ -658,9 +658,11 @@ EOF ...@@ -658,9 +658,11 @@ EOF
die "Generator type for $src unknown: $generator\n"; die "Generator type for $src unknown: $generator\n";
} }
my $cppflags = { lib => '$(LIB_CPPFLAGS)', my $cppflags = {
dso => '$(DSO_CPPFLAGS)', lib => '$(LIB_CFLAGS) $(LIB_CPPFLAGS)',
bin => '$(BIN_CPPFLAGS)' } -> {$args{intent}}; dso => '$(DSO_CFLAGS) $(DSO_CPPFLAGS)',
bin => '$(BIN_CFLAGS) $(BIN_CPPFLAGS)'
} -> {$args{intent}};
my @incs_cmds = includes({ lib => '$(LIB_INCLUDES)', my @incs_cmds = includes({ lib => '$(LIB_INCLUDES)',
dso => '$(DSO_INCLUDES)', dso => '$(DSO_INCLUDES)',
bin => '$(BIN_INCLUDES)' } -> {$args{intent}}, bin => '$(BIN_INCLUDES)' } -> {$args{intent}},
......
...@@ -850,9 +850,9 @@ EOF ...@@ -850,9 +850,9 @@ EOF
} }
my $cppflags = { my $cppflags = {
lib => '$(LIB_CPPFLAGS)', lib => '$(LIB_CFLAGS) $(LIB_CPPFLAGS)',
dso => '$(DSO_CPPFLAGS)', dso => '$(DSO_CFLAGS) $(DSO_CPPFLAGS)',
bin => '$(BIN_CPPFLAGS)' bin => '$(BIN_CFLAGS) $(BIN_CPPFLAGS)'
} -> {$args{intent}}; } -> {$args{intent}};
if (defined($generator)) { if (defined($generator)) {
# If the target is named foo.S in build.info, we want to # If the target is named foo.S in build.info, we want to
......
...@@ -436,9 +436,11 @@ EOF ...@@ -436,9 +436,11 @@ EOF
} }
my $cppflags = $incs; my $cppflags = $incs;
$cppflags .= { lib => '$(LIB_CPPFLAGS)', $cppflags .= {
dso => '$(DSO_CPPFLAGS)', lib => ' $(LIB_CFLAGS) $(LIB_CPPFLAGS)',
bin => '$(BIN_CPPFLAGS)' } -> {$args{intent}}; dso => ' $(DSO_CFLAGS) $(DSO_CPPFLAGS)',
bin => ' $(BIN_CFLAGS) $(BIN_CPPFLAGS)'
} -> {$args{intent}};
if (defined($generator)) { if (defined($generator)) {
# If the target is named foo.S in build.info, we want to # If the target is named foo.S in build.info, we want to
# end up generating foo.s in two steps. # end up generating foo.s in two steps.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册