514 entries in 0.689s
trinque: obviously there are other problems. if you want
musl, you need ebuilds with
musl patches. as it stands on stock gentoo, this means using "layman" which for the
musl overlay, eats directly from shithub
diana_coman: asciilifeform, ave1 did you succeed building gnat on non-
musl gentoo?
a111: Logged on 2018-05-05 06:48 lobbes: ls: cannot access toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-g++: No such file or directory
lobbes: ls: cannot access toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-g++: No such file or directory
☟︎ mod6: lobbes: if you are still in the `bitcoin/build' directory, what does `ls -al toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-g++` return?
ave1: Yes I have developed and run this on a computer without
musl ave1: it's part of the cross compiler (under aarch64-linux-
musl/aarch64-linux-
musl/lib directory). The compilers assume it will live under /lib/ld.so, so that part won't work on glibc machines
ave1: BTW although it does build code based on shared libraries, this code needs the
musl "ld.so" to live at a specific place, so that does not work.
mircea_popescu: so, tmsr-kernel, such as for instance the very tight
musl stuff, or what cuntoo evnetually will become, is out of scope for this discussion. of course it should have native fg handling, and im sure it will.
BingoBoingo: My impressions of the gentoo thus far are that is very much a "some assembly required" product. This has up and down sides which is why eventually we will need to specify something narrower than Gentoo. I look forward to
musl'd up cuntoo.
trinque is on a box currently that's
musl + libressl, but I don't know that it's much better
mircea_popescu: anyway, let's restate : "since you're stuck with a c library anyway as long as you're on c-machine, at the very least to do init and end ; and since
musl is not that terrible and only links what you use anyway ; just use it and be done with the headache -- the alternative is bloating ada with nonsense"
ave1: So as long as the
MUSL C library development stays sane, I would say follow it.
ave1: And if you want to do this for a C program, you will end up with much the same code as
MUSL.
mimisbrunnr: Logged on 2018-03-29 08:15 ave1: For
musl the initialization / finalization part is minimal and easy to read, for gnu lib C it is not and part of it used code from the dynamic linking library.
ave1:
http://btcbase.org/log/2018-03-29#1790899, I'm saying use the
musl C library for the "no C library on a C machine", if you do all the things it does yourself, you get the same kind of code. For example, you could do this all in ADA but you'll still have to shuffle pointers around and get this "unsafe" but it's written in Ada code.
☝︎ mimisbrunnr: Logged on 2018-03-29 08:15 ave1: For
musl the initialization / finalization part is minimal and easy to read, for gnu lib C it is not and part of it used code from the dynamic linking library.
lobbesbot: mircea_popescu: Sent 6 hours and 18 minutes ago: <ave1> re:
http://btcbase.org/log/2018-03-28#1790127, not close at all. I do have a script to make a
musl C library based ada (and one with a minimal Ada library). No C library only makes sense for systems without an OS.
ave1: For
musl the initialization / finalization part is minimal and easy to read, for gnu lib C it is not and part of it used code from the dynamic linking library.
ave1: Note that if you use the
musl c library, you will only get the parts from the C library you actually use in your binary. (this is not true for gnu C library)
ave1: !Qlater tell mircea_popescu re:
http://btcbase.org/log/2018-03-28#1790127, not close at all. I do have a script to make a
musl C library based ada (and one with a minimal Ada library). No C library only makes sense for systems without an OS.
☝︎ ave1: !~later tell mircea_popescu re:
http://btcbase.org/log/2018-03-28#1790127, not close at all. I do have a script to make a
musl C library based ada (and one with a minimal Ada library). No C library only makes sense for systems without an OS.
☝︎ trinque: diana_coman tried to build a cuntoo per my recipe and was bitten by the upstream
musl-overlay gentoo repository having shifted enough to break the build.
trinque doesn't recall that anybody but danielpbarron used his standard
musl gentoo.
BingoBoingo: !~later tell mircea_popescu a
MUSL box is now ready to plug in and serve a form of Qntra... after a weekend of head banging
ave1: asciilifeform, yes! also on gnat for
musl...
BingoBoingo: Anyways
musl servering is going well, building a trb on the box because gotta test for republican standards compliance.
BingoBoingo: Wire is expected to hit the datacenter account Monday. This weekend configuring and double checking the configuring of the switch and the
musl Qntra
BingoBoingo: In other news, signing contracts Monday in the afternoon. This weekendś adventure setting up a
MUSL webserver for Qntra.
spyked: mircea_popescu, I wanna first get a working item (js highlighting for trilema anchors) then make everything link into a static binary, then post them. as they are right now, I expect them to be unusable on many systems (e.g.
musl-gentoo).
ave1: the adacore diff also includes previous 4.9.4 patches for
musl ave1: I fixed the link, the "gcc-4.9.adacore2016-
musl.diff" and "gprbuild-gpl-2017-src-
musl.diff" are mine, the others came from
musl-cross
trinque: yeah I dunno I want to digest this in present form. would be nice to know which items came from where in "
musl-cross" and which were edited by ave1
BingoBoingo: Find fab that has 14-22 nm process, make simple multicore MIPS and a
MUSL'd cuntoo for it
mod6 is looking at the
musl overlay
trinque: the mere act of producing a booting gentoo is trivial; what we need is a genesis of a ports tree merged between the
musl overlay and a particular vintage of portage.
trinque: must be organ-chopping week. first trb wallet, now
musl dynloader and gcc linker
trinque: part of the exercise will be to get a statically linked adatronic gcc, with which to build gnat from inside the
musl system.
trinque spent yesterday stepping a
musl build from gcc 6 -> 5 -> 4
trinque: heh, in other peasant huts, cannot build gcc 4.9.4 from 6.4.0 on gentoo
musl, gotta step to 5.4.0 first.
trinque: I'm over here dusting off the
musl gentoo recipe to produce same.
trinque: eh why not use
musl anyway
trinque: which, gentoo
musl overlay is a git repo somewhere. whole thing would have to be repo'd for cuntoo
mike_c: it is using /var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-g++, so I guess it exists..
mike_c: it's looking for x86_64-therealbitcoin-linux-
musl-gcc, which doesn't exist
mod6: for instance, i think that to be: bitcoin/build/toolchain/usr/x86_64-therealbitcoin-linux-
musl/bin
mike_c: CC =/var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-gcc
mod6: phf: <+mike_c> this exists: /var/trb/trb54/bitcoin/build/toolchain/usr/x86_64-therealbitcoin-linux-
musl phf: mike_c: does this exist /var/trb/trb54/bitcoin/build/toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-gcc ?
mike_c: this exists: /var/trb/trb54/bitcoin/build/toolchain/usr/x86_64-therealbitcoin-linux-
musl phf: erll, quite obviously for the makefile to work you have to have a file "toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-gcc" relative to where you're calling "make" from
phf: export CC=$(shell readlink -f toolchain/usr/bin/x86_64-therealbitcoin-linux-
musl-gcc)
ave1: hmm, the
musl-cross repository was hg but should not be needed, will remove
ave1: after 3 hours or so, you'll have a tar file there with static gcc/gnat tools that are all based on
musl a111: Logged on 2017-07-19 13:21 ave1: of clean gcc 4.9.4 from FSF to a gcc 4.9.4 that build with
musl + gnat
ave1: will do, I will probably create version of musl_cross that does all this
ave1: if you get musl_cross, and replace the gcc-4.9.4-
musl.diff therein with this one
ave1: of clean gcc 4.9.4 from FSF to a gcc 4.9.4 that build with
musl + gnat
☟︎ ave1: ok, this is the diff (also contains
musl diffs from musl_cross)
ave1: p.s I already have a
musl build for x86_64 (based on musl_cross) (works on adacore stuff and gcc-4.9.4), but is needs some more work
mod6: ah, herp. missed that part about the statics &
musl trinque: re:
musl and X, you have to tell it in xorg.conf what order to load modules in. had this for intel, but don't know the proper incantation yet for amd/ati
trinque: also have an apu2 on the way which will be a dedicated gentoo+
musl. I'll write up the unboxing and gentooing of that guy when it arrives.
trinque: I dug a glibc trench for now while I fiddle with
musl+X
trinque:
musl and x11 are angry at each other yet, something to do with the way x11 loads modules
trinque: mostly, it's 1) start from a musltronic stage3 (they're present on the mirrors in iirc "experimental") and 2) install layman, add
musl overlay
trinque: aha, asciilifeform,
musl defines the flag only, in include/sys/socket.h:262
trinque:
musl's probably defining the thing in net.h or w/e it was
mircea_popescu: i think we're not talking of the same thing. so, i have, for the sake of argument, a 50k line bcc, which builds c and doesn't optimize. it's my bootstrapping compiler. it runs on
musl, say. i fire up a pogo, put this on, and proceed to build a kernel during the next week.
mircea_popescu: certainly the btc
musl thing is a major cornerstone in that vein.