summaryrefslogtreecommitdiff
path: root/pkg/awk
AgeCommit message (Collapse)Author
2025-02-07awk: 20250116hovercats
2024-08-09awk: Update to 20240728Michael Forney
2024-08-09awk: bump to 20240623hovercats
2024-05-06awk: Update to 20240422Michael Forney
2024-05-06awk: bump to 20240311-1-g2bab10bhovercats
2024-03-17awk: Build with warning flagsMichael Forney
Use C11 for noreturn to prevent warning.
2024-01-01awk: 20231228hovercats
2022-09-08awk: Update to 20220830Michael Forney
2022-02-18awk: Update to 20211208Michael Forney
2021-11-17awk: Update to 20211103Michael Forney
2021-03-02awk: Update to 20210215Michael Forney
2021-01-07awk: Update to 20210106Michael Forney
2020-12-14awk: Update to 20201208Michael Forney
2020-09-04awk: Update to 20200816Michael Forney
2020-08-11awk: Fix header dependency for renamed gram -> awkgramMichael Forney
Reported by Akira Hasegawa. Fixes #17.
2020-08-04awk: Fix for rename of gram -> awkgramMichael Forney
2020-08-04awk: Update to 20200730Michael Forney
2020-07-09awk: Update to 20200702Michael Forney
2020-06-23awk: Update to 20200612Michael Forney
2020-02-20awk: Update to 20200219Michael Forney
2020-01-29Move toolchain config into config.luaMichael Forney
2020-01-29awk: Add patch to avoid VLAMichael Forney
2019-12-09awk: Update to 20191208Michael Forney
2019-11-17Update ninja requirement to 1.8.0 and don't bother with atomic outputsMichael Forney
Since ninja 1.8.0[0] and samurai 0.2[1], output mtime is always recorded after a job succeeds, and outputs are considered dirty if the recorded mtime is older than any input. This means that even if a command partially writes its output then fails (for example, if run with stdout redirected to a file), it will still get re-run during the next build. This means that outputs no longer have to be written atomically (i.e. renamed into place) in order to ensure a correct build, and we can drop the idiom `command >$out.tmp && mv $out.tmp $out`. [0] https://github.com/ninja-build/ninja/commit/04d886b11041bb59d01df794cce7a1e8cad2250d [1] https://github.com/michaelforney/samurai/commit/799bc5a4719b90a1026c129b55b92c0bccf97eeb
2019-09-20awk: Update to 20190910Michael Forney
2019-08-13awk: Update to latest gitMichael Forney
2019-03-19Rename rev to ver, and keep track of package versions as wellMichael Forney
2019-03-03awk: Update to latest gitMichael Forney
2018-10-23Revert accidentally updated submodule in 6673d9ab52Michael Forney
I missed one in the last commit.
2018-10-18curl: Probe for size of size_t, time_t and longMichael Forney
There are still several more SIZEOF_* constants in curl_config.h, but they seem to match for architectures we care about.
2018-08-27awk: Update to latest gitMichael Forney
2018-03-16Revert accidentally updated submodules in ↵Michael Forney
b99ef6bfc544b340d6ea0d07b82f764539cc62e9 `git commit -a` with ignored submodules strikes again. I really should report a bug about this.
2018-03-10libdrm: Check if config.video_drivers is setMichael Forney
2017-09-25Rewrite ninja generation scripts in LuaMichael Forney
2016-12-19Compress man pagesMichael Forney
2016-12-13Move {cc,cxx,ld}flags settings from toolchain to configMichael Forney
2016-12-13Move to flat package hierarchyMichael Forney
Note to self: never try to move submodules again To migrate your existing submodules (more or less): set -x set -e mkdir .git/modules/pkg for old in */*/src ; do new="pkg/${old#*/}" if ! [ -f "$old/.git" ] || [ "${old%%/*}" = pkg ] ; then continue fi git -C ".git/modules/$old" config core.worktree "../../../../../$new" rmdir "$new" mv "$old" "$new" sed -e "s,$old,$new," "$new/.git" > "$new/.git.tmp" mv "$new/.git.tmp" "$new/.git" mkdir ".git/modules/${new%/src}" mv ".git/modules/$old" ".git/modules/$new" rm "${old%/src}"/*.ninja mv "${old%/src}"/*.tar.{gz,xz,bz2} "${new%/src}/" rmdir "${old%/src}" || true done sed -e 's,^\[submodule "[^/]*/,[submodule "pkg/,' .git/config > .git/config.tmp mv .git/config.tmp .git/config
generated by cgit v1.2.3 (git 2.25.1) at 2026-02-12 11:08:58 +0000