From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=40.92.64.43; helo=eur01-db5-obe.outbound.protection.outlook.com; envelope-from=marvin.haeuser@outlook.com; receiver=edk2-devel@lists.01.org Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-oln040092064043.outbound.protection.outlook.com [40.92.64.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id D70192244E3EC for ; Sun, 15 Apr 2018 08:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ahtqq8oZmqBeWje6h8gMeba2fRtvEOvDvLl8/7Ss9Yc=; b=CgPmO+DRZLxKnAPFTK2I3iJz+Q9xxp0uZAmtxBpvmLDPFaEqJxbBos8tlaXxgOuQIcPpA7OCOZXWc1/m+SsNfgZBi/E9LtYY/f5fgaxetnMr41Iw5o2djPA0WZb7sEV3/OoM1ytzPvyVJ47k0NtuLf89VtesxQJ7tWeq+BuTVlz/6D7b+corzrAUt4ejL6u7umuYdfEfK+Kc2SKse1rENabwFcvjEsTAOGyVLqY6axQK6/62lO5LqsMKL9c3anTv8UvLUfYa4m9n5MQDBS5TPpE4zydmrdXEVf9B0pYeTP+bfgUvCfUs+MkNtVKJdF5Ie2LMAMmO/Ik49EQKh/AVZA== Received: from VE1EUR01FT045.eop-EUR01.prod.protection.outlook.com (10.152.2.55) by VE1EUR01HT028.eop-EUR01.prod.protection.outlook.com (10.152.3.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.653.8; Sun, 15 Apr 2018 15:31:11 +0000 Received: from VI1PR0801MB1790.eurprd08.prod.outlook.com (10.152.2.56) by VE1EUR01FT045.mail.protection.outlook.com (10.152.3.125) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.653.8 via Frontend Transport; Sun, 15 Apr 2018 15:31:11 +0000 Received: from VI1PR0801MB1790.eurprd08.prod.outlook.com ([fe80::90c0:177a:2337:1058]) by VI1PR0801MB1790.eurprd08.prod.outlook.com ([fe80::90c0:177a:2337:1058%17]) with mapi id 15.20.0675.011; Sun, 15 Apr 2018 15:31:11 +0000 From: =?iso-8859-1?Q?Marvin_H=E4user?= To: "edk2-devel@lists.01.org" Thread-Topic: [edk2] TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)? Thread-Index: AdPUzq47rSPc5iUNQFeN3KT11pw8fw== Date: Sun, 15 Apr 2018 15:31:11 +0000 Message-ID: Accept-Language: de-DE, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:F6544DB19CF6296E121DED86CD784611E57D1AE79A91A4A152BE6D6E3508F01E; UpperCasedChecksum:A00652D6D33D9D8DEEEED0C3BB2C0C5938CEEF5B83D37D874E86632ACFF921B6; SizeAsReceived:7102; Count:44 x-tmn: [V9LsnE048thKf+U6OyXETvp8ZyEOvyKm] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VE1EUR01HT028; 7:PN+nS6ainSBg9QdVnL5Zsh2Klo8TLD2AD2+msgf7Hm08OS9UFbTNkVeZpKmvqZD1gNjxRAoqHB38keYudKyx/5flOea/NXD0T/jYeSs5uh/5HPqmE0TBI3MUyEwWWuHT7HBuFMSUmRsNUaBVnYoyeViv98nrA5NOkdkVHAQlkgUd+MW3M6sxL6cEGp5o0OS3KvS0jhgAVnxmH71ygsXS21qSDMuS+Tas6xP2wpSP5NYd/OjSNWp25F0A53l4kehH x-incomingheadercount: 44 x-eopattributedmessage: 0 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:VE1EUR01HT028; x-ms-traffictypediagnostic: VE1EUR01HT028: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT028; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT028; x-forefront-prvs: 0643BDA83C x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT028; H:VI1PR0801MB1790.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:; x-microsoft-antispam-message-info: uT6bSLnmsiT9V98qXv53oV/cHrFLWIUodzG923uaJumfQjsegz3HJ9NSICwlqrjPSN9ONtR/zDHv8SCW4iLnUak97icQIiKvqC252QxCf+un9yDtfszovGINrOAV7IF+msxzj2I7Q35BalSMBeowLJPUWBTm9PZxL6nkE9bAwAbJ3GgqLGyVCup/vwdOPGZ6 MIME-Version: 1.0 X-MS-Office365-Filtering-Correlation-Id: 563bb4ea-1f7e-4a0e-fbdd-08d5a2e5eadc X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 7181d4b0-87d6-4f4e-ba33-0d3746212cec X-MS-Exchange-CrossTenant-Network-Message-Id: 563bb4ea-1f7e-4a0e-fbdd-08d5a2e5eadc X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 7181d4b0-87d6-4f4e-ba33-0d3746212cec X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2018 15:31:11.3573 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT028 Subject: Re: TianoCore UEFI Development Kit build: how to cause the build process to correctly recognize the build platform (Linux)? X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2018 15:31:18 -0000 Content-Language: de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey, As you have found out, Nt32Pkg is for Windows and shouldn't be built on Lin= ux. You can specify the platform descriptor file to build via the "-p " parameter. Regards, Marvin. > -----Urspr=FCngliche Nachricht----- > Von: edk2-devel Im Auftrag von Aleksey > Shevandin > Gesendet: Sonntag, 15. April 2018 17:23 > An: edk2-devel@lists.01.org > Betreff: [edk2] TianoCore UEFI Development Kit build: how to cause the > build process to correctly recognize the build platform (Linux)? >=20 > Dear members, >=20 > I'm trying to build *UDK2018* on *Ubuntu 17*. After studying the > documentation, I had impressed that the platform setup script > (*sedksetup.sh*) shall configure the build framework to target the correc= t > build platform, the tool chain etc. Unfortunately this is not what actual= ly > happens. >=20 > The platform build process (the Build base tool) unexpectedly tries to bu= ild > some *MS Windows* oriented stuff and fails. How this can be fixed? >=20 > Following the documented recommendations, at the first stage I build the > "Base Tools": >=20 > |/make all -C ${EDK_TOOLS_PATH}/| >=20 > Then I run the setup script: >=20 > |/edksetup.sh BaseTools/| >=20 > This stages are finished with success, also the setup script runs some te= sts > that successfully pass. >=20 > On the next stage I'm trying to build the platform: >=20 > |build all -a X64 -t GCC5| >=20 > This last stage fails with the follow error: >=20 > Nt32Pkg/Include/WinNtPeim.h:27:10: fatal error: Common/WinNtInclude.h: > No such file or directory >=20 >=20 > Regards, >=20 > Aleksey >=20 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel