Shakedown Social

Freya (it/its)𒀭𒈹𒍠𒊩Solaris you're cursed. We've had to add<a href="https://chaosfem.tw/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> NI_MAXHOST <a href="https://chaosfem.tw/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> NI_MAXHOST 1025 // As per POSIX recommendation <a href="https://chaosfem.tw/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a><a href="https://chaosfem.tw/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> NI_MAXSERV <a href="https://chaosfem.tw/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> NI_MAXSERV 32 // As per POSIX recommendation <a href="https://chaosfem.tw/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>To like 6 C source files to get pgsql to build

Thierry Laurion<a href="https://mas.to/@libreleah" class="u-url mention" rel="nofollow noopener" target="_blank">@libreleah</a> <a href="https://mas.to/@mkukri" class="u-url mention" rel="nofollow noopener" target="_blank">@mkukri</a> Both Heads and lbmk permit to apply patches on top of a coreboot fork. The difference between the two here is that lbmk builds the tree, clean, for each boards, where Heads applies the patches to a fork once, and each board reuses fork build artifacts;, building board specifics in a board specific artifact directory. That permits crossgcc, being the buildstack of each coreboot fork version to be built once, and also repro build issues upstream, economizing both disk space, cpu resource for user and CI.In Heads goal of building fully functional roms, CI can build and stitch reproducible roms for each commit for end users to download directly from CI, for each commit, and see if a comit broke a built, for each commit. CI cache is reused, so that we don't waste CI resources either.In the case of t480, the patch was made with lbmk in mind, not coreboot nor Heads, and breaks other thinkpads in coreboot upstream, trying to not only build for t480 but make sure t480 patchset doesn't break other boards. In this case, it breaks all other thinkpads, so prevent Heads from merging the PR. What you propose here is for libreboot and Heads to maintain a patchset not merged upstream; it might suit libreboot mindset, being more bleeding edge, and minifree, selling the t480, but not Heads. Heads tries to stay as close as possible to upstream forks, and pushes upstream projects to merge patches. Its long, not easy, but the right thing to do. The patches stays in a patch dir for everyone to see, per software version. In this case, patches/coreboot-24.12/*I tried to apply the following patch without success instead of commenting thermal.asl+diff --git a/src/ec/lenovo/h8/acpi/ec.asl b/src/ec/lenovo/h8/acpi/ec.asl +index bc54d3b..a0408c8 100644 +--- a/src/ec/lenovo/h8/acpi/ec.asl ++++ b/src/ec/lenovo/h8/acpi/ec.asl +@@ -331,7 +331,13 @@ Device(EC) + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "sleepbutton.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "lid.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "beep.asl" ++ ++<a href="https://infosec.exchange/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> CONFIG_BOARD_LENOVO_T480 + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "thermal.asl" ++<a href="https://infosec.exchange/tags/else" class="mention hashtag" rel="nofollow noopener" target="_blank">#else</a> ++//#include "thermal.asl" ++<a href="https://infosec.exchange/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> ++ + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "systemstatus.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener" target="_blank">#include</a> "thinkpad.asl" + }Other non t480 fail to build, and I have no more time to spend on this. The community is interested, tried to reach libreboot and were seen as spammers.Please fix your patchset upstream. People saw the t480 being "supported by coreboot" in a talk. People didn't understand it was a WiP patchset under coreboot. And here we are. 24.12 was december 2024 "release", there will be another one in 25.03... I do not have time to maintain patches on top of patches, Leah. My focus is not to be a coreboot distribution. My focus is to deliver reproducible roms to users needing accessible security, and improve that UX. There is no grub/seabios under Heads, my focus is to make upstream do the right thing and participate upstream, and make contributors participate upstream. Here, you stated loud and clear tha libreboot comes first before coreboot, I respect that. But the t480 patchset is the one too from upstream. That upstream patch needs to build, and then will be merged and then you won't have to maintain it either. And others will fix audio issues, nvidia etc. Otherwise its silo work, and i'm not interested in that anymore---Yes, there is different coreboot forks specified in a central place: modules/coreboot. And there, the buildsystem says if it can reuse crossgcc of another fork to fasten builds for each commit. The idea here is that the user building one board, or multiple boards will get the same result, but CI building multiple boards based on the same fork will speed up builds massively.d16 will move to fam15h fork from other community effort. I mentor now, I don't try to do everything myself. Just as here, trying tto collaborate with you so you fix what was brought up upstream. But up to now, you are upstream for t480.The goal here was not to compare our buildsystems, simply stating that the patchset upstream will never be merged if it causes regressions building other boards. Libreboot can do what it wants, but needs to respect how coreboot works. Their CI does the same, and make sure that building a commit for a board won't break others. In current case, it breaks others and needs to be updated.This needs to be fixed upstream at <a href="https://review.coreboot.org/c/coreboot/+/83274" rel="nofollow noopener" translate="no" target="_blank">https://review.coreboot.org/c/coreboot/+/83274</a>

Craig HockenberryGood news: there's code for it:<a href="https://mastodon.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> ZAHL <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> ZAHL 0 <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>Bad news: XOR-ing a value with 0 isn't going to help. It's a NOP.And it's intentional, for example:ts ^= ZAHL; /* hehe */I can’t reverse engineer the real value of ZAHL without knowing the original timestamp.It might be possible to do an exhaustive search, but time_t is a long long and my time is short short.So no blog.fefe.de for Tapestry. Sorry!3/3

SpaceLifeForm<a href="https://mastodon.social/@bigzaphod" class="u-url mention" rel="nofollow noopener" target="_blank">@bigzaphod</a> Using a C toolchain, I would -Dname from command line, which gets passed to pre-compiler (the frontend), and inside your source code, you conditionally compile using <a href="https://infosec.exchange/tags/ifdef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifdef</a> and/or <a href="https://infosec.exchange/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> .<a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a>

Andre Weissflog<a href="https://peoplemaking.games/@sol_hsa" class="u-url mention" rel="nofollow noopener" target="_blank">@sol_hsa</a> <a href="https://mastodon.gamedev.place/@pythno" class="u-url mention" rel="nofollow noopener" target="_blank">@pythno</a> fwiw this is what I do in sokol_app.h before including windows.h: <a href="https://mastodon.gamedev.place/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> WIN32_LEAN_AND_MEAN <a href="https://mastodon.gamedev.place/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> WIN32_LEAN_AND_MEAN <a href="https://mastodon.gamedev.place/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> <a href="https://mastodon.gamedev.place/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> NOMINMAX <a href="https://mastodon.gamedev.place/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> NOMINMAX <a href="https://mastodon.gamedev.place/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a> (also I only include windows.h in the implementation, not in the interface declaration)

Paul Haddad :tapbots_logo:<a href="https://mastodon.social/@marcoarment" class="u-url mention" rel="nofollow noopener" target="_blank">@marcoarment</a> I mean you can work around at least one of those.<a href="https://tapbots.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> let <a href="https://tapbots.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> let __auto_type const <a href="https://tapbots.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a><a href="https://tapbots.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> var <a href="https://tapbots.social/tags/define" class="mention hashtag" rel="nofollow noopener" target="_blank">#define</a> var __auto_type <a href="https://tapbots.social/tags/endif" class="mention hashtag" rel="nofollow noopener" target="_blank">#endif</a>

Foone🏳️‍⚧️arg two libraries I'm using are colliding on IFDEF namesbecause both have <a href="https://digipres.club/tags/ifndef" class="mention hashtag" rel="nofollow noopener" target="_blank">#ifndef</a> KEY_H include barriers around their very generically named key.h files

Recent searches

Search options

Administered by:

Server stats:

#ifndef