Helvede

0 posts0 participants0 posts today

Thierry Laurion<a href="https://mas.to/@libreleah" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@libreleah</a> <a href="https://mas.to/@mkukri" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#include</a> "sleepbutton.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#include</a> "lid.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#include</a> "beep.asl" ++ ++<a href="https://infosec.exchange/tags/ifndef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifndef</a> CONFIG_BOARD_LENOVO_T480 + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#include</a> "thermal.asl" ++<a href="https://infosec.exchange/tags/else" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#else</a> ++//#include "thermal.asl" ++<a href="https://infosec.exchange/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> ++ + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#include</a> "systemstatus.asl" + <a href="https://infosec.exchange/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#ifndef</a> ZAHL <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> ZAHL 0 <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" 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

Christian BeerIf you ask me, we all should not use ! like this:<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> !os(macOS ... <a href="https://mastodon.social/tags/else" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#else</a> ... do macOS things <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>The ! can be overlooked easily as it's only very thin... also why not just turn it around:<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> os(macOS) ... do macOS things <a href="https://mastodon.social/tags/else" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#else</a> … <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>

lambdageek<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mcc</a> <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> false Console.WriteLine("Hello false"); <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> true Console.WriteLine("Hello true"); <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>printed hello true.adding a DefineConstants for false 1. wasn't an error 😠 2. still only printed "hello true"

mccI am in C#. I wish to create an <a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a>…<a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> block that will always be false. I say "<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> false". This will:- Erase the code because "false" is not a defined symbol - Keep the code because "false" is a keyword - Keep or not keep depending on whether a command to define false was sent to the c# compiler?Here's some documentation. It doesn't help with this question<a href="https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/preprocessor-directives#conditional-compilation</a>

witch_t *navi<pre><code>#ifdef ENABLE_TRADITIONAL_ACTIVATION /* Kill the spawned process, since it sucks * (not sure this is what we want to do, but * may as well try it for now) */ if (pending_activation->babysitter) _dbus_babysitter_kill_child (pending_activation->babysitter); <a class="hashtag" href="https://social.vlhl.dev/tag/endif" rel="nofollow noopener noreferrer" target="_blank">#endif</a> </code></pre>why is this so funny to me

Fluor<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@mcc</a> true but really it was nothing more than<a href="https://wetdry.world/tags/ifdef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifdef</a> vsh [vsh code] <a href="https://wetdry.world/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a><a href="https://wetdry.world/tags/ifdef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifdef</a> fsh [fsh code] <a href="https://wetdry.world/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>so really nothing crazy here, it just allows you to have everything in one file instead of having to jump between 2 (though now that you point it out, not having the ability to set breakpoints is kind of an issue here)

наб<a href="https://social.treehouse.systems/@grawity" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@grawity</a> my anonymous dump from vetusware (that calls it "This is AT&T's swan song of UNIX, SYSVr4. The base platform here is the i386." but doesn't mention XENIX) doesn't know of any others, sys/stat.h dated 1993-01-26 says<a href="https://101010.pl/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> !defined(_POSIX_SOURCE) <a href="https://101010.pl/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> S_IFNAM 0x5000 /* XENIX special named file */ <a href="https://101010.pl/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> S_INSEM 0x1 /* XENIX semaphore subtype of IFNAM */ <a href="https://101010.pl/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> S_INSHD 0x2 /* XENIX shared data subtype of IFNAM */ <a href="https://101010.pl/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> /* !defined(_POSIX_SOURCE) */it's just really surprising because this is a whole new File Type. that i've never before seen and will likely never see and is undocumented in my SysVr4 manuals from AT&T. that API is also missing. but i suppose that's expected if it's a XENIX thing

Ariadne Conill 🐰:therian:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> <a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ska</a> oh, sure, but that isn’t incompatible with what i am saying, which is that platform-specific abstractions for code which actually needs it (such as parallel I/O) are a good thing over ifdef hell.though i have also seen in code:<a href="https://social.treehouse.systems/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> !defined(__GLIBC__) && defined(__linux__) && !defined(__ANDROID__) # define MUSL (1) <a href="https://social.treehouse.systems/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>so i am not sure we have succeeded here as much as we would like to believe we have

Begasus<a href="https://mastodon.social/tags/KTimer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KTimer</a> 24.02.2 also working fine on <a href="https://mastodon.social/tags/HaikuOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HaikuOS</a>, to bad <a href="https://mastodon.social/tags/KDE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#KDE</a> insists on forcing DBusService into the applications, patching it out works fine enough though for Haiku though (mostly). Dirty patch (for checking): // KDBusService service;Proper patch (for packaging): <a href="https://mastodon.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifndef</a> Q_OS_HAIKU KDBusService service; <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>

Ariadne Conill 🐰:therian:<pre><code>#if !defined(__XEN__) && !defined(__XEN_TOOLS__) #error "domctl operations are intended for use by node control tools only" #endif </code></pre>thanks, i hate it

jacquelines 🌟<a href="https://chaos.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifdef</a> __cplusplus extern "C" { <a href="https://chaos.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>

Hidde van der PloegIf Self._printChanges() was your best friend debugging <a href="https://mastodon.design/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SwiftUI</a> views. Go ahead and try the new Self._logChanges() instead!var body: some View { <a href="https://mastodon.design/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> DEBUG let _ = Self._logChanges() <a href="https://mastodon.design/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> // … rest of view body … }It does the exact same thing but logs at the info level to the "com.apple.SwiftUI" which is cleaner (and easier to filter) in your console ✨*In Xcode 15.1 and up

Paul Haddad :tapbots_logo:<a href="https://mastodon.social/@marcoarment" class="u-url mention" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#ifndef</a> let <a href="https://tapbots.social/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> let __auto_type const <a href="https://tapbots.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a><a href="https://tapbots.social/tags/ifndef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifndef</a> var <a href="https://tapbots.social/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> var __auto_type <a href="https://tapbots.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>

Simon B. StøvringWrapping iOS-specific code in<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> os(iOS) && !os(xrOS) ... <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>does the trick. That solves my need but it isn't intuitive for me that the compiler allows an overlap between the platforms.Thanks for the help <a href="https://mstdn.social/@adamwulf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@adamwulf</a>! 🙏

Simon B. StøvringCode wrapped in<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> os(iOS) ... <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>*is* included when compiling for visionOS but code wrapped in<a href="https://mastodon.social/tags/if" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#if</a> os(xrOS) ... <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>is *not* included when compiling for iOS.This makes it tricky to manage platform-specific code 🧐

mattst88 :gentoo: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):> <a href="https://fosstodon.org/tags/ifndef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifndef</a> NDEBUG > unsigned canary; > <a href="https://fosstodon.org/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>Oh.

Studio 8502 :verified:Not-So-Stupid C Tricks: Preprocessor BasicsThis one is especially for C newbies. I suppose most of you will already know it, so feel free to ignore it.You probably know this bit of C:<pre><code>#define PI 3.14159 </code></pre>which makes PI a preprocessor symbol that is replaced at compile time with its value. Great, that's good to have, and we all use it a lot. But what if you need a compile time symbol with a default value, but you want to be able to change it at compile time without altering the source code?Here's how you do it:<pre><code>#ifndef MY_SYMBOL #define MY_SYMBOL 0xCAFEBEEF #endif </code></pre>What this does is, the preprocessor will check if MY_SYMBOL is already defined, and only define it with the source code if it's not. You can override it at compile time by passing the compiler the <code>-DMY_SYMBOL=whatever</code> argument, usually tucked into your CFLAGS variable via Make.

screwlisp<a href="https://mastodon.sdf.org/@zoerhoff" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zoerhoff</a> <a href="https://mastodon.social/@amszmidt" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@amszmidt</a> on this note, change m 's line 90 <<< to < for /bin/sh (as on openbsd current) the other change I needed to make was to add a missing function prototype to usim's tv.c . I just wedged the tv_write() function prototype at the top of the file rather than putting it in the header. After which usim appeared to build happily. I didn't think about how it relates to the tv.h <a href="https://mastodon.sdf.org/tags/IFNDEF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IFNDEF</a> USIM_TV_H .. extern void tv_write(uint32_t, uint32_t); .. <a href="https://mastodon.sdf.org/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a> prototype. I should think more ;p

Krishean Draconis<a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bagder</a> to build <a href="https://mastodon.social/tags/trurl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#trurl</a> with msvc you need to define strncasecmp with something like<a href="https://mastodon.social/tags/ifdef" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ifdef</a> _MSC_VER <a href="https://mastodon.social/tags/define" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#define</a> strncasecmp _strnicmp <a href="https://mastodon.social/tags/endif" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#endif</a>And a few minor changes to the perl teststest.pl: replace single quotes with double quotes on lines 22,23,24 my <a href="https://mastodon.social/@out" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@out</a> = ($^O eq 'MSWin32')?`.\\trurl.exe $i 2>nul`:`./trurl $i 2>/dev/null`;Similar line for <a href="https://mastodon.social/@out" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@out</a> in test-json.plThere might be better ways to do any of this, it's just what I did to get it to work

Recent searches

Search options

Administered by:

Server stats:

#endif