I mean to manually trig build in Jenkins server and see what happen.

Thanks
Liming
From: wang xiaofeng [mailto:winggundu...@163.com]
Sent: Wednesday, April 3, 2019 8:16 PM
To: Gao, Liming <liming....@intel.com>
Cc: edk2-devel@lists.01.org; ard.biesheu...@linaro.org; leif.lindh...@linaro.org
Subject: Re:Re: [edk2] aarch64-linux-gnu-gcc.exe: error due to loss ‘/’in code 
path in in Jenkins server

HI Liming,
   I don;t have direct access to server but  I can ask someone to try.
   How to verify gcc tool enviroment? any command I can run to check the 
difference?
   I just compare the gcc tool binarys , server and my local desktop are same. 
But I am not sure whether other software/enviroment is installed on server may 
affect the tools.




At 2019-04-03 20:00:09, "Gao, Liming" 
<liming....@intel.com<mailto:liming....@intel.com>> wrote:

>Are your local server the same environment to Jenkins server? Can you login in 
>Jenkins sever and verify gcc tool?

>

>Thanks

>Liming

>From: wang xiaofeng [mailto:winggundu...@163.com]

>Sent: Wednesday, April 3, 2019 3:55 PM

>To: Gao, Liming <liming....@intel.com<mailto:liming....@intel.com>>; 
>edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>; 
>ard.biesheu...@linaro.org<mailto:ard.biesheu...@linaro.org>; 
>leif.lindh...@linaro.org<mailto:leif.lindh...@linaro.org>

>Subject: aarch64-linux-gnu-gcc.exe: error due to loss ‘/’in code path in in 
>Jenkins server

>

>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\udk2018\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<mailto:edk2-devel@lists.01.org>

>https://lists.01.org/mailman/listinfo/edk2-devel



_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to