#linux - VBoxNetFlt does not build on #Fedora 38 - Super User
https://superuser.com/questions/1806205/vboxnetflt-does-not-build-on-fedora-38
edit /usr/share/virtualbox/src/vboxhost/vboxnetflt/linux/VBoxNetFlt-linux.c and change
#if RTLNX_VER_MIN(6,5,0) # include <net/gso.h> #endif
to 5,4,0
@lain_7 @rifkin @jef Basically same here:
────
#if 0
ctime -begin ${0%.*}.ctm
clang -g -fsanitize=address -std=c99 $0 -o ${0%.*}
ctime -end ${0%.*}.ctm
exit
#endif
────
That's the intro to all my new .c files. (ctime, by the way, times the build.) I got the idea from Won Chun, and like to think of it grandly as "The Won Build System".
I used to start quickie C programs with:
----------------------------
#ifdef notdef
gcc $0 -o $(basename $0 .c)
exit $?
#endif
int main....
---------------------------
Then I could compile by saying "sh foo.c"
This was especially useful if the compile line was complicated (e.g., the C program required linking with special libraries or something).
(Actually I used back-quotes instead of $(....), but this phone doesn't have back-quote on this keyboard.)
sys/dev/fdt: fdt_boot.c
skrll: G/C some #if 0 / #endif code
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/fdt/fdt_boot.c.diff?r1=1.3&r2=1.4
Cファイル内にシェルスクリプトを書くことによりビルドスクリプトとソースコードを1つのファイルにまとめるという荒業
```c
#if 0
set -e
OUTPUT="$(mktemp)"
gcc "${0}" -o "${OUTPUT}"
set +e
"${OUTPUT}" "${@}"
RET="${?}"
rm "${OUTPUT}"
exit "${RET}"
#endif
#include <stdio.h>
#include <stdlib.h>
int main(int argc, char* argv[]) {
printf("Hello, world!\n");
for (int i = 1; i < argc; i++)
printf("argv[%d]: %s\n", i, argv[i]);
return EXIT_SUCCESS;
}
```
sys/arch/evbarm/nslu2: nslu2_machdep.c
rin: Missing #endif for the previous...
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/evbarm/nslu2/nslu2_machdep.c.diff?r1=1.38&r2=1.39
I rebuild Mesa with assertions enabled and rerun the unit test... and it passes. Huh?
I rebuild without assertions, assuming I made some kind of mistake. Unit test fails again.
I confirm that the allocations are properly aligned when Mesa is built with assertions and unaligned when built without assertions. So I'm not going crazy, but WTF?
Then I spot this in the definition of the `gc_block_header` struct (which `gc_alloc_size` allocates):
> #ifndef NDEBUG
> unsigned canary;
> #endif
Oh.
Compiling sqlite3.c (amalgamated version of sqlite) with cake
I got interesting warnings
static void charFunc(
...
*zOut++ = 0x80 + (u8)(c & 0x3F);
} \
}
sqlite3_result_text64(context, (char*)z, zOut-z, sqlite3_free, SQLITE_UTF8);
}
#if defined(SQLITE_WIN32_HAS_ANSI)
WINBASEAPI HANDLE WINAPI CreateFileMappingA(HANDLE, LPSECURITY_ATTRIBUTES, \
DWORD, DWORD, DWORD, LPCSTR);
#endif /* defined(SQLITE_WIN32_HAS_ANSI) */
2023-05-18: CHANGES IN R 4.3.0 patched C-LEVEL FACILITIES
*
The C prototypes for LAPACK calls ‘dspgv’ and ‘dtptrs’ in ‘R_exts/Lapack.h’ had one too many and one too few character length arguments - but this has not caused any known issues. To get the corrected prototypes, include
#include // for PR18534fixed #ifdef PR18534fixed # define usePR18534fix 1 #endif #include
in your C/C++ code (PR#18534). https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2023/05/18?utm_source=dlvr.it&utm_medium=mastodon#n2023-05-18