mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

#binutils

0 posts0 participants0 posts today
Sourceware<p>The next GNU Tools Cauldron, taking place in Porto, Portugal, on September 26-28, 2025.</p><p><a href="https://inbox.sourceware.org/gcc/87o6ubhn4j.fsf@oracle.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">inbox.sourceware.org/gcc/87o6u</span><span class="invisible">bhn4j.fsf@oracle.com/</span></a><br><a href="https://gcc.gnu.org/wiki/cauldron2025" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">gcc.gnu.org/wiki/cauldron2025</span><span class="invisible"></span></a><br><a href="https://gnu-tools-cauldron.org/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">gnu-tools-cauldron.org/</span><span class="invisible"></span></a></p><p>Some <a href="https://fosstodon.org/tags/Sourceware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sourceware</span></a> Project Leadership Committee members and <span class="h-card" translate="no"><a href="https://social.sfconservancy.org/users/conservancy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>conservancy</span></a></span> staff should also be there.</p><p><a href="https://fosstodon.org/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a> <a href="https://fosstodon.org/tags/GDB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GDB</span></a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> <a href="https://fosstodon.org/tags/CGEN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CGEN</span></a> <a href="https://fosstodon.org/tags/DejaGnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DejaGnu</span></a> <a href="https://fosstodon.org/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newlib</span></a> <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a> <a href="https://fosstodon.org/tags/poke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>poke</span></a> <a href="https://fosstodon.org/tags/libabigail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libabigail</span></a> <a href="https://fosstodon.org/tags/elfutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elfutils</span></a></p>
datenwolf<p>All I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>llvm</span></a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clang</span></a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></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">#<span>squashfs</span></a> image to carry around to my various development machines.</p><p>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.</p><p>Yeah, about that. IYKYK</p>
Sun Microdevil Pte Ltd<p>Anyone 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: </p><p>Say, I have this `decode.s` file containing the following line:<br>decode: addxccc %g0, %g0, %g0</p><p>One VIS3 instruction, very simple. Then assemble it with both gcc and clang:<br>gcc -mcpu=niagara4 -c decode.s -o decode-gcc.o<br>clang -mcpu=niagara4 -c decode.s -o decode-clang.o</p><p>And now, if I run objdump on the files, the results are different:<br>decode-clang.o: file format elf64-sparc</p><p>Disassembly of section .text:</p><p>0000000000000000 &lt;decode&gt;:<br> 0: 81 b0 02 60 unknown</p><p>Compare with GCC's:<br>decode-gcc.o: file format elf64-sparc</p><p>Disassembly of section .text:</p><p>0000000000000000 &lt;decode&gt;:<br> 0: 81 b0 02 60 addxccc %g0, %g0, %g0</p><p>In both cases the binary stream is the same, but why does objdump decodes it as "unknown" with the clang-built file?</p><p>Edit: found it, seems like GCC sets something in the attribute section:</p><p>Attribute Section: gnu<br>File Attributes<br> Tag_GNU_Sparc_HWCAPS: vis3</p><p>Though as far as I can tell other than odd objump output it doesn't seem to affect binary execution, etc.</p><p><a href="https://uwu.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AskFedi</span></a> <a href="https://uwu.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binutils</span></a> <a href="https://uwu.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a> <a href="https://uwu.social/tags/SPARC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SPARC</span></a></p>
OSTechNix<p>Introduction to GNU Binutils: A Beginner's Guide <a href="https://floss.social/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binutils</span></a> <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://floss.social/tags/Assembler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Assembler</span></a> <a href="https://floss.social/tags/Linker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linker</span></a> <a href="https://floss.social/tags/Debugger" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debugger</span></a> <a href="https://floss.social/tags/ELF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ELF</span></a> <a href="https://floss.social/tags/ObjectFiles" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ObjectFiles</span></a> <a href="https://floss.social/tags/ExecutableFiles" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ExecutableFiles</span></a> <a href="https://floss.social/tags/AssemblyLanguage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AssemblyLanguage</span></a> <a href="https://floss.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opensource</span></a> <a href="https://floss.social/tags/Linuxhowto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linuxhowto</span></a> <a href="https://floss.social/tags/Linuxbasics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linuxbasics</span></a> <a href="https://floss.social/tags/Commandline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Commandline</span></a> <br><a href="https://ostechnix.com/introduction-to-gnu-binutils/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/introduction-to-</span><span class="invisible">gnu-binutils/</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>GNU <a href="https://fosstodon.org/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binutils</span></a> 2.44 is out:</p><p><a href="https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lists.gnu.org/archive/html/inf</span><span class="invisible">o-gnu/2025-02/msg00001.html</span></a></p><p>Some highlights:</p><p>* Assembler:<br> - Support for new architecture extensions for AArch64, Risc-V and x86.</p><p>* Linker:</p><p>- This now supports mixed LTO and non-LTO object files in relocatable output.<br>- The ELF forms of the linker support a --image-base=&lt;ADDR&gt; option for compatibility with LLD.</p><p>[…] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]</p>
Dan McDonald<p>Please boost this one if you can.</p><p>Anyone here a, or know a, GNU binutils wizard? ( <a href="https://hostux.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> <a href="https://hostux.social/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gnu</span></a> )</p><p>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.</p><p>I have a downloadable test tarball that'll exercise the code, broken or not, available upon request.</p><p>This MIGHT be <a href="https://hostux.social/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>illumos</span></a> , but I tested binutils 2.38 on ubuntu-22 and it passed, so I'm doubting that!</p>
Wattana<p>did you know that gnu <a href="https://toot.community/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> have support for the <a href="https://toot.community/tags/z80" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>z80</span></a>? now you do! it includes assembler, linker, ar, ranlib, and all kinds of stuff you need for a basic toolchain.</p><p>you can also use a linker script and output to a flat binary, or even use custom sections as header!</p><p><a href="https://toot.community/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>retrocomputing</span></a> <a href="https://toot.community/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a></p>
Dr. Brian Callahan<p>I updated my <a href="https://bsd.network/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gcc</span></a> tip-of-tree package for <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a>. Installs GCC 15.0.0 and <a href="https://bsd.network/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> 2.42.50 (all but ld, gold, and gdb) from about 3 hours ago. Includes compilers for Ada, C, C++, D, Fortran, Modula-2, Objective-C and Objective-C++. Only amd64 (sorry! I could probably do arm64 and riscv64 if I had fast-enough machines...).</p><p>Installs to /usr/local/gnu so it won't conflict with any other gcc packages you might have installed.</p><p><a href="https://github.com/ibara/ports/releases/download/v1.0/gcc-devel-15.0.0pl20240613p0.tgz" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/ibara/ports/release</span><span class="invisible">s/download/v1.0/gcc-devel-15.0.0pl20240613p0.tgz</span></a></p><p><a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compiler</span></a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compilers</span></a> <a href="https://bsd.network/tags/bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bsd</span></a> <a href="https://bsd.network/tags/c" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>c</span></a> <a href="https://bsd.network/tags/dlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dlang</span></a></p>
Luke T. Shumaker<p><span class="h-card" translate="no"><a href="https://mastodon.social/@amszmidt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>amszmidt</span></a></span><br>I've tracked down where *almost* all the bundled files in<br><a href="https://fosstodon.org/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> came from; pinning down </p><p>1 rev of autoconf<br>1 rev of gettext<br>1 rev of libtool<br>1 rev of readline<br>2 revs of automake<br>2 revs of GNU config<br>2 revs of texinfo<br>2 revs of gnulib<br>2 revs of zlib<br>7 revs of GCC</p><p>Still TODO: (not hard, just not done yet)</p><p>config.rpath<br>config/ChangeLog<br>config/ax_lib_socket_nsl.m4<br>config/bootstrap-hwasan.mk<br>ltmain.sh<br>readline/readline/support/config.rpath<br>readline/readline/support/mkinstalldirs</p>
Luke T. Shumaker<p>ltmain.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">#<span>GNU</span></a> <a href="https://fosstodon.org/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></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">#<span>GPLviolation</span></a> :P</p><p>(It has a --no-finish flag that no libtool sources have ever had.)</p>
Marco Ivaldi<p>Toolchain Necromancy: Past Mistakes Haunting ASLR</p><p>“Starting from 2001 and continuing until 6 years ago with version 2.32, <a href="https://infosec.exchange/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a>' ld linker set too large of an alignment on ELF binary sections. With a <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> kernel &gt;= 5.10 or glibc &gt;= 2.35, binaries/libraries that were built with the older toolchain act as timebombs against <a href="https://infosec.exchange/tags/ASLR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASLR</span></a>, making brute-force attacks easier on 64-bit binaries and reducing randomness to nothing in some cases for 32-bit binaries.”</p><p><a href="https://grsecurity.net/toolchain_necromancy_past_mistakes_haunting_aslr" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">grsecurity.net/toolchain_necro</span><span class="invisible">mancy_past_mistakes_haunting_aslr</span></a></p>
Dr. Brian Callahan<p>A new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> post appears!</p><p>Can GCC use Clang as its assembler?</p><p>Come with me on this wild ride to use <a href="https://bsd.network/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GCC</span></a> without the <a href="https://bsd.network/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> <a href="https://bsd.network/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> and instead use <a href="https://bsd.network/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>clang</span></a> and the <a href="https://bsd.network/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLVM</span></a> binutils.</p><p><a href="https://briancallahan.net/blog/20240122.html" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">briancallahan.net/blog/2024012</span><span class="invisible">2.html</span></a></p><p><a href="https://bsd.network/tags/compile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compile</span></a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compiler</span></a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compilers</span></a> <a href="https://bsd.network/tags/dlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dlang</span></a> <a href="https://bsd.network/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> <a href="https://bsd.network/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetBSD</span></a> <a href="https://bsd.network/tags/DragonFlyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DragonFlyBSD</span></a> <a href="https://bsd.network/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://bsd.network/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Solaris</span></a> <a href="https://bsd.network/tags/Illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Illumos</span></a> <a href="https://bsd.network/tags/Unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unix</span></a> <a href="https://bsd.network/tags/program" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>program</span></a> <a href="https://bsd.network/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://bsd.network/tags/programmer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programmer</span></a> <a href="https://bsd.network/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>code</span></a> <a href="https://bsd.network/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coding</span></a></p>
Dr. Frog<p>I'm looking for a new <a href="https://mas.to/tags/gnutools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gnutools</span></a> job; long story short, my current employer is pushing me to retire early as part of a division-wide "reorganization", but I want to keep working. I'm a current <a href="https://mas.to/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gcc</span></a> and <a href="https://mas.to/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> maintainer and have also contributed to <a href="https://mas.to/tags/gdb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gdb</span></a>, <a href="https://mas.to/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a>, <a href="https://mas.to/tags/newlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>newlib</span></a>, and <a href="https://mas.to/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qemu</span></a>. Lately I've been working on adding GCC front-end support for <a href="https://mas.to/tags/openmp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openmp</span></a>, but I've also done back-end things for multiple architectures, and I write documentation. DM me for more details and contact info.</p>
Free Software Foundation<p>GNU 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">#<span>Binutils</span></a>, <a href="https://hostux.social/tags/Coreutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Coreutils</span></a>, <a href="https://hostux.social/tags/Emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Emacs</span></a>, <a href="https://hostux.social/tags/Gama" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gama</span></a>, <a href="https://hostux.social/tags/Glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Glibc</span></a>, <a href="https://hostux.social/tags/Lilypond" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lilypond</span></a>, "LinuxLibre <a href="https://hostux.social/tags/Poke" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Poke</span></a>, and more. Full details: <a href="https://u.fsf.org/40h" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">u.fsf.org/40h</span><span class="invisible"></span></a> Big thanks to @bandali0 <span class="h-card"><a href="https://mastodon.sdf.org/@bandali" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bandali</span></a></span>, all the devs, and other contributors!</p>
GCC - GNU Toolchain<p>GNU <a href="https://fosstodon.org/tags/Binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binutils</span></a> BFD Linker joins the linker performance challenge. Thanks to Michael Matz of <br><span class="h-card"><a href="https://fosstodon.org/@SUSE" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SUSE</span></a></span> . <a href="https://www.youtube.com/watch?v=h5pXt_YCwkU" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=h5pXt_YCwk</span><span class="invisible">U</span></a></p>
Dr. Brian Callahan<p>A new <a href="https://bsd.network/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> post appears!</p><p>Can <a href="https://bsd.network/tags/mold" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mold</span></a> be used as the <a href="https://bsd.network/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> system <a href="https://bsd.network/tags/linker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linker</span></a>? Let's find out!</p><p><a href="https://briancallahan.net/blog/20230813.html" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">briancallahan.net/blog/2023081</span><span class="invisible">3.html</span></a></p><p><a href="https://bsd.network/tags/program" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>program</span></a> <a href="https://bsd.network/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://bsd.network/tags/ld" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ld</span></a> <a href="https://bsd.network/tags/linkers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linkers</span></a> <a href="https://bsd.network/tags/compiler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compiler</span></a> <a href="https://bsd.network/tags/compilers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compilers</span></a> <a href="https://bsd.network/tags/programminglanguage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programminglanguage</span></a> <a href="https://bsd.network/tags/programminglanguages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programminglanguages</span></a> <a href="https://bsd.network/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://bsd.network/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>netbsd</span></a> <a href="https://bsd.network/tags/dragonflybsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dragonflybsd</span></a> <a href="https://bsd.network/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://bsd.network/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://bsd.network/tags/toolchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toolchain</span></a> <a href="https://bsd.network/tags/toolchains" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toolchains</span></a> <a href="https://bsd.network/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>llvm</span></a> <a href="https://bsd.network/tags/lld" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lld</span></a> <a href="https://bsd.network/tags/gnu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gnu</span></a> <a href="https://bsd.network/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a></p>
Felix Palmen 📯<p>We have <a href="https://techhub.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a>, <a href="https://techhub.social/tags/zlib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zlib</span></a>, <a href="https://techhub.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a>, <a href="https://techhub.social/tags/gmp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gmp</span></a>, <a href="https://techhub.social/tags/mpfr" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mpfr</span></a> and <a href="https://techhub.social/tags/mpc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mpc</span></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">#<span>gcc</span></a> for C and C++. Oh wow. Now, trying to create *this* port 😎</p><p>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 🙈</p>
Felix Palmen 📯<p>This feature-branch finally starts to look somewhat promising, just added native <a href="https://techhub.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://techhub.social/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> <a href="https://techhub.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> for <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a>'s <a href="https://techhub.social/tags/Linuxulator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linuxulator</span></a> 😎</p><p>linux_base-dirs is a tiny metaport just owning ${LINUXBASE} and a few essential subdirs.</p><p>Everything prefixed "lxcross-" is part of the cross-toolchain and installed to ${LXCROSSBASE}, defaulting to ${LOCALBASE}/linux-cross.</p><p>Everything suffixed "-bootstrap" is some minimal/temporary port needed to build the full cross-toolchain and installed to ${LXBOOTSTRAP}, defaulting to ${LXCROSSBASE}/bootstrap.</p><p>Everything prefixed "linux-" is Linux-native and installed to ${LINUXBASE}.</p><p>linuxheaders44 just contains the headers from Linux-4.4.x, installed to ${LINUXBASE} but coming with a slave-port installing to ${LXCROSSBASE} for the cross toolchain.</p><p>Next step: GNU gmp! Let's see 😎</p>
Felix Palmen 📯<p>I'm carefully optimistic now again 😎</p><p>After first building very basic/limited "-bootstrap" versions of binutils and gcc into a separate prefix, it seems I could finally build a complete <a href="https://techhub.social/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> cross (<a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> -&gt; <a href="https://techhub.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>) toolchain, including <a href="https://techhub.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a>, <a href="https://techhub.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>glibc</span></a> and <a href="https://techhub.social/tags/gcc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gcc</span></a> (with libstdc++). This final cross gcc at least passed the most basic sanity check -- it successfully compiles an empty program 🙈</p><p>Now doing a bit of cleanup and then trying whether this beast is able to build the *real* (native) glibc for a new <a href="https://techhub.social/tags/Linuxulator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linuxulator</span></a> userland 😎</p>
PulkoMandy<p>Ok let's port <a href="https://mastodon.tetaneutral.net/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binutils</span></a> to the unsp CPU used in the <a href="https://mastodon.tetaneutral.net/tags/VTech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VTech</span></a> <a href="https://mastodon.tetaneutral.net/tags/VSmile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VSmile</span></a> !<br>Apparently this starts by building a version of autoconf from 11 years ago, otherwise you can't regenerate the configure scripts (which need to be modified to add a new target)</p>