tmsr - Search: build gnat

diana_coman: mircea_popescu: not until I get rid of cs or move it to gnat and build it statically

asciilifeform: diana_coman: heathen sores tars do tend to contain astonishing volumes of binliquishit. ( or were you thinking of the thompsonistic trap where 'need gnat to build gnat' etc. , rather ? )

asciilifeform: http://logs.nosuchlabs.com/log/trilema/2019-08-30#1932158 << this is more or less what was done with orig. gnat. but eventually will have to be solved properly (i.e. 'here's an asm thing for $machine, with which in turn can build x...')

ave1: I updated http://ave1.org/2019/gnat-sjlj-build-project/, next will be plan for gcc genisis project.

asciilifeform: mipsism is a half-solution, of sorts, in that can build a mipsistic gnat and then will execute anywhere you can port the 12kB emu to

a111: Logged on 2019-07-17 12:25 asciilifeform: the incident where i glued together rk pilot plant, to only ~then~ find out that nobody knows when the fuck proper gnat will actually build arm binaries w/ working threading, was instructive.

a111: Logged on 2019-07-17 16:38 asciilifeform: http://btcbase.org/log/2019-07-17#1923088 << the circular situation of gnat , where 'need gnat to build gnat', is the third reason for the mips approach -- arch with 100 fixed-length instructions, simplify the eventual rewriting of backend so can ditch gcc dep.

asciilifeform: http://btcbase.org/log/2019-07-17#1923088 << the circular situation of gnat , where 'need gnat to build gnat', is the third reason for the mips approach -- arch with 100 fixed-length instructions, simplify the eventual rewriting of backend so can ditch gcc dep. ☝︎☟︎

asciilifeform: the incident where i glued together rk pilot plant, to only ~then~ find out that nobody knows when the fuck proper gnat will actually build arm binaries w/ working threading, was instructive. ☟︎

feedbot: http://ave1.org/2019/gnat-sjlj-build-project/ << ave1 -- GNAT SJLJ Build project

asciilifeform: http://btcbase.org/log/2019-06-24#1919790 << old era. afaik no one yet knows even a theoretical cure for ye olde 'to build gnat, 1st find a working gnat' headache ☝︎

mod6: so I never was able to build the ave1 musltronic tools on cuntoo, because no working gnat, I just bundled them up after I built them on a gentoo machine that had a working AdaCore 2016.

trinque: we agree. I contend that folks are going to have to build e.g. v, gnat, in order to move forward, which is why I'm asking for ebuilds

mod6: asciilifeform: I changed all of the CC, CXX, LD to point at all of the binaries located in the tarball I extracted from the build of Ave1's GNAT, like this one: /opt/20180924/x86_64-linux-musl-native/bin/gcc

bvt: also, you can't build ave1gnat from scratch on fresh adaless system because of http://btcbase.org/log/2019-04-23#1909529 - so initial gnat binary will be required (ebuilds just download binary gnat for that). ☝︎

a111: Logged on 2019-04-22 14:29 spyked: asciilifeform, unfortunately 2GB (max. supported by motherboard) might still not be enuff. ideally I would plug in ave1 gnat build and use it to build a minimal system, but will prolly have to bootstrap the whole thing on another machine.

spyked: asciilifeform, unfortunately 2GB (max. supported by motherboard) might still not be enuff. ideally I would plug in ave1 gnat build and use it to build a minimal system, but will prolly have to bootstrap the whole thing on another machine. ☟︎

asciilifeform: ( in the last iteration , the 1 that presently dun build on acct of gnat bug , you simply make any data structure you like in ada, and it persists to disk. )

hanbot: trinque, /sys fails with "/usr/gnat/vtoolsp1/vtools/cuntoo/build/sys: target is busy." lsof doesn't match anything tho.

asciilifeform: diana_coman: neato. tho i did find that the arm build won't build a x86 gnat ( still afaik mystery )

asciilifeform: strangely , the -j32 thing aint working for good chunk of the build, possibly dun apply to the bootstrap gnat..?

asciilifeform: possibly i oughta add the detail, that $item is like any other machine i/o-ism -- on bare irons, it writes to the irq table ( whatever shape that has on $irons ) , on unixen it yes uses signals, because wtf else can you do there, on (hypothetical) msdos gnat, will again write to irq table, on boxen without interrupts -- will give eggog on build, what else; etc

a111: Logged on 2019-02-12 13:12 bvt: during the gnat build, the sjlj runtime is built, so it should be possible to switch to it and test.

diana_coman: I also tend to remember asciilifeform had at some point a signed build; anyway, if it's still needed I can pack ave1's gnat, yes; possibly he'd need both the "static-only" (i.e. latest version) and some previous version

mircea_popescu: seems we're en route to discover that all gnat builds depend on ~this one bridge build~ that was done by a meanwhile dead graybeard sometime in 2001.

asciilifeform: see what happens if you snip out the aarch64 build ( whether chokes same when building x64 gnat )

asciilifeform: diana_coman: were you attempting to build ~x64~ gnat on this ? ftr i was never able to ( with classic zxc variant, this was long before the current thread )

a111: Logged on 2019-02-15 16:13 diana_coman: anyways, I'll try presently ave1's previous version i.e. http://ave1.org/2018/building-gnat-on-musl-now-with-partial-and-parallel-build-support/

diana_coman: for sanity I just checked by the way that the exact same machine DOES in fact build successfully GNAT with those same scripts without the sjlj added requirement

a111: Logged on 2018-06-03 22:27 asciilifeform: !Q later tell ave1 http://p.bvulpes.com/pastes/J7Aey/?raw=true << amd64 gnat dun build on arm64.

diana_coman: ave1 or anyone else more experienced in rebuilding ave1's gnat with a previous incarnation of same: I'm trying to build using the scripts in ada-musl-cross-2018-09-24.tgz on a machine that has as only existing and perfectly working !) gnat a previous ave1 gnat version; I ran as the readme says simply ./build-ada.sh absolute_path_to_dir but the whole thing fails because it doesn't find some libs such as libgmp.la; a closer look at the outpu

bvt: during the gnat build, the sjlj runtime is built, so it should be possible to switch to it and test. ☟︎

a111: Logged on 2019-02-05 01:00 asciilifeform: the ultimate win would be to get something other than gnat ( say, an adatron implemented in cl... ) that can build something resembling a working gnat. but sadly i suspect this is yrs away.

asciilifeform: trinque: seems to me that for nao, a working binary build of ave1-gnat gotta be included in standard cuntoo, same as working kernel etc

asciilifeform: the ultimate win would be to get something other than gnat ( say, an adatron implemented in cl... ) that can build something resembling a working gnat. but sadly i suspect this is yrs away. ☟︎

asciilifeform: theoretically it may be possible to build it with a diff adatron, but gnat is the only openly published one

asciilifeform: verisimilitude: try building ave1's , unless your iron is quite exotic you will probably find that you can build a cross-gnat that outputs bins for it.

asciilifeform: incidentally, even old-fashioned barbaric adacorpse gnat was well-behaved re '-static' flag -- there's an os that dun even support static link (crapple) and it will properly barf there, rather than silently build dynamic ( incidentally can still build a runnable ffa there, fwiw, in debug mode -- see readme.txt )

asciilifeform: trinque: configure: error: GNAT is required to build ada << unsurprising , ave1's thing only builds on existing gnat

asciilifeform: it is actually a complete proggy, correct per the ada standard, but currently doesnt build on acct of the gnat bug described in the linked thread.

billymg: hi all, this past week i've been able to take advantage of the holiday vacation time to get a local workbench set up. i now have a proper gnat so was able to build phf's vdiff. i also have my blog running locally which makes it a lot easier to work on and test changes

a111: Logged on 2018-12-03 20:52 lobbes: Since this was my first time using vtools, I used diana's "starter v" with the build.sh. Script ran fine, and vtools such as ksum are working. I installed GNAT from https://www.adacore.com/download (the x86-64 GNU Linux). I'm on my debian box, gcc version 4.9.2

lobbes: Since this was my first time using vtools, I used diana's "starter v" with the build.sh. Script ran fine, and vtools such as ksum are working. I installed GNAT from https://www.adacore.com/download (the x86-64 GNU Linux). I'm on my debian box, gcc version 4.9.2 ☟︎

phf: well, it's also a reason why bug wasn't caught in development. a sequence of wtfs: linux man page says mktemp should be 3 or more X's, so project builds on a non-musl build. meanwhile POSIX mandates there to be exactly 6 X's, so a musl build fails to produce a random string, returning instead a blank one, which is when gnat decides to not only generate a temp file but also do cleanup.

mats: depending on how that goes, i'll explore different power plants, and if THAT goes well, there's a gnat port to build future ffa-gossipd

asciilifeform: phf: at this point, if something dun build under musltronic gnat, the problem is with item, not with the gnat

asciilifeform: a Troo Eternal gnat oughta be able to build itself ad-infinitum, jumping archs as necessary

asciilifeform: it's a musltronic build, like rotor. so it builds absolutely errything that is needed for a working static elf-outputting gnat.

phf: ave1, asciilifeform or other ada specialists, how did you bootstrap a gnat on aarch64? is there some binary that's floating around (because adacore doesn't seem to have linux-aarch64 build) or is it bootstrapped using a cross compiler on a x86 linux?

ave1: asciilifeform, yes that was my first reaction too. It does does something with word copying though and also individual files can be build without any of the extra gnat checks. So maybe the ada versions can be stand-ins so long as a native asm based version has not been written.

a111: Logged on 2018-06-03 22:27 asciilifeform: !Q later tell ave1 http://p.bvulpes.com/pastes/J7Aey/?raw=true << amd64 gnat dun build on arm64.

asciilifeform: a musl-gnat is first built, using a conventional gnat; this is then installed in user homedir, placed in path, and becomes the active gnat; with which then can build musltronic proggies.

asciilifeform: diana_coman: you don't need cuntoo to build musl executables, ave1's gnat does this on an ~arbitrary linux. ( via similar method as the 2015 'rotor' item )

asciilifeform: phf: now i'm curious, what you build on that dos ( i.e. do you have gnat for dos built ?! major asciilifeform-wishlist item )

lobbesbot: ave1: Sent 5 hours and 57 minutes ago: <asciilifeform> http://p.bvulpes.com/pastes/J7Aey/?raw=true << amd64 gnat dun build on arm64.

asciilifeform: diana_coman: all you gotta do is build, then put the tarball on your rc box, extract, and add to .bashrc e.g. PATH="/home/stas/gnat/aarch64-linux-musl-native/bin/:$PATH"; export PATH and you're up & running.

trinque: I suppose I should've said instead "had there been a gnat v-tree, eucrypt would never find itself in a position where gnat had moved, and nobody can find the gnat to build eucrypt"

spyked: hey, ave1! I gave http://ave1.org/2018/building-gnat-on-musl-now-with-partial-and-parallel-build-support/ a run and I'm sad to report that it failed. attached a screenlog of the run at http://lmogo.xyz/randomio/gnat-musl-screenlog.0 (notice: file is ~5MB in size). unfortunately my hands are full now, so I've no time to dig further, but I'll provide any further info if you need.

a111: Logged on 2018-05-15 21:28 asciilifeform: diana_coman: steps to replicate: 0) on a machine WITH A WORKING GNAT (e.g. adacore's , and it must be in your path already ) 1 ) download the tarball from http://ave1.org/2018/building-gnat-on-musl-now-with-partial-and-parallel-build-support 2) unpack tarball ada-musl-cross-2018-05-15.tgz , go to the dir 3) mkdir bin << this is where the built binariola will live 4) ./build-ada.sh /home/foo/temp/ada/ada-musl-cross-2018-05-15/bin

asciilifeform: incidentally 1 other interesting auxiliary project , would be to determine what is the oldest gnat that will build ave1's generator

asciilifeform: diana_coman: steps to replicate: 0) on a machine WITH A WORKING GNAT (e.g. adacore's , and it must be in your path already ) 1 ) download the tarball from http://ave1.org/2018/building-gnat-on-musl-now-with-partial-and-parallel-build-support 2) unpack tarball ada-musl-cross-2018-05-15.tgz , go to the dir 3) mkdir bin << this is where the built binariola will live 4) ./build-ada.sh /home/foo/temp/ada/ada-musl-cross-2018-05-15/bin ☟︎

deedbot: http://ave1.org/2018/building-gnat-on-musl-now-with-partial-and-parallel-build-support/ << ave1 - Building GNAT on MUSL, now with partial and parallel build support

ave1: As far as I can see, the culprit is this part "-I/opt/gnat/lib/gcc/x86_64-pc-linux-gnu/4.9.4/rts-native/adalib /opt/gnat/lib/gcc/x86_64-pc-linux-gnu/4.9.4/rts-native/adalib/../adainclude", It contains a space in the "-I", so now gnatmake thinks it needs to build an "adainclude" which will fail. I'll look into how these vars a set. (It's the ADA_INCLUDES flag in the makefile).

ave1: asciilifeform: the exact same line in my build output shows almost the same -I directories, except all end with adalib/../adainclude, that last part '../adainclude' seems to be missing on your side. I will start a rebuild with some extra logging on that line. I will get back to it tomorrow. In the mean time, I have only set the path to the adacore gnat tools and I do not have any other GNAT* flags or CFLAGS or LDFLAGS etc. etc.

a111: 48 results for "build gnat", http://btcbase.org/log-search?q=build%20gnat

a111: Logged on 2018-04-05 16:32 ave1: asciilifeform: http://btcbase.org/log/2018-04-05#1793119, with this script http://ave1.org/2018/building-gnat-on-musl-now-with-a-signature/ it is possible to build a cross compiler for aarch64, I will try to use this cross-compiler to then create a native compiler.

ave1: asciilifeform: http://btcbase.org/log/2018-04-05#1793119, with this script http://ave1.org/2018/building-gnat-on-musl-now-with-a-signature/ it is possible to build a cross compiler for aarch64, I will try to use this cross-compiler to then create a native compiler. ☝︎☟︎

asciilifeform: arm64 gnat does not appear to exist anywhere, nor anyone publicly mentioned having build one afaik.

hanbot: phf : installed gnat with diana_coman's help; vpatch.gpr looks alright (maybe? http://p.bvulpes.com/pastes/LwAtx/?raw=true), but vdiff.gpr won't build for me: http://p.bvulpes.com/pastes/yS82H/?raw=true

asciilifeform: but really there's no reason why a server needs unixclone os etc. build small bin with gnat, that knows how to run the nic, has basic ip stack.

a111: Logged on 2017-11-29 01:38 asciilifeform yet again, for 3rd time in 2 yrs, attempted and failed to build a 'zero foot print runtime' for gnat -- to abolish the 3MB of liquishit it shits into every executable.

asciilifeform: ( it won't build without an existing working copy of their gnat, exactly like the gcc fork's )

ave1: http://ave1.org/2018/building-gnat-on-musl-now-with-a-signature/ script to build GNAT, now with signature and the result can compile ch1

a111: Logged on 2018-01-16 13:20 ave1: I finally had some time to update the musl gnat build-script, write-up and download here: http://ave1.org/2018/building-gnat-on-musl/

ave1: I finally had some time to update the musl gnat build-script, write-up and download here: http://ave1.org/2018/building-gnat-on-musl/ ☟︎

a111: Logged on 2018-01-10 15:26 ave1: (also like gnat, gprbuild 2016 needs gprbuild to build etc)

trinque: part of the exercise will be to get a statically linked adatronic gcc, with which to build gnat from inside the musl system.

a111: Logged on 2017-12-10 02:43 asciilifeform: the sad fact re gnat is that there is no known way to build a gnat without an existing (built) gnat.

asciilifeform: ben_vulpes: if you want to use gcc's gnat, you gotta get old ( 2016 and earlier oughta work ) tarball manually, and build; or obtain the 'obsolete' gentoo ebuild.

asciilifeform: the sad fact re gnat is that there is no known way to build a gnat without an existing (built) gnat. ☟︎