Fabian Ruffy

Option 2 would be nice since we do have good MacOS support for P4C. Part of the reason support is now easier for P4C is because we control most of...

Getting the stacktrace of this particular exception could be helpful. I currently do not have the bf-p4c binary at hand.

> How do I enable stack traces for exceptions? If Vladimir's suggestion does not work you could install `https://github.com/ianlancetaylor/libbacktrace` and recompile with it [enabled](https://github.com/p4lang/p4c/blob/main/CMakeLists.txt#L247). Or use gdb with `catch exception`...

This looks like a bug introduced by #5018. We are probably accessing an annotation in an unsafe way.

Fixed in #5193 but requires some more testing.

We should add this to the documentation. @pkotikal @hanw Do you know who is responsible for maintaining the Tofino back end at this point?

That might be a better approach. It'd be nice if non-system includes were also preserved, but it seems complicated to reconstructed this after the preprocessed has inlined everything.

> And what is the problem you are trying to solve here? How are system includes treated differently from non-system once in P4C? The problem is that there might be...

@osinstom @tatry You can add the `--extern-file` command to the compiler, I would take a look at the https://github.com/p4lang/p4c/blob/main/backends/ebpf/CMakeLists.txt#L256C156-L256C169 `ebpf_checksum_extern` example. ```bash sudo -E p4c/backends/ebpf/run-ebpf-test.py -t test -c "p4c/build/p4c-ebpf" p4c...

Clever solution. Nevertheless, it might be easier to just compile with a version of boost that is not broken?