C++ Source Constructor and Proxy Class Constructor Contradiction

[OftenDream]

I'm trying to use swig to automatically generate java code from C++ code. there are classes in C++ that have the original constructors (long, boolean), such as RangeSearchResult(Long, boolean)
In macos swig, this conflicts with the proxy classes generated by swig. (Similar to this issue swig/swig#1057)
But in linux swig, there is no such problem. swig automatically converts constructor arguments of this type to (int, boolean).

proxy class:
protected RangeSearchResult(long cPtr, boolean cMemoryOwn)
{
swigCMemOwn = cMemoryOwn;
swigCPtr = cPtr;
}

constructor on macOS：
public final static native long new_RangeSearchResult__SWIG_0(long jarg1, boolean jarg2);
（long, boolean） is the type of the original construct in C++ code, but it conflicts with the proxy class.

constructor on CentOS：
public final static native long new_RangeSearchResult__SWIG_0(int jarg1, boolean jarg2);

I would like to know how to have this effect on MacOS as well.Thanks a lot.