Caddy 2 not built for i386?

pgf · July 21, 2020, 1:56pm

I’m guessing that the omission of i386 from the pre-built architectures in the download area is not an oversight. (I do wonder whether i386 is really less popular than some of the MIPS or PPC variants, but that’s an aside, and my gut feeling is possibly quite wrong.)

But, for those of us that have been very happily running websites on older hardware, and now need to upgrade to caddy 2, it would be nice to still have that download option. Any chance of i386 being brought back?

In absence of that, a couple of suggestions for making that regression less painful: a) Call it out early in the upgrade notes that i386 is no longer directly supported, and b) give specific instructions for building one’s own i386 binary. (I’ve found the cross-build instructions, but will need to search further to find the proper GOARCH value.

paul
(who has never built a Go application, and hopes it will be as painless as advertised.

Merith-TK · July 22, 2020, 3:51am

As someone who builds go programs a lot, their website https://golang.org will be helpful for building your own binary.

As for cross-compiling, this is a list of the values you can use to cross-compile.

gist.github.com

https://gist.github.com/asukakenji/f15ba7e588ac42795f421b48b8aede63

0-go-os-arch.md

# Go (Golang) GOOS and GOARCH

All of the following information is based on `go version go1.17.1 darwin/amd64`.

## GOOS Values

| GOOS        | Out of the Box |
| :---------- | :------------: |
| `aix`       | ✅              |
| `android`   | ✅              |

This file has been truncated. show original

1-main1.go

package main

func main() {}

2-make1.sh

#!/bin/bash

# This list is based on:
# https://github.com/golang/go/blob/master/src/go/build/syslist.go
gooses=(
    aix android darwin dragonfly freebsd hurd illumos ios js \
    linux nacl netbsd openbsd plan9 solaris windows zos
)
gooses=($(printf -- '%s\n' "${gooses[@]}" | sort))

This file has been truncated. show original

There are more than three files. show original

Also, xcaddy should be a useful tool if you have to go installed on your personal machine. If you have Linux, it should be as simple as installing the golang package from your package manager, if you have windows, head over to go’s website (linked above) and download the MSI installer and then build caddy from source according to these docs

francislavoie · July 22, 2020, 3:52am

Caddy does not require cgo (and actively avoids dependencies that would cause it to be required). Some plugins might though, but ideally they shouldn’t.

Merith-TK · July 22, 2020, 3:53am

Thanks for the clarification, will edit my post to clear that up

francislavoie · July 22, 2020, 3:54am

Also, instructions for using xcaddy are here:

I think your command would look like this, if I’m not mistaken:

GOOS=linux GOARCH=386 xcaddy build

The list of supported OS/arch combinations are here: Installing Go from source - The Go Programming Language

Merith-TK · July 22, 2020, 3:56am

yeah i just updated my post with the link

pgf · July 22, 2020, 12:00pm

Thank you both. I did manage to muddle my way through all that yesterday, partly with the help of that same list of GOOS and GOARCH values that came up while googling. Also had to figure out how to use snap for the first time (I’m on ubuntu, and go version 1.14 and above aren’t available any other way). snap was easy, but realizing that I couldn’t find go because /snap/bin wasn’t in my PATH was the part that took me a while. Sigh. Sure would have been nice if i386 were one of the pre-built caddy versions. ; - )

paul

system · October 19, 2020, 1:56pm

This topic was automatically closed after 90 days. New replies are no longer allowed.