MastodonTech.de

SourcewareThe next GNU Tools Cauldron, taking place in Porto, Portugal, on September 26-28, 2025.<a href="https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/" rel="nofollow noopener" translate="no" target="_blank">https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/</a> <a href="https://gcc.gnu.org/wiki/cauldron2025" rel="nofollow noopener" translate="no" target="_blank">https://gcc.gnu.org/wiki/cauldron2025</a> <a href="https://gnu-tools-cauldron.org/" rel="nofollow noopener" translate="no" target="_blank">https://gnu-tools-cauldron.org/</a>Some <a href="https://fosstodon.org/tags/Sourceware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sourceware</a> Project Leadership Committee members and <a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener" target="_blank">@conservancy</a> staff should also be there.<a href="https://fosstodon.org/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> <a href="https://fosstodon.org/tags/GDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#GDB</a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://fosstodon.org/tags/CGEN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGEN</a> <a href="https://fosstodon.org/tags/DejaGnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#DejaGnu</a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#newlib</a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/poke" class="mention hashtag" rel="nofollow noopener" target="_blank">#poke</a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#libabigail</a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#elfutils</a>

datenwolfAll I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#squashfs</a> image to carry around to my various development machines.You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.Yeah, about that. IYKYK

AptiviLinux 6.16 will need GCC 8 and Binutils 2.30 to build.<a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernel</a> <a href="https://mastodon.social/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://mastodon.social/tags/Computers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computers</a> <a href="https://mastodon.social/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptops</a> <a href="https://mastodon.social/tags/TechNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechNews</a> <a href="https://mastodon.social/tags/TechUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechUpdates</a> <a href="https://mastodon.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> <a href="https://mastodon.social/tags/Clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Clang</a> <a href="https://mastodon.social/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> <a href="https://mastodon.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a><a href="https://officialaptivi.wordpress.com/2025/06/01/linux-6-16-needs-gcc-8-and-binutils-2-30/" rel="nofollow noopener" translate="no" target="_blank">https://officialaptivi.wordpress.com/2025/06/01/linux-6-16-needs-gcc-8-and-binutils-2-30/</a>

AptiviLinux 6.16 needs GCC 8 and Binutils 2.30The upcoming version of Linux now needs at least GCC 8 and GNU Binutils 2.30 to be able to successfully build, because this was needed to remove all legacy code that provided workarounds for build systems prior to GCC 8, which became a maintenance burden. Previously, GCC 5 and Binutils 2.25 were required to build Linux, and the latest version, 6.15, had this requirement before 6.16 increased it.GCC 8 and Binutils 2.30 brought new features that Linux 6.16 needed, while LLVM Clang 13 was the minimum requirement for Linux in case you’ll need to use LLVM instead of the legacy GCC.You can see the merge request below. <a class="" href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dee264c16a6334dcdbea5c186f5ff35f98b1df42" rel="nofollow noopener" target="_blank">See merge request</a> The reasoning for this minimum version requirement bump is here:<blockquote>x86 already uses gcc-8 as the minimum version, this changes all other architectures to the same version. gcc-8 is used is Debian 10 and Red Hat Enterprise Linux 8, both of which are still supported, and binutils 2.30 is the oldest corresponding version on those.Ubuntu Pro 18.04 and SUSE Linux Enterprise Server 15 both use gcc-7 as the system compiler but additionally include toolchains that remain supported.With the new minimum toolchain versions, a number of workarounds for older versions can be dropped, in particular on x86_64 and arm64. Importantly, the updated compiler version allows removing two of the five remaining gcc plugins, as support for sancov and structeak features is already included in modern compiler versions.I tried collecting the known changes that are possible based on the new toolchain version, but expect that more cleanups will be possible.Since this touches multiple architectures, I merged the patches through the asm-generic tree.”</blockquote><a href="https://www.pexels.com/photo/woman-wearing-tank-top-sitting-by-the-window-920381/" rel="nofollow noopener" target="_blank">Photo by Andrea Piacquadio</a><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/binutils/" target="_blank">#Binutils</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/gcc/" target="_blank">#GCC</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a>

BSI WID Advisories Feed<a href="https://social.adlerweb.info/tags/BSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSI</a> WID-SEC-2025-1157: [NEU] [mittel] <a href="https://social.adlerweb.info/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>: Mehrere Schwachstellen ermöglichen CodeausführungEin lokaler Angreifer kann mehrere Schwachstellen in binutils ausnutzen, um beliebigen Programmcode auszuführen.<a href="https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-1157" rel="nofollow noopener" translate="no" target="_blank">https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-1157</a>

Sun Microdevil Pte LtdAnyone here familiar with SPARC binutils internals? I'm having a rather odd case where the same instruction (and same binary sequence) gets interpreted differently depending on who compiles it :cirnothinking: Say, I have this `decode.s` file containing the following line: decode: addxccc %g0, %g0, %g0One VIS3 instruction, very simple. Then assemble it with both gcc and clang: gcc -mcpu=niagara4 -c decode.s -o decode-gcc.o clang -mcpu=niagara4 -c decode.s -o decode-clang.oAnd now, if I run objdump on the files, the results are different: decode-clang.o: file format elf64-sparcDisassembly of section .text:0000000000000000 <decode>: 0: 81 b0 02 60 unknownCompare with GCC's: decode-gcc.o: file format elf64-sparcDisassembly of section .text:0000000000000000 <decode>: 0: 81 b0 02 60 addxccc %g0, %g0, %g0In both cases the binary stream is the same, but why does objdump decodes it as "unknown" with the clang-built file?Edit: found it, seems like GCC sets something in the attribute section:Attribute Section: gnu File Attributes Tag_GNU_Sparc_HWCAPS: vis3Though as far as I can tell other than odd objump output it doesn't seem to affect binary execution, etc.<a href="https://uwu.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskFedi</a> <a href="https://uwu.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a> <a href="https://uwu.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> <a href="https://uwu.social/tags/SPARC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPARC</a>

OSTechNixIntroduction to GNU Binutils: A Beginner's Guide <a href="https://floss.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://floss.social/tags/Assembler" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembler</a> <a href="https://floss.social/tags/Linker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linker</a> <a href="https://floss.social/tags/Debugger" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debugger</a> <a href="https://floss.social/tags/ELF" class="mention hashtag" rel="nofollow noopener" target="_blank">#ELF</a> <a href="https://floss.social/tags/ObjectFiles" class="mention hashtag" rel="nofollow noopener" target="_blank">#ObjectFiles</a> <a href="https://floss.social/tags/ExecutableFiles" class="mention hashtag" rel="nofollow noopener" target="_blank">#ExecutableFiles</a> <a href="https://floss.social/tags/AssemblyLanguage" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssemblyLanguage</a> <a href="https://floss.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#Opensource</a> <a href="https://floss.social/tags/Linuxhowto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxhowto</a> <a href="https://floss.social/tags/Linuxbasics" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxbasics</a> <a href="https://floss.social/tags/Commandline" class="mention hashtag" rel="nofollow noopener" target="_blank">#Commandline</a> <a href="https://ostechnix.com/introduction-to-gnu-binutils/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/introduction-to-gnu-binutils/</a>

BSI WID Advisories Feed<a href="https://social.adlerweb.info/tags/BSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSI</a> WID-SEC-2025-0304: [NEU] [mittel] <a href="https://social.adlerweb.info/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>: Mehrere SchwachstellenEin entfernter, anonymer Angreifer kann mehrere Schwachstellen in binutils ausnutzen, um einen Denial of Service-Zustand zu erzeugen oder nicht spezifizierte Auswirkungen zu verursachen.<a href="https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0304" rel="nofollow noopener" translate="no" target="_blank">https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0304</a>

Thorsten Leemhuis (acct. 1/4)GNU <a href="https://fosstodon.org/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a> 2.44 is out:<a href="https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html" rel="nofollow noopener" translate="no" target="_blank">https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html</a>Some highlights:* Assembler: - Support for new architecture extensions for AArch64, Risc-V and x86.* Linker:- This now supports mixed LTO and non-LTO object files in relocatable output. - The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD.[…] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]

BSI WID Advisories Feed<a href="https://social.adlerweb.info/tags/BSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSI</a> WID-SEC-2025-0223: [NEU] [mittel] <a href="https://social.adlerweb.info/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>: Schwachstelle ermöglicht nicht spezifizierten AngriffEin entfernter, anonymer Angreifer kann eine Schwachstelle in binutils ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.<a href="https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0223" rel="nofollow noopener" translate="no" target="_blank">https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0223</a>

BSI WID Advisories Feed<a href="https://social.adlerweb.info/tags/BSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSI</a> WID-SEC-2024-3470: [NEU] [mittel] <a href="https://social.adlerweb.info/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>: Schwachstelle ermöglicht Denial of ServiceEin lokaler Angreifer kann eine Schwachstelle in binutils ausnutzen, um einen Denial of Service Angriff durchzuführen.<a href="https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-3470" rel="nofollow noopener" translate="no" target="_blank">https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-3470</a>

Dan McDonaldPlease boost this one if you can.Anyone here a, or know a, GNU binutils wizard? ( <a href="https://hostux.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> <a href="https://hostux.social/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnu</a> )I have software that depends on binutils honoring the the -z/--disassemble-zeroes option. My testing indicates that starting in binutils 2.41 (extending to 2.42) that option is ignored.I have a downloadable test tarball that'll exercise the code, broken or not, available upon request.This MIGHT be <a href="https://hostux.social/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a> , but I tested binutils 2.38 on ubuntu-22 and it passed, so I'm doubting that!

Luke T. Shumakerltmain.sh isn't a source file, it's the compiled output of a bunch of m4 code from libtool. The version of ltmain.sh in <a href="https://fosstodon.org/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> does not correspond to any version of the libtool sources (release tarballs or libtool.git). We don't have the Complete Corresponding Source to binutils' ltmain.sh! <a href="https://fosstodon.org/tags/GPLviolation" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLviolation</a> :P(It has a --no-finish flag that no libtool sources have ever had.)

BSI WID Advisories Feed<a href="https://social.adlerweb.info/tags/BSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSI</a> WID-SEC-2023-2165: [UPDATE] [hoch] <a href="https://social.adlerweb.info/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>: Mehrere SchwachstellenEin entfernter, anonymer Angreifer kann mehrere Schwachstellen in binutils ausnutzen, um einen Denial of Service Angriff durchzuführen, Informationen offenzulegen oder sonstige Auswirkungen zu verursachen.<a href="https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2165" rel="nofollow noopener" translate="no" target="_blank">https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2165</a>

Dr. Brian CallahanA new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> post appears!Can GCC use Clang as its assembler?Come with me on this wild ride to use <a href="https://bsd.network/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> without the <a href="https://bsd.network/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://bsd.network/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a> and instead use <a href="https://bsd.network/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a> and the <a href="https://bsd.network/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a> binutils.<a href="https://briancallahan.net/blog/20240122.html" rel="nofollow noopener" target="_blank">https://briancallahan.net/blog/20240122.html</a><a href="https://bsd.network/tags/compile" class="mention hashtag" rel="nofollow noopener" target="_blank">#compile</a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#compiler</a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#compilers</a> <a href="https://bsd.network/tags/dlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#dlang</a> <a href="https://bsd.network/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a> <a href="https://bsd.network/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetBSD</a> <a href="https://bsd.network/tags/DragonFlyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#DragonFlyBSD</a> <a href="https://bsd.network/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://bsd.network/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a> <a href="https://bsd.network/tags/Illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#Illumos</a> <a href="https://bsd.network/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unix</a> <a href="https://bsd.network/tags/program" class="mention hashtag" rel="nofollow noopener" target="_blank">#program</a> <a href="https://bsd.network/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://bsd.network/tags/programmer" class="mention hashtag" rel="nofollow noopener" target="_blank">#programmer</a> <a href="https://bsd.network/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a> <a href="https://bsd.network/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a>

Free Software FoundationGNU Spotlight with Amin Bandali: Seventeen new GNU releases in the last month including <a href="https://hostux.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a>, <a href="https://hostux.social/tags/Coreutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coreutils</a>, <a href="https://hostux.social/tags/Emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Emacs</a>, <a href="https://hostux.social/tags/Gama" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gama</a>, <a href="https://hostux.social/tags/Glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#Glibc</a>, <a href="https://hostux.social/tags/Lilypond" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lilypond</a>, "LinuxLibre <a href="https://hostux.social/tags/Poke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Poke</a>, and more. Full details: <a href="https://u.fsf.org/40h" rel="nofollow noopener" target="_blank">https://u.fsf.org/40h</a> Big thanks to @bandali0 <a href="https://mastodon.sdf.org/@bandali" class="u-url mention" rel="nofollow noopener" target="_blank">@bandali</a>, all the devs, and other contributors!

GCC - GNU ToolchainGNU <a href="https://fosstodon.org/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#Binutils</a> BFD Linker joins the linker performance challenge. Thanks to Michael Matz of <a href="https://fosstodon.org/@SUSE" class="u-url mention" rel="nofollow noopener" target="_blank">@SUSE</a> . <a href="https://www.youtube.com/watch?v=h5pXt_YCwkU" rel="nofollow noopener" target="_blank">https://www.youtube.com/watch?v=h5pXt_YCwkU</a>

Felix Palmen 📯We have <a href="https://techhub.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a>, <a href="https://techhub.social/tags/zlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#zlib</a>, <a href="https://techhub.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>, <a href="https://techhub.social/tags/gmp" class="mention hashtag" rel="nofollow noopener" target="_blank">#gmp</a>, <a href="https://techhub.social/tags/mpfr" class="mention hashtag" rel="nofollow noopener" target="_blank">#mpfr</a> and <a href="https://techhub.social/tags/mpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#mpc</a> ... in theory everything needed to build a full-featured native <a href="https://techhub.social/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gcc</a> for C and C++. Oh wow. Now, trying to create *this* port 😎Edit: My hope is that with the --sysroot option (set to ${LINUXBASE}), this new toolchain will only ever look for libraries inside ${LINUXBASE}, avoiding weird build issues you might get when using the existing linux-c7-devtools port. Well, I'm not sure I fully understand this --sysroot magic 🙈

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#binutils