@jahway603 ok, very cool. First thing to check would be what happens when we run build.sh on FreeBSD (any version) before/after pulling in the changes from those 2 commits.
@jahway603 ok, very cool. First thing to check would be what happens when we run build.sh on FreeBSD (any version) before/after pulling in the changes from those 2 commits.
Looking at upstream, they have a regular /bin/sh build script and I've found FreeBSD to be funny & complain about the bash build scripts we're using, even after I've installed bash. Not sure why.
There's this upstream build script which we need to change for our use that deals with using clang, but I'm not sure what needs to change.
Looking at upstream, they have a regular /bin/sh build script and I've found FreeBSD to be funny & complain about the bash build scripts we're using, even after I've installed bash. Not sure why.
There's [this upstream build script](https://raw.githubusercontent.com/zcash/zcash/master/depends/packages/native_clang.mk) which we need to change for our use that deals with using clang, but I'm not sure what needs to change.
@jahway603 all modern Linux systems use bash as /bin/sh but on FreeBSD it's not bash, it's csh iirc
I remember that much from regularly running it decades ago :)
> @jahway603 all modern Linux systems use bash as /bin/sh but on FreeBSD it's not bash, it's csh iirc
I remember that much from regularly running it decades ago :)
@jahway603 it would be interesting to see how FreeBSD deals with our latest dev code. If possible, try to use gcc on FreeBSD (which I don't believe is the default)
@jahway603 it would be interesting to see how FreeBSD deals with our latest `dev` code. If possible, try to use gcc on FreeBSD (which I don't believe is the default)
Very big changes will be needed in our build system.
This code is currently on hold, some work was done on the freebsd branch : https://git.hush.is/hush/hush3/src/branch/freebsd
Very big changes will be needed in our build system.
eadc3d48f2updates a year after that upstream commit here
aac77dd284@jahway603 do you have a freebsd machine to test on or know anybody that does?
@duke I have a FreeBSD 13 VM to help me test, but also re-learning BSD since it's been decades since I've ran it on anything.
@jahway603 ok, very cool. First thing to check would be what happens when we run build.sh on FreeBSD (any version) before/after pulling in the changes from those 2 commits.
FreeBSD 12 supportto FreeBSD 12 or 13 support 2 years ago@jahway603 if you can post any details of FreeBSD (any version) building of master and what problems arise, we can try to move forward on this
Looking at upstream, they have a regular /bin/sh build script and I've found FreeBSD to be funny & complain about the bash build scripts we're using, even after I've installed bash. Not sure why.
There's this upstream build script which we need to change for our use that deals with using clang, but I'm not sure what needs to change.
@jahway603 all modern Linux systems use bash as /bin/sh but on FreeBSD it's not bash, it's csh iirc
I remember that much from regularly running it decades ago :)
@jahway603 it would be interesting to see how FreeBSD deals with our latest
devcode. If possible, try to use gcc on FreeBSD (which I don't believe is the default)This code is currently on hold, some work was done on the freebsd branch : https://git.hush.is/hush/hush3/src/branch/freebsd
Very big changes will be needed in our build system.