Wow, meanwhile hugo seems to have defeated Go's fanatical commitment to compatibility.
-
Aaargh the released binaries are dynamically linked so don't work on this weird-ass OS.
Igor, fetch the heavy duty clippers! This yak goes deeper than I thought!
-
Having a completely normal morning:
GOPATH=/tmp/oldgo GOCACHE=/tmp/oldgocache steam-run ../../go/bin/go build -o hugo -tags extended .
It's somehow finding packages that use io/fs when I do this, which doesn't bode _super_ well, but let's see...
-
jfc this dependency stack is deep, why is it compiling OpenAPI specs for Google
-
Okay well that super didn't work, and fucking opentelemetry is somehow involved, as fucking usual.
IT'S FINE it's fine I just wanted to publish a little blog post but it's fine, where's that old debian VM...
-
@danderson Ugh. Once you touch any of that nonsense you're down the rabbit hole. Not even once.
-
@creachadair I just need this nonsense to work _once_, so that I can compile a static binary and then never think about it ever again. Alas, I am being foiled, so far.
-
haha fml, I was off by a few months in history, go 1.10 doesn't support modules, I needed go 1.11.0. FINE it's fine I can do that.
-
OKAY the toolchain now works well enough to compile hugo without the stupid libsass cgo dep. Now, will it blend when I add that dep, or has libsass also made fucking incompatible changes
-
> ldd ./hugo
not a dynamic executable
> ./hugo version
Hugo Static Site Generator v0.51-DEV/extended linux/amd64 BuildDate: unknownhahaha eat shit computers, I have prevailed!
-
HAAAAAHAHAHA IT'S ALIIIIIIIVE!!
Finally, I can produce one (1) HTML for my blog. and it only took the entire morning.
-
@danderson now encase that binary in amber and you'll never have to compile it again!
-
@kajord Way ahead of you:
commit 5d106793be49d234434c8ef4e8f41c7d380ba30b (HEAD -> main)
Date: Fri Jun 7 11:51:37 2024 -0700get off the compatibiltiy treadmill
diff --git a/hugo b/hugo
new file mode 100755
index 0000000..8e7cb75
Binary files /dev/null and b/hugo differ -
Now to try deploying this. What are the odds I'm going to discover that netlify uses arm64 builders and the madness doesn't end yet
-
@danderson judging from my own struggle with deployments on netlify it's more likely they are still on x86 machines.
-
@danderson just to be clear: I mean the 32bit variant. just so you will continue to have “fun”
-
@danderson I'm feeling much better about my hugo struggles now
-
@vaurora @danderson and I had a very vague "... I should look into Hugo sometime soon", which got "nope nope nope" very quickly just about now
-
@danderson @vaurora oh, I don't doubt that, but now I seriously doubt it's part of my vaguely envisioned use case of "leave it in a corner and use it once a blue moon"