I did not indicate I was initially building with MSVC. I am compiling on a Mac
using cmake. I don’t know what it's defaults are.
-- DM
> On Jul 8, 2025, at 11:42 PM, Greg Hellings wrote:
>
> Including it also fixes the build in my cross-build environment. Did you
> indicate you were initially
Including it also fixes the build in my cross-build environment. Did you
indicate you were initially building with MSVC? That might explain the
difference.
--Greg
On Tue, Jul 8, 2025 at 9:54 PM DM Smith wrote:
> While I don’t get the error in my local build environment, I get it on the
> crossw
While I don’t get the error in my local build environment, I get it on the
crosswire server. If I include , it compiles just fine.
I’ll guess that my build environment includes it indirectly.
DM
> On Jul 8, 2025, at 10:40 PM, DM Smith wrote:
>
> Greg,
> Could you try 2 different things and let
Greg,
Could you try 2 different things and let me know what the result is?
a) include as I didn’t include it, but somehow “It works for me”.
b) remove the namespace.
I’ll try the same on the crosswire server.
Thanks,
DM
> On Jul 8, 2025, at 9:35 PM, Greg Hellings wrote:
>
> DM,
>
> A
DM,
As mentioned elsewhere, here is the compile error from gcc when trying to
cross-build osis2mod. It appears to be a case where the function exists but
is not namespaced to `std::` in whichever version of C++ is the
default version. From a quick glance around it appears there is a
difference bet
