From: Leif Lindholm <leif.lindholm@linaro.org>
To: wang xiaofeng <winggundum82@163.com>,
Sami Mujawar <Sami.Mujawar@arm.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Subject: Re: aarch64-linux-gnu-gcc.exe: error due to loss ‘/’in code path in in Jenkins server
Date: Wed, 3 Apr 2019 09:00:04 +0100 [thread overview]
Message-ID: <20190403080004.6olnatfjkrge35q7@bivouac.eciton.net> (raw)
In-Reply-To: <541f0df5.aa56.169e2314641.Coremail.winggundum82@163.com>
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\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?
>
next prev parent reply other threads:[~2019-04-03 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:54 aarch64-linux-gnu-gcc.exe: error due to loss ‘/’in code path in in Jenkins server wang xiaofeng
2019-04-03 8:00 ` Leif Lindholm [this message]
2019-04-03 8:07 ` wang xiaofeng
2019-04-03 10:59 ` Leif Lindholm
2019-04-03 12:12 ` wang xiaofeng
2019-04-03 13:09 ` Sami Mujawar
2019-04-03 12:00 ` Gao, Liming
[not found] ` <3ea8e74.10983.169e320a125.Coremail.winggundum82@163.com>
2019-04-03 12:51 ` Gao, Liming
2019-04-03 12:59 ` wang xiaofeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190403080004.6olnatfjkrge35q7@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox