Build Fails on cbindgen Error

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Build Fails on cbindgen Error

Chris-4
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
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Build Fails on cbindgen Error

Bobby Holley-2
Try: cargo install cbindgen

On Sat, Dec 29, 2018, 16:45 <[hidden email] 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
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Build Fails on cbindgen Error

Chris-4
In reply to this post by Chris-4
On Saturday, December 29, 2018 at 5:43:43 PM UTC-7, [hidden email] 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


Hi,

Thanks Bobby!  That helped get me through the previous error.  But, I still can't get a successful build.  Below are the results of the latest attempt.

I obviously don't want to have to ask for help on every build error.  Where would be the best place for me to go to lookup what these errors are and how to resolve them?

But, if it's something obvious in my configuration, feel free to point it out.

Thanks,
Chris

 0:30.34 Clobber not needed.
 0:30.38 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:31.80 c:\mozilla-build\bin\mozmake.EXE -f client.mk -s
 1:29.87 Elapsed: 0.02s; From dist/public: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:31.34 Elapsed: 0.02s; From dist/private: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:34.36 Elapsed: 1.77s; From dist/xpi-stage: Kept 76 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:54.68 Elapsed: 19.00s; From _tests: Kept 0 existing; Added/updated 1478; Removed 0 files and 0 directories.
 2:16.72 Elapsed: 19.56s; From dist/bin: Kept 0 existing; Added/updated 2543; Removed 0 files and 0 directories.
 2:27.09 Elapsed: 57.20s; From dist/include: Kept 0 existing; Added/updated 6032; Removed 0 files and 0 directories.
 3:33.79 js/src/rust/force-cargo-library-build
 3:33.87 toolkit/library/rust/force-cargo-library-build
 4:01.74     Blocking waiting for file lock on build directory
 4:21.59    Compiling mozurl v0.0.1 (F:\mozilla-source\netwerk\base\mozurl)
 4:29.81    Compiling baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)
 4:30.33     Blocking waiting for file lock on build directory
 4:30.37 error: failed to run custom build command for `baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)`
 4:30.37 process didn't exit successfully: `f:/mozilla-source/obj-i686-pc-mingw32\release\build\baldrdash-38f50de767197ce4\build-script-build` (exit code: 101)
 4:30.37 --- stdout
 4:30.37 cargo:rerun-if-changed=baldrapi.h
 4:30.37 cargo:rerun-if-changed=f:/mozilla-source/obj-i686-pc-mingw32\js/src/rust/extra-bindgen-flags
 4:30.37 --- stderr
 4:30.37 thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'clang.dll\', \'libclang.dll\'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"', libcore\result.rs:1009:5
 4:30.37 stack backtrace:
 4:30.37    0:     0x7ffc719d3ed2 - <std::sync::mpsc::select::Select as core::fmt::Debug>::fmt::h3779cdf6deab4fb2
 4:30.37    1:     0x7ffc719bed7f - std::path::<impl core::convert::From<std::path::PathBuf> for std::ffi::os_str::OsString>::from::hef69882d0aae8fb6
 4:30.37    2:     0x7ffc719b9038 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:30.37    3:     0x7ffc719b8cf1 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:30.37    4:     0x7ffc719b989c - std::panicking::rust_panic_with_hook::h83c643dba7ec424c
 4:30.37    5:     0x7ffc719b93c3 - std::panicking::begin_panic_fmt::hdc3de53d5c0ccc24
 4:30.37    6:     0x7ffc719b92a8 - rust_begin_unwind
 4:30.37    7:     0x7ffc719edbdb - core::panicking::panic_fmt::ha79ca86aa4b70ade
 4:30.37    8:     0x7ff6e10a80c6 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:30.37    9:     0x7ff6e109a182 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:30.37   10:     0x7ffc719dfc18 - std::sync::once::Once::call_inner::h314cd51909d142ef
 4:30.37   11:     0x7ff6e116d51d - bindgen::Builder::generate::h657cfddd494ecf1a
 4:30.37   12:     0x7ff6e1097776 - core::alloc::size_align::h9cf92d476a11de20
 4:30.37   13:     0x7ff6e1091f85 - std::rt::lang_start::h4fba4b55d34bb956
 4:30.37   14:     0x7ffc719b9206 - std::panicking::update_panic_count::hf9e0b184b1baf22b
 4:30.37   15:     0x7ffc719eaa61 - _rust_maybe_catch_panic
 4:30.37   16:     0x7ffc719c8a82 - std::rt::lang_start_internal::h8f028255e9554163
 4:30.39   17:     0x7ff6e1091f72 - std::rt::lang_start::h4fba4b55d34bb956
 4:30.39   18:     0x7ff6e123ee13 - invoke_main
 4:30.39                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:30.39   19:     0x7ff6e123ee13 - invoke_main
 4:30.39                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:30.39   20:     0x7ffca1163033 - BaseThreadInitThunk
 4:30.39   21:     0x7ffca3a53690 - RtlUserThreadStart
 4:30.81 mozmake.EXE[4]: *** [f:/mozilla-source/config/rules.mk:1040: force-cargo-library-build] Error 101
 4:30.84 mozmake.EXE[3]: *** [f:/mozilla-source/config/recurse.mk:74: toolkit/library/rust/target] Error 2
 4:30.84 mozmake.EXE[3]: *** Waiting for unfinished jobs....
 4:31.34    Compiling baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)
 4:31.34    Compiling target-lexicon v0.2.0
 4:31.83 error: failed to run custom build command for `baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)`
 4:31.83 process didn't exit successfully: `f:/mozilla-source/obj-i686-pc-mingw32\release\build\baldrdash-38f50de767197ce4\build-script-build` (exit code: 101)
 4:31.83 --- stdout
 4:31.83 cargo:rerun-if-changed=baldrapi.h
 4:31.83 cargo:rerun-if-changed=f:/mozilla-source/obj-i686-pc-mingw32\js/src/rust/extra-bindgen-flags
 4:31.83 --- stderr
 4:31.83 thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'clang.dll\', \'libclang.dll\'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"', libcore\result.rs:1009:5
 4:31.83 stack backtrace:
 4:31.83    0:     0x7ffc719d3ed2 - <std::sync::mpsc::select::Select as core::fmt::Debug>::fmt::h3779cdf6deab4fb2
 4:31.83    1:     0x7ffc719bed7f - std::path::<impl core::convert::From<std::path::PathBuf> for std::ffi::os_str::OsString>::from::hef69882d0aae8fb6
 4:31.83    2:     0x7ffc719b9038 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:31.83    3:     0x7ffc719b8cf1 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:31.83    4:     0x7ffc719b989c - std::panicking::rust_panic_with_hook::h83c643dba7ec424c
 4:31.83    5:     0x7ffc719b93c3 - std::panicking::begin_panic_fmt::hdc3de53d5c0ccc24
 4:31.83    6:     0x7ffc719b92a8 - rust_begin_unwind
 4:31.83    7:     0x7ffc719edbdb - core::panicking::panic_fmt::ha79ca86aa4b70ade
 4:31.83    8:     0x7ff6e10a80c6 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:31.83    9:     0x7ff6e109a182 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:31.83   10:     0x7ffc719dfc18 - std::sync::once::Once::call_inner::h314cd51909d142ef
 4:31.83   11:     0x7ff6e116d51d - bindgen::Builder::generate::h657cfddd494ecf1a
 4:31.83   12:     0x7ff6e1097776 - core::alloc::size_align::h9cf92d476a11de20
 4:31.84   13:     0x7ff6e1091f85 - std::rt::lang_start::h4fba4b55d34bb956
 4:31.84   14:     0x7ffc719b9206 - std::panicking::update_panic_count::hf9e0b184b1baf22b
 4:31.84   15:     0x7ffc719eaa61 - _rust_maybe_catch_panic
 4:31.84   16:     0x7ffc719c8a82 - std::rt::lang_start_internal::h8f028255e9554163
 4:31.84   17:     0x7ff6e1091f72 - std::rt::lang_start::h4fba4b55d34bb956
 4:31.84   18:     0x7ff6e123ee13 - invoke_main
 4:31.84                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:31.84   19:     0x7ff6e123ee13 - invoke_main
 4:31.84                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:31.84   20:     0x7ffca1163033 - BaseThreadInitThunk
 4:31.84   21:     0x7ffca3a53690 - RtlUserThreadStart
 4:31.84 warning: build failed, waiting for other jobs to finish...
 4:31.95 error: build failed
 4:32.06 mozmake.EXE[4]: *** [f:/mozilla-source/config/rules.mk:1040: force-cargo-library-build] Error 101
 4:32.06 mozmake.EXE[3]: *** [f:/mozilla-source/config/recurse.mk:74: js/src/rust/target] Error 2
 4:32.08 mozmake.EXE[2]: *** [f:/mozilla-source/config/recurse.mk:34: compile] Error 2
 4:32.09 mozmake.EXE[1]: *** [f:/mozilla-source/config/rules.mk:424: default] Error 2
 4:32.12 mozmake.EXE: *** [client.mk:125: build] Error 2
 4:32.19 0 compiler warnings present.
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Build Fails on cbindgen Error

Bobby Holley-2
Try: ./mach bootstrap

On Sat, Dec 29, 2018, 22:05 <[hidden email] wrote:
On Saturday, December 29, 2018 at 5:43:43 PM UTC-7, [hidden email] 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


Hi,

Thanks Bobby!  That helped get me through the previous error.  But, I still can't get a successful build.  Below are the results of the latest attempt.

I obviously don't want to have to ask for help on every build error.  Where would be the best place for me to go to lookup what these errors are and how to resolve them?

But, if it's something obvious in my configuration, feel free to point it out.

Thanks,
Chris

 0:30.34 Clobber not needed.
 0:30.38 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:31.80 c:\mozilla-build\bin\mozmake.EXE -f client.mk -s
 1:29.87 Elapsed: 0.02s; From dist/public: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:31.34 Elapsed: 0.02s; From dist/private: Kept 0 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:34.36 Elapsed: 1.77s; From dist/xpi-stage: Kept 76 existing; Added/updated 0; Removed 0 files and 0 directories.
 1:54.68 Elapsed: 19.00s; From _tests: Kept 0 existing; Added/updated 1478; Removed 0 files and 0 directories.
 2:16.72 Elapsed: 19.56s; From dist/bin: Kept 0 existing; Added/updated 2543; Removed 0 files and 0 directories.
 2:27.09 Elapsed: 57.20s; From dist/include: Kept 0 existing; Added/updated 6032; Removed 0 files and 0 directories.
 3:33.79 js/src/rust/force-cargo-library-build
 3:33.87 toolkit/library/rust/force-cargo-library-build
 4:01.74     Blocking waiting for file lock on build directory
 4:21.59    Compiling mozurl v0.0.1 (F:\mozilla-source\netwerk\base\mozurl)
 4:29.81    Compiling baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)
 4:30.33     Blocking waiting for file lock on build directory
 4:30.37 error: failed to run custom build command for `baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)`
 4:30.37 process didn't exit successfully: `f:/mozilla-source/obj-i686-pc-mingw32\release\build\baldrdash-38f50de767197ce4\build-script-build` (exit code: 101)
 4:30.37 --- stdout
 4:30.37 cargo:rerun-if-changed=baldrapi.h
 4:30.37 cargo:rerun-if-changed=f:/mozilla-source/obj-i686-pc-mingw32\js/src/rust/extra-bindgen-flags
 4:30.37 --- stderr
 4:30.37 thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'clang.dll\', \'libclang.dll\'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"', libcore\result.rs:1009:5
 4:30.37 stack backtrace:
 4:30.37    0:     0x7ffc719d3ed2 - <std::sync::mpsc::select::Select as core::fmt::Debug>::fmt::h3779cdf6deab4fb2
 4:30.37    1:     0x7ffc719bed7f - std::path::<impl core::convert::From<std::path::PathBuf> for std::ffi::os_str::OsString>::from::hef69882d0aae8fb6
 4:30.37    2:     0x7ffc719b9038 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:30.37    3:     0x7ffc719b8cf1 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:30.37    4:     0x7ffc719b989c - std::panicking::rust_panic_with_hook::h83c643dba7ec424c
 4:30.37    5:     0x7ffc719b93c3 - std::panicking::begin_panic_fmt::hdc3de53d5c0ccc24
 4:30.37    6:     0x7ffc719b92a8 - rust_begin_unwind
 4:30.37    7:     0x7ffc719edbdb - core::panicking::panic_fmt::ha79ca86aa4b70ade
 4:30.37    8:     0x7ff6e10a80c6 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:30.37    9:     0x7ff6e109a182 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:30.37   10:     0x7ffc719dfc18 - std::sync::once::Once::call_inner::h314cd51909d142ef
 4:30.37   11:     0x7ff6e116d51d - bindgen::Builder::generate::h657cfddd494ecf1a
 4:30.37   12:     0x7ff6e1097776 - core::alloc::size_align::h9cf92d476a11de20
 4:30.37   13:     0x7ff6e1091f85 - std::rt::lang_start::h4fba4b55d34bb956
 4:30.37   14:     0x7ffc719b9206 - std::panicking::update_panic_count::hf9e0b184b1baf22b
 4:30.37   15:     0x7ffc719eaa61 - _rust_maybe_catch_panic
 4:30.37   16:     0x7ffc719c8a82 - std::rt::lang_start_internal::h8f028255e9554163
 4:30.39   17:     0x7ff6e1091f72 - std::rt::lang_start::h4fba4b55d34bb956
 4:30.39   18:     0x7ff6e123ee13 - invoke_main
 4:30.39                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:30.39   19:     0x7ff6e123ee13 - invoke_main
 4:30.39                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:30.39   20:     0x7ffca1163033 - BaseThreadInitThunk
 4:30.39   21:     0x7ffca3a53690 - RtlUserThreadStart
 4:30.81 mozmake.EXE[4]: *** [f:/mozilla-source/config/rules.mk:1040: force-cargo-library-build] Error 101
 4:30.84 mozmake.EXE[3]: *** [f:/mozilla-source/config/recurse.mk:74: toolkit/library/rust/target] Error 2
 4:30.84 mozmake.EXE[3]: *** Waiting for unfinished jobs....
 4:31.34    Compiling baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)
 4:31.34    Compiling target-lexicon v0.2.0
 4:31.83 error: failed to run custom build command for `baldrdash v0.1.0 (F:\mozilla-source\js\src\wasm\cranelift)`
 4:31.83 process didn't exit successfully: `f:/mozilla-source/obj-i686-pc-mingw32\release\build\baldrdash-38f50de767197ce4\build-script-build` (exit code: 101)
 4:31.83 --- stdout
 4:31.83 cargo:rerun-if-changed=baldrapi.h
 4:31.83 cargo:rerun-if-changed=f:/mozilla-source/obj-i686-pc-mingw32\js/src/rust/extra-bindgen-flags
 4:31.83 --- stderr
 4:31.83 thread 'main' panicked at 'Unable to find libclang: "couldn\'t find any valid shared libraries matching: [\'clang.dll\', \'libclang.dll\'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"', libcore\result.rs:1009:5
 4:31.83 stack backtrace:
 4:31.83    0:     0x7ffc719d3ed2 - <std::sync::mpsc::select::Select as core::fmt::Debug>::fmt::h3779cdf6deab4fb2
 4:31.83    1:     0x7ffc719bed7f - std::path::<impl core::convert::From<std::path::PathBuf> for std::ffi::os_str::OsString>::from::hef69882d0aae8fb6
 4:31.83    2:     0x7ffc719b9038 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:31.83    3:     0x7ffc719b8cf1 - std::panicking::take_hook::h28cd6f8e37a0a07d
 4:31.83    4:     0x7ffc719b989c - std::panicking::rust_panic_with_hook::h83c643dba7ec424c
 4:31.83    5:     0x7ffc719b93c3 - std::panicking::begin_panic_fmt::hdc3de53d5c0ccc24
 4:31.83    6:     0x7ffc719b92a8 - rust_begin_unwind
 4:31.83    7:     0x7ffc719edbdb - core::panicking::panic_fmt::ha79ca86aa4b70ade
 4:31.83    8:     0x7ff6e10a80c6 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:31.83    9:     0x7ff6e109a182 - <&T as core::convert::AsRef<U>>::as_ref::h703ff844f1016e01
 4:31.83   10:     0x7ffc719dfc18 - std::sync::once::Once::call_inner::h314cd51909d142ef
 4:31.83   11:     0x7ff6e116d51d - bindgen::Builder::generate::h657cfddd494ecf1a
 4:31.83   12:     0x7ff6e1097776 - core::alloc::size_align::h9cf92d476a11de20
 4:31.84   13:     0x7ff6e1091f85 - std::rt::lang_start::h4fba4b55d34bb956
 4:31.84   14:     0x7ffc719b9206 - std::panicking::update_panic_count::hf9e0b184b1baf22b
 4:31.84   15:     0x7ffc719eaa61 - _rust_maybe_catch_panic
 4:31.84   16:     0x7ffc719c8a82 - std::rt::lang_start_internal::h8f028255e9554163
 4:31.84   17:     0x7ff6e1091f72 - std::rt::lang_start::h4fba4b55d34bb956
 4:31.84   18:     0x7ff6e123ee13 - invoke_main
 4:31.84                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:31.84   19:     0x7ff6e123ee13 - invoke_main
 4:31.84                                at d:\agent\_work\3\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:78
 4:31.84   20:     0x7ffca1163033 - BaseThreadInitThunk
 4:31.84   21:     0x7ffca3a53690 - RtlUserThreadStart
 4:31.84 warning: build failed, waiting for other jobs to finish...
 4:31.95 error: build failed
 4:32.06 mozmake.EXE[4]: *** [f:/mozilla-source/config/rules.mk:1040: force-cargo-library-build] Error 101
 4:32.06 mozmake.EXE[3]: *** [f:/mozilla-source/config/recurse.mk:74: js/src/rust/target] Error 2
 4:32.08 mozmake.EXE[2]: *** [f:/mozilla-source/config/recurse.mk:34: compile] Error 2
 4:32.09 mozmake.EXE[1]: *** [f:/mozilla-source/config/rules.mk:424: default] Error 2
 4:32.12 mozmake.EXE: *** [client.mk:125: build] Error 2
 4:32.19 0 compiler warnings present.
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds