From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=192.55.52.120; helo=mga04.intel.com; envelope-from=liming.gao@intel.com; receiver=edk2-devel@lists.01.org Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 138D221A07A92 for ; Mon, 26 Nov 2018 06:09:28 -0800 (PST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Nov 2018 06:09:28 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,282,1539673200"; d="scan'208";a="109843340" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga004.fm.intel.com with ESMTP; 26 Nov 2018 06:09:28 -0800 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 26 Nov 2018 06:09:27 -0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.117]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.214]) with mapi id 14.03.0415.000; Mon, 26 Nov 2018 22:09:26 +0800 From: "Gao, Liming" To: Peter Wiehe , edk2-devel Thread-Topic: [edk2] Newbie: Getting Ovmf built Thread-Index: AQHUg34zwK0y1U5zhEmxteqN+oLKzqVdj2+AgAEYcICAA3OjwA== Date: Mon, 26 Nov 2018 14:09:25 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E37255D@SHSMSX104.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZmRhZjIxMjktNDY2Yi00MTJjLWJhYmMtMjVjNTExNGM0OTU4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiaFwvenFZSWpcL1ZWbUxcL0wwd3IzWU9MWW5XQUFabVlVS3lKVmY1Um01eDNxWWdPUllOUTRFSWVnSXluWmVuRjBDcyJ9 dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: Newbie: Getting Ovmf built X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Nov 2018 14:09:29 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Do you type ". edksetup.bat BaseTools" in Edk2 directory? What output of th= is command? This script will add edk2 BaseTools path into system PATH, then= build can be used.=20 And, you can use GCC5 as the default tool chain. It supports GCC 5.0 or the= above version.=20 > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Pe= ter Wiehe > Sent: Sunday, November 25, 2018 1:24 AM > To: edk2-devel > Subject: Re: [edk2] Newbie: Getting Ovmf built >=20 > OK >=20 > Building went well to a certain point. I successfully git cloned. I > built the BaseTools. >=20 > I (seemingly successfully) setup the build shell environment. (I got no e= rrors.) >=20 > In the target conf file I chose "IA32 X64" and ELFGCC (since I habe > gcc 7.3.0 installed). > When I type "build", there comes an error like "Command build not found". >=20 > I thought that maybe it's because of the shell environment variable > $PATH. $PATH does NOT contain the edk2 source directory in any way > (despite the fact that I entered "export EDK_TOOLS_PATH..."). >=20 > What can I do? >=20 > Greetings > Peter >=20 > 2018-11-24 1:40 GMT+01:00, stephano : > > Hello Peter, > > > > Thanks for giving EDK2 a try! > > > > We have a set of simple instructions for folks building on standard > > Linux distros. Please have a look at this page: > > > > https://github.com/tianocore/tianocore.github.io/wiki/Common-instructio= ns > > > > Note: Be sure the TARGET_ARCH is set correctly. (E.g. TARGET_ARCH =3D x= 64) > > > > Once you have built the BaseTools and MdeModulePkg without any errors, > > you can try building and running in OVMF: > > > > https://github.com/tianocore/tianocore.github.io/wiki/How-to-build-OVMF > > > > Tip: Add the -j option so that you can grep through the log easily for > > any errors (build -j /path/to/log/file.txt). > > > > Hopefully those links help get you started. Let me know if you run into > > any other issues. > > > > Cheers, > > Stephano > > > > Stephano Cetola > > TianoCore Community Manager > > > > On 11/23/2018 2:44 PM, Peter Wiehe wrote: > >> Hello, I'm a total newbie to Tianocore/EDK2/OVMF. > >> (My coding is at high school level I think, not university level. I > >> have some (small) experience writing in Assembler, C, C++. I wrote a > >> little bootloader, so I know something about filesystem in general and > >> ext2 and pre-kernel "environment".) > >> > >> I use xubuntu 18.04 on an AMD 64bit PC. > >> > >> I'm currently trying to > >> 1.) build OVMF from source > >> 2.) and then want to run it in/with Qemu. > >> 3.) Later I would like to try to write a simple ext2 "driver". Can't > >> guarantee I will succeed, but let's see. > >> > >> So far I have > >> 1.) downloaded the whole edk2 zip/tar-ball > >> 2.) have installed nasm and ASL (iasl) > >> 3.) Run "EmulatorPkg/build.sh" > >> 4.) Run "OvmfPkg/build.sh -a X64" > >> 5.) Run "OvmfPkg/build.sh -a X64 qemu" > >> > >> Then I get the error message "qemu-system-x86_64: -pflash > >> /home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bio= s.bin: > >> Could not open > >> '/home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bi= os.bin': > >> No such file or directory" > >> > >> So my first question is how to deal with this error. > >> > >> Kind regards > >> Peter Wiehe > >> _______________________________________________ > >> edk2-devel mailing list > >> 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