Yes, both my local and server using Cygwin for aarch64 build
At 2019-04-03 18:59:29, "Leif Lindholm" <leif.lindh...@linaro.org> wrote: >On Wed, Apr 03, 2019 at 04:07:58PM +0800, wang xiaofeng wrote: >> Hi Leif, >> We use VC for X86 (do not need GCC cross complie) > >Ah, that was not clear from the original mail. > >Are both server and local system using cygwin/mingw32? > >Best Regards, > >Leif > >> gcc revision : >> Using built-in specs. >> COLLECT_GCC=aarch64-linux-gnu-gcc.exe >> COLLECT_LTO_WRAPPER=c:/code/gnutools/gcc-linaro-7.3.1-2018.05-i686-mingw32_aarch64-linux-gnu/bin/../libexec/gcc/aarch64-linux-gnu/7.3.1/lto-wrapper.exe >> Target: aarch64-linux-gnu >> Configured with: >> '/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/snapshots/gcc.git~linaro-7.3-2018.05/configure' >> SHELL=/bin/bash >> --with-mpc=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32 >> >> --with-mpfr=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32 >> >> --with-gmp=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32 >> --with-gnu-as --with-gnu-ld --disable-libmudflap --enable-lto >> --enable-shared --without-included-gettext --enable-nls --with-system-zlib >> --disable-sjlj-exceptions --enable-gnu-unique-object >> --enable-linker-build-id --disable-libstdcxx-pch --enable-c99 >> --enable-clocale=gnu --enable-libstdcx x-debug --enable-long-long --with-cloog=no --with-ppl=no --with-isl=no --disable-multilib --enable-fix-cortex-a53-835769 --enable-fix-cortex-a53-843419 --with-arch=armv8-a --enable-threads=posix --enable-multiarch --enable-libstdcxx-time=yes --enable-gnu-indirect-function --with-build-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/sysroots/aarch64-linux-gnu --with-sysroot=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32/aarch64-linux-gnu/libc --enable-checking=release --disable-bootstrap --enable-languages=c,c++,fortran,lto --with-libiconv-prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32/usr --with-system-zlib=no --build=x86_64-unknown-linux-gnu --host=i686-w64-mingw32 --target=a arch64-linux-gnu --prefix=/home/tcwg-buildslave/workspace/tcwg-make-release/builder_arch/amd64/label/tcwg-x86_64-build/target/aarch64-linux-gnu/_build/builds/destdir/i686-w64-mingw32 >> Thread model: posix >> gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision >> d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) >> >> >> >> >> GNUmake revision : GNUMake-3.81_win32 >> >> >> Can the tool provide more debug output ? >> >> >> >> >> >> >> >> >> >> >> At 2019-04-03 16:00:04, "Leif Lindholm" <leif.lindh...@linaro.org> wrote: >> >Sami, any ideas? >> > >> >Xiaofeng, what gcc is being used for x86? (output of "gcc -v") >> > >> >Best Regards, >> > >> >Leif >> > >> >On Wed, Apr 03, 2019 at 03:54:33PM +0800, wang xiaofeng wrote: >> >> HI ARM Base tool owners, >> >> I meet a strange issue that aarch64 build . The aarch64 build pass on >> >> my local server. But it fails at Jenkins server(a Win10 autobuild system >> >> written by Java that will can call edk2 bat in command line) >> >> >> >> >> >> The build command is >> >> "c:\jenkins\workspace\gop2018\udk2018\gnutools\gcc-linaro-7.3.1-2018.05-i686-mingw32_aarch64-linux-gnu\bin\aarch64-linux-gnu-gcc" >> >> -g -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror >> >> -Wno-array-bounds -ffunction-sections -fdata-sections -include AutoGen.h >> >> -fno-common -DSTRING_ARRAY_NAME=UefiDevicePathLibStrings -g -Os >> >> -fshort-wchar -fno-builtin -fno-strict-aliasing -Wall -Werror >> >> -Wno-missing-braces -Wno-array-bounds -include AutoGen.h -fno-common >> >> -mlittle-endian -fno-short-enums -fverbose-asm -funsigned-char >> >> -ffunction-sections -fdata-sections -Wno-address >> >> -fno-asynchronous-unwind-tables -fno-pic -fno-pie -ffixed-x18 -flto >> >> -Wno-unused-but-set-variable -Wno-unused-const-variable -mcmodel=small >> >> -DEDKII -DEFIX64 -DUEFI_BUILD -DFGL_LINUX -DGCC_TOOLCHAIN -c -o >> >> c:\jenkins\workspace\gop2018\udk2018\Build\AmdGopPkg\DEBUG_GCC5\AARCH64\MdePkg\Library\UefiDevicePathLib\UefiDevicePathLib\OUTPUT\.\DevicePathUtilities.obj >> >> -Ic:\jenkins\workspace\gop2018\udk201 8\MdePkg\Library\UefiDevicePathLib -Ic:\jenkins\workspace\gop2018\udk2018\Build\AmdGopPkg\DEBUG_GCC5\AARCH64\MdePkg\Library\UefiDevicePathLib\UefiDevicePathLib\DEBUG -Ic:\jenkins\workspace\gop2018\udk2018\MdePkg -Ic:\jenkins\workspace\gop2018\udk2018\MdePkg\Include -Ic:\jenkins\workspace\gop2018\udk2018\MdePkg\Include\AArch64 c:\jenkins\workspace\gop2018\udk2018\MdePkg\Library\UefiDevicePathLib\DevicePathUtilities.c >> >> >> >> >> >> But aarch64-linux-gnu-gcc.exe will return error with : >> >> c:jenkinsworkspacegop2018udk2018MdePkgLibraryUefiDevicePathLibDevicePathUtilities.c: >> >> No such file or director >> >> The failure is due to all \ is missed from view of >> >> aarch64-linux-gnu-gcc.exe, while the makefile and build log have '\' >> >> Another clue is that x86 build is ok on the same Jenkins system >> >> >> >> >> >> Anyone have advice for this strange issue? >> >> _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
