Try: cargo install cbindgen

On Sat, Dec 29, 2018, 16:45 <ch...@christopherlindsey.com wrote:

> Hi,
>
> I'm trying to set up a development environment for Thunderbird for the
> first time and am following the instructions for a Windows machine at:
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Thunderbird_build
>
> I've been searching everywhere I could think of for a solution to the
> below error with no success and I'm not sure where to go from here.
>
> Any suggestions?
>
> Thank you,
> Chris
>
>
>
> $ ./mach build
>  Config object not found by mach.
>  0:24.82 Clobber not needed.
>  0:24.89 Adding make options from f:\mozilla-source\mozconfig
>     MOZ_OBJDIR=f:/mozilla-source/obj-i686-pc-mingw32
>     OBJDIR=f:/mozilla-source/obj-i686-pc-mingw32
>     FOUND_MOZCONFIG=f:/mozilla-source/mozconfig
>     export FOUND_MOZCONFIG
>  0:27.13 c:\mozilla-build\bin\mozmake.EXE -f client.mk -s configure
>  0:27.91 cd f:/mozilla-source/obj-i686-pc-mingw32
>  0:28.11 f:/mozilla-source/configure
>  0:31.84 Creating Python environment
>  1:35.19 New python executable in
> f:\mozilla-source\obj-i686-pc-mingw32\_virtualenvs\init\Scripts\python2.7.exe
>  1:35.20 Not overwriting existing python script
> f:\mozilla-source\obj-i686-pc-mingw32\_virtualenvs\init\Scripts\python.exe
> (you must use
> f:\mozilla-source\obj-i686-pc-mingw32\_virtualenvs\init\Scripts\python2.7.exe)
>  1:35.20 Installing setuptools, pip, wheel...done.
>  1:38.69 f:\mozilla-source\python\mozbuild\mozbuild\virtualenv.py:410:
> UserWarning: Hacking environment to allow binary Python extensions to
> build. You can make this warning go away by installing Visual Studio 2008.
> You can download the Express Edition installer from
> http://go.microsoft.com/?linkid=7729279
>  1:38.70   warnings.warn('Hacking environment to allow binary Python '
>  1:38.72 Reexecuting in the virtualenv
>  1:42.14 Adding configure options from f:\mozilla-source\mozconfig
>  1:42.26   --enable-application=comm/mail
>  1:42.34   --enable-calendar
>  1:42.37 checking for vcs source checkout... hg
>  1:44.63 checking for a shell... C:/mozilla-build/msys/bin/sh.exe
>  1:49.84 checking for host system type... i686-pc-mingw32
>  1:49.84 checking for target system type... i686-pc-mingw32
>  1:50.52 checking whether cross compiling... no
>  1:52.30 checking for the target C compiler...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/cl.exe
>  1:54.83 checking whether the target C compiler can be used... yes
>  1:57.10 checking for Python 3... C:/mozilla-build//python3/python3.exe
> (3.6.5)
>  1:57.11 checking for hg... c:/mozilla-build/python/Scripts/hg.exe
>  1:58.79 checking for Mercurial version... 4.5.3
>  1:59.56 checking for sparse checkout... no
>  1:59.65 checking for pkg_config... not found
>  1:59.69 checking for yasm... c:/mozilla-build/bin/yasm.exe
>  2:00.17 checking yasm version... 1.3.0
>  2:00.25 checking for nasm... not found
>  2:00.34 checking the target C compiler version... 19.16.27025
>  2:02.86 checking the target C compiler works... yes
>  2:02.90 checking for the target C++ compiler...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/cl.exe
>  2:03.79 checking whether the target C++ compiler can be used... yes
>  2:03.82 checking the target C++ compiler version... 19.16.27025
>  2:04.63 checking the target C++ compiler works... yes
>  2:04.63 checking for the host C compiler...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/cl.exe
>  2:05.01 checking whether the host C compiler can be used... yes
>  2:05.08 checking the host C compiler version... 19.16.27025
>  2:05.41 checking the host C compiler works... yes
>  2:05.41 checking for the host C++ compiler...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/cl.exe
>  2:05.68 checking whether the host C++ compiler can be used... yes
>  2:05.69 checking the host C++ compiler version... 19.16.27025
>  2:06.00 checking the host C++ compiler works... yes
>  2:06.58 checking for 64-bit OS... no
>  2:06.66 checking for llvm_profdata... not found
>  2:14.45 checking for Windows SDK... 0x0a00 in 'C:\Program Files
> (x86)\Windows Kits\10\'
>  2:14.59 checking for Universal CRT SDK... 10.0.17763.0 in 'C:\Program
> Files (x86)\Windows Kits\10\'
>  2:14.61 checking for the Debug Interface Access SDK...
> C:\PROGRA~2\MICROS~2\2017\COMMUN~1\DIA SDK
>  2:14.75 checking for mt...
> C:/PROGRA~2/WI3CF2~1/10/bin/100177~1.0/x64/mt.exe
>  2:15.35 checking whether MT is really Microsoft Manifest Tool... yes
>  2:15.45 checking for linker...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/link.exe
>  2:15.57 checking for host_linker...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/link.exe
>  2:15.59 checking for makecab... c:/WINDOWS/System32/makecab.exe
>  2:16.68 checking for the assembler...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/ml.exe
>  2:17.01 checking whether the C compiler supports
> -fsanitize=fuzzer-no-link... yes
>  2:17.12 checking for rc...
> C:/PROGRA~2/WI3CF2~1/10/bin/100177~1.0/x64/rc.exe
>  2:17.19 checking for ar...
> C:/PROGRA~2/MICROS~2/2017/COMMUN~1/VC/Tools/MSVC/1416~1.270/bin/HostX64/x86/lib.exe
>  2:17.67 checking for stdint.h... yes
>  2:18.42 checking for inttypes.h... yes
>  2:19.36 checking for malloc.h... yes
>  2:19.99 checking for alloca.h... no
>  2:20.27 checking for perf_event_open system call... no
>  2:21.21 checking for llvm-config... not found
>  2:21.25 checking bindgen cflags... -x c++ -std=gnu++14
> -fno-sized-deallocation -DTRACING=1 -DIMPL_LIBXUL -DMOZILLA_INTERNAL_API
> -DRUST_BINDGEN -DOS_WIN=1 -DWIN32=1
>  2:21.34 checking for rustc... c:/Users/calindsey/.cargo/bin/rustc.exe
>  2:21.42 checking for cargo... c:/Users/calindsey/.cargo/bin/cargo.exe
>  2:33.06 checking rustc version... 1.31.1
>  2:34.43 checking cargo version... 1.31.0
>  2:46.95 checking for rustdoc... c:/Users/calindsey/.cargo/bin/rustdoc.exe
>  2:47.00 checking for cbindgen... not found
>  2:47.00 DEBUG: cbindgen: Trying cbindgen
>  2:47.02 DEBUG: cbindgen: Trying c:/Users/calindsey/.cargo/bin/cbindgen
>  2:47.02 ERROR: Cannot find cbindgen
>  2:47.24 *** Fix above errors and then restart with\
>  2:47.24                "./mach build"
>  2:47.27 mozmake.EXE: *** [client.mk:115: configure] Error 1
> _______________________________________________
> dev-builds mailing list
> dev-builds@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-builds
>
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds

Reply via email to