log☇︎
127 entries in 0.931s
asciilifeform: probably spiffiest build system i've ever used, and it ships with gnat.
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 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. ☟︎☟︎☟︎☟︎
a111: Logged on 2017-11-27 20:40 asciilifeform: currently asciilifeform is barfing over the fact that adacore's gnat is happy to build static 'independent library' .a while gpl gcc's gnat barfs
asciilifeform: currently asciilifeform is barfing over the fact that adacore's gnat is happy to build static 'independent library' .a while gpl gcc's gnat barfs ☟︎
asciilifeform: 1 ) build a gnat proj 2) gnatxref -a -aO path_where_your_ali_files_end_up yourmain.adb > xref.txt
mod6: <+asciilifeform> ( recall, you can't build gnat without gnat ) << yeah, was the reason i asked. hehe
asciilifeform: ( recall, you can't build gnat without gnat )
asciilifeform: ( how didja build gnat ? from where ? etc )
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: of clean gcc 4.9.4 from FSF to a gcc 4.9.4 that build with musl + gnat ☟︎
ave1: I can build a gnat using the sources from adacore and all is fine
asciilifeform: mod6: you may recall, that it is not possible to build gnat without... gnat
asciilifeform: it comes with adacore's gnat, but with the vanilla gnu one, you gotta build it by hand
a111: Logged on 2017-05-04 10:14 phf: afaik gnat is built as part of gcc, i.e. it's one of possible artifacts produced during gcc suite compilation, so you shouldn't have a situation of non matching versions, and if you do it's most likely not going to work right. the easiest approach is to build matching gcc/gnat into their own directory structure, and change PATH when you're working with gnat projects. i think package managers going the other way and try and carefully match gcc/gnat
phf: afaik gnat is built as part of gcc, i.e. it's one of possible artifacts produced during gcc suite compilation, so you shouldn't have a situation of non matching versions, and if you do it's most likely not going to work right. the easiest approach is to build matching gcc/gnat into their own directory structure, and change PATH when you're working with gnat projects. i think package managers going the other way and try and carefully match gcc/gnat ☟︎
a111: Logged on 2015-02-16 06:17 asciilifeform: so the 'google finds unique strings' thing, sure - can we conclude that i'm the only one alive trying to build 'gnat' on 'gentoo' ?
asciilifeform: (same problem as gcc, but difference is, gcc will -- theoretically -- build on certain other compilers, though i have nfi when anyone last attempted this. but there are not and never were any open alternatives to gnat.)
asciilifeform: to build any gnat.
asciilifeform: emacs, gcc4.9+gnat, build tools, trb, kernel.
asciilifeform: because ALL version of gcc i've been able to get a hold of, which are able to build a version of gnat i've been able to get a hold of, refuse to build gnattools (the linker) when standard lib (which dun belong on a microcontroller) is disabled.
asciilifeform: but, e.g., gnat, will ONLY BUILD USING ANOTHER GNAT
decimation: why can't you build gcc/gnat?
decimation: macports has a 'port' of gcc-gnat , but it requires an existing ada compiler to build
asciilifeform: so the 'google finds unique strings' thing, sure - can we conclude that i'm the only one alive trying to build 'gnat' on 'gentoo' ? ☟︎
asciilifeform: decimation: just for gnat to build, from source, on my particular, unremarkable gentoo box
asciilifeform: unrelated, gnat-gcc-4.6.4 does in fact build.