From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=17.151.62.66; helo=nwk-aaemail-lapp01.apple.com; envelope-from=afish@apple.com; receiver=edk2-devel@lists.01.org Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (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 3A4D421A00AE6 for ; Sat, 24 Nov 2018 12:46:02 -0800 (PST) Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.22/8.16.0.22) with SMTP id wAOKgAF9044329; Sat, 24 Nov 2018 12:46:01 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=mime-version : content-type : sender : from : message-id : subject : date : in-reply-to : cc : to : references; s=20180706; bh=BGz7mduth2Yy8g1bt6vI6Bg7rs2WzJbIbAB8Ayd3SAg=; b=mQO/YBglaWWNr7S+1kWMg0GGLmsZMUPZ9n613Htw252cq3KIXTndtk1l1gs8QnMCLfnb 27GpVDbKyVCZJq11bq0XhWIsHQhgzwOJ8FPCiM3IDy40EGrc6A+smDftSJQt6+cXooXU RQM7p8K6FGtgv3RpSWDu5rlhzSTUl2S8PTk7JDrWJmNHQ7nuLS0Whlh4TbyFm5kI3VAx j6jlu1pRqwyUtDgyX7lmB70xRiXLRAXpETHOxQQFk2RfKYWHn10iujL9GpDyzrZMxPHJ ZeP+C24loSbnmDIw5VQrOnKXzv6M2IzQG3BcovhPLHi3xc8hudKO0iGJD6Pko2FcdSmI LA== Received: from ma1-mtap-s02.corp.apple.com (ma1-mtap-s02.corp.apple.com [17.40.76.6]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2ny6f6qk9s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 24 Nov 2018 12:46:01 -0800 MIME-version: 1.0 Received: from ma1-mmpp-sz07.apple.com (ma1-mmpp-sz07.apple.com [17.171.128.149]) by ma1-mtap-s02.corp.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPS id <0PIP00FDLTOO7D00@ma1-mtap-s02.corp.apple.com>; Sat, 24 Nov 2018 12:46:00 -0800 (PST) Received: from process_viserion-daemon.ma1-mmpp-sz07.apple.com by ma1-mmpp-sz07.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PIP00I00TOAR400@ma1-mmpp-sz07.apple.com>; Sat, 24 Nov 2018 12:46:00 -0800 (PST) X-Va-A: X-Va-T-CD: 7069b87e460bab77838bd4ff93c12437 X-Va-E-CD: 1758fc4680fd58cfa24a3d78200b33d1 X-Va-R-CD: f4ce024657388c4f41e2355efbeac5df X-Va-CD: 0 X-Va-ID: 38ba1015-2212-4e45-9572-658e81750ac9 X-V-A: X-V-T-CD: 98a778f61b85c340d07cc74675eb362f X-V-E-CD: 1758fc4680fd58cfa24a3d78200b33d1 X-V-R-CD: f4ce024657388c4f41e2355efbeac5df X-V-CD: 0 X-V-ID: fa2cfb30-36ac-48d2-a9fd-04b8cb7f8377 Received: from process_milters-daemon.ma1-mmpp-sz07.apple.com by ma1-mmpp-sz07.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) id <0PIP00700SZKUO00@ma1-mmpp-sz07.apple.com>; Sat, 24 Nov 2018 12:45:57 -0800 (PST) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-11-24_17:,, signatures=0 Received: from [17.234.136.238] (unknown [17.234.136.238]) by ma1-mmpp-sz07.apple.com (Oracle Communications Messaging Server 8.0.2.3.20180614 64bit (built Jun 14 2018)) with ESMTPSA id <0PIP0089FTOIF210@ma1-mmpp-sz07.apple.com>; Sat, 24 Nov 2018 12:45:57 -0800 (PST) Sender: afish@apple.com From: Andrew Fish Message-id: Date: Sat, 24 Nov 2018 12:44:51 -0800 In-reply-to: Cc: edk2-devel To: Peter Wiehe References: <4DF911E2-CFF4-4FA7-8270-7F17E29E51ED@apple.com> X-Mailer: Apple Mail (2.3445.6.18) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-11-24_17:, , signatures=0 X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sat, 24 Nov 2018 20:46:02 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Nov 24, 2018, at 11:46 AM, Peter Wiehe = wrote: >=20 > As I said: I can't run "build". That command is unkown. >=20 Peter, The build command is what is required to build the firmware.=20 Sourcing the edksetup.sh should set your path so build can be found.=20 I'm on macOS and it looks like this to me: /Volumes/Case/UDK2018(vUDK2018)>echo $PATH = /opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbi= n:/Applications/VMware = Fusion.app/Contents/Public:/opt/appleinternal/bin:/opt/apple/bin:/opt/X11/= bin:/Applications/Araxis\ Merge.app/Contents/Utilities /Volumes/Case/UDK2018(vUDK2018)>. edksetup.sh BaseTools WORKSPACE: /Volumes/Case/UDK2018 EDK_TOOLS_PATH: /Volumes/Case/UDK2018/BaseTools CONF_PATH: /Volumes/Case/UDK2018/Conf /Volumes/Case/UDK2018(vUDK2018)>echo $PATH = /Volumes/Case/UDK2018/BaseTools/Bin/Darwin-x86_64:/Volumes/Case/UDK2018/Ba= seTools/BinWrappers/PosixLike:/opt/local/bin:/opt/local/sbin:/usr/local/bi= n:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware = Fusion.app/Contents/Public:/opt/appleinternal/bin:/opt/apple/bin:/opt/X11/= bin:/Applications/Araxis\ Merge.app/Contents/Utilities /Volumes/Case/UDK2018(vUDK2018)>which build /Volumes/Case/UDK2018/BaseTools/BinWrappers/PosixLike/build /Volumes/Case/UDK2018(vUDK2018)>cat = /Volumes/Case/UDK2018/BaseTools/BinWrappers/PosixLike/build #!/usr/bin/env bash #python `dirname $0`/RunToolFromSource.py `basename $0` $* # If a python2 command is available, use it in preference to python if command -v python2 >/dev/null 2>&1; then python_exe=3Dpython2 fi full_cmd=3D${BASH_SOURCE:-$0} # see = http://mywiki.wooledge.org/BashFAQ/028 for a discussion of why $0 is not = a good choice here dir=3D$(dirname "$full_cmd") cmd=3D${full_cmd##*/} export PYTHONPATH=3D"$dir/../../Source/Python" exec "${python_exe:-python}" "$dir/../../Source/Python/$cmd/$cmd.py" = "$@" As you can see sourcing edksetup.sh should update your path to point to = a location for build. What happens on your system?=20 Thanks, Andrew Fish > Peter >=20 > Andrew Fish > schrieb am Sa., = 24. Nov. 2018 20:45: > Run the build command. Conf/target.txt controls the default arguments = passed to build. >=20 > Sourcing edksetup.sh should set your path. Did you miss the =E2=80=9C.=E2= =80=9D or get an error? > . edksetup.sh BaseTools >=20 > Sent from my iPad >=20 > > On Nov 24, 2018, at 10:03 AM, Peter Wiehe > wrote: > >=20 > > OK, thanks! Done that. > >=20 > > But how do I get to build the MdeModulePkg? I did setup as mentioned > > in = https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions = > >=20 > > Peter > >=20 > > 2018-11-24 18:57 GMT+01:00, stephano = >: > >> Hey Peter, > >>=20 > >> We're still using GCC5 for most of our testing. Try building with = that > >> release: > >>=20 > >> apt install gcc-5 > >>=20 > >> Then in Conf/target.txt: > >> TOOL_CHAIN_TAG =3D GCC5 > >>=20 > >> Cheers, > >> Stephano > >>=20 > >>> On 11/24/2018 9:23 AM, Peter Wiehe wrote: > >>> 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 > >>> errors.) > >>>=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, > >>>>=20 > >>>> Thanks for giving EDK2 a try! > >>>>=20 > >>>> We have a set of simple instructions for folks building on = standard > >>>> Linux distros. Please have a look at this page: > >>>>=20 > >>>> = https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions = > >>>>=20 > >>>> Note: Be sure the TARGET_ARCH is set correctly. (E.g. TARGET_ARCH = =3D x64) > >>>>=20 > >>>> Once you have built the BaseTools and MdeModulePkg without any = errors, > >>>> you can try building and running in OVMF: > >>>>=20 > >>>> = https://github.com/tianocore/tianocore.github.io/wiki/How-to-build-OVMF = > >>>>=20 > >>>> Tip: Add the -j option so that you can grep through the log = easily for > >>>> any errors (build -j /path/to/log/file.txt). > >>>>=20 > >>>> Hopefully those links help get you started. Let me know if you = run into > >>>> any other issues. > >>>>=20 > >>>> Cheers, > >>>> Stephano > >>>>=20 > >>>> Stephano Cetola > >>>> TianoCore Community Manager > >>>>=20 > >>>>> 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".) > >>>>>=20 > >>>>> I use xubuntu 18.04 on an AMD 64bit PC. > >>>>>=20 > >>>>> 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. > >>>>>=20 > >>>>> 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" > >>>>>=20 > >>>>> Then I get the error message "qemu-system-x86_64: -pflash > >>>>> = /home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bios.bi= n: > >>>>> Could not open > >>>>> = '/home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEMU/bios.b= in': > >>>>> No such file or directory" > >>>>>=20 > >>>>> So my first question is how to deal with this error. > >>>>>=20 > >>>>> Kind regards > >>>>> Peter Wiehe > >>>>> _______________________________________________ > >>>>> edk2-devel mailing list > >>>>> edk2-devel@lists.01.org > >>>>> https://lists.01.org/mailman/listinfo/edk2-devel = > >>>>>=20 > >>>>=20 > >>> _______________________________________________ > >>> edk2-devel mailing list > >>> edk2-devel@lists.01.org > >>> https://lists.01.org/mailman/listinfo/edk2-devel = > >>>=20 > >>=20 > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel =