On Thu, Jan 23, 2020 at 12:27 PM akuster808 wrote:
>
>
> On 1/23/20 10:35 AM, Khem Raj wrote:
> > one of the build steps ruby has is that it generated rb_mjit_header.h
> > during configure using gcc preprocessor using -dD which emits built-in
> > defines as well, problem happens when this header
On 1/23/20 10:35 AM, Khem Raj wrote:
> one of the build steps ruby has is that it generated rb_mjit_header.h
> during configure using gcc preprocessor using -dD which emits built-in
> defines as well, problem happens when this header is later included in
> subsequent compiles, where compiler
ignore it
On Thu, Jan 23, 2020 at 10:35 AM Khem Raj wrote:
>
> one of the build steps ruby has is that it generated rb_mjit_header.h
> during configure using gcc preprocessor using -dD which emits built-in
> defines as well, problem happens when this header is later included in
> subsequent
one of the build steps ruby has is that it generated rb_mjit_header.h
during configure using gcc preprocessor using -dD which emits built-in
defines as well, problem happens when this header is later included in
subsequent compiles, where compiler errors out stating that an existing
internal
