The current process is a bit broken.  See
https://bugzilla.mozilla.org/show_bug.cgi?id=1434943 for more.  Some
people report success with the patch there, but it's not completely
ready.
On Tue, Aug 14, 2018 at 6:00 AM Will Barnz <wbarn...@gmail.com> wrote:
>
> I'm trying to build NSS 3.38. I've downloaded and installed the latest 
> Mozilla Build environment and am running the script within it.
>
> I've got multiple compilers installed as I sometimes use one for a specific 
> purpose.
>
> Borland C++ builder
> CygWin
> MinGW (Code::Blocks)
>
> and Visual Studio 2017 with the latest update (which breaks 8.1 environment 
> compatibility)
>
> I want to build it using the VC++ compiler in Visual Studio... but this is 
> what I get when I run the script:
>
> $ make nss_build_all
> expr: syntax error
> expr: syntax error
> expr: syntax error
> mkdir -p ./../nspr/WIN954.0_DBG.OBJ
> cd ./../nspr/WIN954.0_DBG.OBJ ; \
>         CC=cl CXX=cl sh ../configure \
>         --enable-win32-target=WIN95 \
>         --with-dist-prefix='$(topsrcdir)/../dist/WIN954.0_DBG.OBJ' \
>         --with-dist-includedir='$(topsrcdir)/../dist/WIN954.0_DBG.OBJ/include'
> checking build system type... i686-pc-mingw32
> checking host system type... i686-pc-mingw32
> checking target system type... i686-pc-mingw32
> checking for cl... cl
> checking for whoami... /c/WINDOWS/System32/whoami
> checking whether the C compiler works... no
> configure: error: in `/c/nss-3.38/nspr/WIN954.0_DBG.OBJ':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> make: *** [../nspr/WIN954.0_DBG.OBJ/config.status] Error 77
>
>
>
>
> any ideas? command line parameters? suggestions?
>
>
> NOTE: if this is a duplicate from me, ignore the first. I tried to post it 
> and didn't see it show up.
> --
> dev-tech-crypto mailing list
> dev-tech-crypto@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-crypto
-- 
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to