Is there anyone with Linux experience here who can tell me why I can't seem to have

F_OFD_* fcntls defined?

e.g.

util.c:155:14: error: 'F_OFD_SETLK' undeclared (first use in this function); did you mean 'F_SETLK'?

-D__USE_GNU?

I did that in a header file but maybe I need it on the gcc cmdline?

Doesn't help @denk

gcc12 on Debian 12 if this helps...

And yes I've installed the header files.

probably it needs something else, it's always a pain when I try to find answers to such questions

from time to time I just use gcc -E

danmcd: -D_GNU_SOURCE

THANK YOU!

jperkin: your gcc __STDC_VERSION__ stuff would be good to float around the developer list

I think we've all looked at it and gone "Oh, huh?" before

yeh I have a few things that I'm testing that can likely be unified, like using the dragonfly locale backend

the dragonfly locale thing makes sense -- I think Garrett took the code from an equivalently aged FreeBSD -- but I suspect what it _actually_ means is the locale code in libc needs fixed

probably worth investigating how much it would suck if we then fixed and had to change back

I am semi-familiar with that stuff if there's something specific that can help.

which bit?

Fixing locale code in libc.

I have some patches in review (that I really should finish) that affect how we find the current locale.

but they should be largely orthogonal to what you do once you find it..

I have heard complaints about C++ locale stuff for a decade, but none that actually explained it

just were like "and there's the locale stuff..."

I think we added the _l stuff initially because it was required there, and then apparently we didn't get it right enough

to be honest, I think the intersection of C++ runtime and OS is something that requires far more from the C++ side than the OS

knowledge-wise

tsoome: Why do we do this ... src.illumos.org/source/xref/illumos…?r=f334afcf&fi=efi_loadaddr#190-191

viz., why do we constrain ourselves to memory under 4GB

I have found a system with 507MB at 000000100000 and then nothing really until 62.9GB up at 000100000000

There is a comment that says ""reportedly some 64bit systems are reported to have issues with memory above 4GB" but not really ... any detail on what those issues might be

anyway, illumos.org/issues/16572

→ BUG 16572: loader should be willing to put modules above 4GB if necessary (New)