On 09/11/2021 11:51, Jan Lehnardt wrote:
Heya Joan & Dave,
I’m working my way through the Glazier readme, thanks so much for the copious
notes.
I had to change a few things to get ahead (noted below), and now I’m stuck.
# Missing PATH
I had to add this to PATH to make tool resolution work as described:
https://github.com/apache/couchdb-glazier/commit/a9499252ad767579b023c179b5da0cd81f32a91d#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5
I hope this works generally and not just for me. So far so good.
# git clone otp under cygwin
The README says to git clone in PowerShell. This has the effect that line
endings are \r\n and that doesn’t agree with the `otp_build` script.
Moving the git operations into cygwin fixes this.
Better to change the git config to not touch line endings, but you can
do it this way.
git config auto.crlf false
https://github.com/apache/couchdb-glazier/commit/51e5767bc1cfd3285c57278d5f794a93e5bd0af9#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5
# Building Erlang
Without any changes, `otp_build autoconf` fails with: ”configure: error: C
compiler cannot create executables“
In config.log I find: “LINK : fatal error LNK1181: cannot open input file
‘MSVCRT.LIB”
A half on on StackOverflow tells me I need:
export CFLAGS="-link -LIBPATH:/cygdrive/c/Program\ Files\ \(x86\)/Microsoft\
Visual\ Studio/2017/BuildTools/VC/Tools/MSVC/14.16.27023/lib/x64”
I got that to build once, but when trying to make it part of the install
instructions, I get into trouble with the configure cache, which doesn’t expect
CFLAGS and seems to come pre-filled with the OTP sources. I went through a
little back and forth trying to fix this, but ended up with \\\\\ escape issues
and gave up.
Any tips for making this work properly rather than hacking .cache files
manually?
Believe I had a patch to submit to OTP to fix this very issue, they said
they'd be willing to take it...and I never got to it. I recall it being
a patch to their autoconf source to add that path.
Best
Jan
—
Professional Support for Apache CouchDB:
https://neighbourhood.ie/couchdb-support/
24/7 Observation for your CouchDB Instances:
https://opservatory.app
On 6. Nov 2021, at 18:06, Jan Lehnardt <j...@apache.org> wrote:
Heya Joan,
thanks for the heads-up. Nick and I are tackling these this time around :)
Best
Jan
—
On 3. Nov 2021, at 08:07, Joan Touzet <woh...@apache.org> wrote:
Hello there,
Sorry, I'm unavailable to help test and vote on releases.
I took notes during the 3.2.0 release as to what was needed to do the binary
releases without me. Someone from the PMC, specifically, should pick this up
for now.
https://gist.github.com/wohali/9f159bbdb6ef2c51a50d1e2326fc1d5b
Any questions, feel free to send me a note offlist.
Cheers,
Joan "too busy for a pithy quote" Touzet
On 02/11/2021 22:00, Nick Vatamaniuc wrote:
Dear community,
I would like to propose that we release Apache CouchDB 3.2.1
Candidate release notes:
https://docs.couchdb.org/en/latest/whatsnew/3.2.html#version-3-2-1
We encourage the whole community to download and test these release
artefacts so that any critical issues can be resolved before the
release is made. Everyone is free to vote on this release, so dig
right in! (Only PMC members have binding votes, but they depend on
community feedback to gauge if an official release is ready to be
made.)
The release artefacts we are voting on are available here:
https://dist.apache.org/repos/dist/dev/couchdb/source/3.2.1/rc.1/
There, you will find a tarball, a GPG signature, and SHA256/SHA512 checksums.
Please follow the test procedure here:
https://cwiki.apache.org/confluence/display/COUCHDB/Testing+a+Source+Release
Please remember that "RC1" is an annotation. If the vote passes, these
artefacts will be released as Apache CouchDB 3.2.1
Please cast your votes now.
Thanks,
-Nick
