From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2607:f8b0:4864:20::d43; helo=mail-io1-xd43.google.com; envelope-from=peter.wiehe2@gmail.com; receiver=edk2-devel@lists.01.org Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id C3B562117FD5E for ; Sat, 24 Nov 2018 13:18:16 -0800 (PST) Received: by mail-io1-xd43.google.com with SMTP id g8so11092761iop.10 for ; Sat, 24 Nov 2018 13:18:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=JQQ2Y8GsQfUpkfciyi4CJViCtkw/rsqdz5l7ofX7g8Q=; b=iq6RLL8y1arIFEgeE2sbagLlSEOm3+hzSTNkNi6IM0jNF4WtKeEG/GsvVCO7LYLsGD Wpc34WihAdgz6I+5If5u/xebjSlqI6OXFCSVZ2zPjkQXov8mioIhjYHRakxVKyPRF13c maif1vlefDnJRTVuroVBVnAHlayNTVBCpRd/z4MA2pwuJJAI7wkbDBsgblcJw/nzT/ri TZGp9biBGmWGelGv33pV+9uoumCKuNr0hgBllZu2eDQL/Q+LjXOHztm5X1JGXzNM/6gh gFzS3qxXfMUsv08HkMRxDQrQ1c6uwI/QdTENEn2peEJI6E/l/y5+Zx+LGZZ7+XQqweFp HEfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=JQQ2Y8GsQfUpkfciyi4CJViCtkw/rsqdz5l7ofX7g8Q=; b=rMNf+967AWEMiAgM1GRFZGI6kQlyQu/ZWGp2rprCXON/UzhIx3eEb9VIHr9GafQSiE rnM8yEAJiWnJXrc8ivoGDm8g0z5TShuJ1YbyvqdQYAD3F64iwNocv2mXc4ujzMN4MfZY WDw0H+/6ozC6H87LQj3+cGnpfg5Lb556GHPDZGiRjVpccq8I4KHfoGz+Ypi3m4s0Fczv eefKCtRgk0FAt+QvYjo7iN1+qgQjccapFI1QdZ4y+9nX/z+bHhmwf0pIF8d59fdXtCud q+QZhY18RTRQPrkNCyhAvOBUYPIgj+LCyMbvz3qIt7qpXhdjGaS5MtIzkG0YhAyezDnV 9JYQ== X-Gm-Message-State: AA+aEWbc0Bb/DZ8IB8FnQKPrQH/b2l3eKif8C13Q+IlpezELgUQs14OJ ko5RgtbMzNKcATYahqHsz1NqaVoyfJMcYJpO2Gf+H/AT X-Google-Smtp-Source: AFSGD/X8KfURjP1JJHJ2Ljn8WpFVRjBomCqUHa4rai/QQJGtTGm5fuX8Mc0fPOkVQ9h11rMveNI8H70bUPbAWoyYdvw= X-Received: by 2002:a5e:de42:: with SMTP id e2mr16116386ioq.91.1543094295552; Sat, 24 Nov 2018 13:18:15 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a5d:899a:0:0:0:0:0 with HTTP; Sat, 24 Nov 2018 13:18:15 -0800 (PST) From: Peter Wiehe Date: Sat, 24 Nov 2018 22:18:15 +0100 Message-ID: To: edk2-devel@lists.01.org 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 21:18:17 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable OK I simply re-did what I have done and now it works. It was probably a typo of ". edksetup.sh BaseTools" or of the "export ..." command. Kind regards Peter 2018-11-24 21:44 GMT+01:00, Andrew Fish : > > >> On Nov 24, 2018, at 11:46 AM, Peter Wiehe wrote= : >> >> As I said: I can't run "build". That command is unkown. >> > > Peter, > > The build command is what is required to build the firmware. > > Sourcing the edksetup.sh should set your path so build can be found. > > 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:/sb= in:/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/B= aseTools/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/02= 8 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? > > Thanks, > > Andrew Fish > >> Peter >> >> Andrew Fish > schrieb am Sa., 2= 4. >> Nov. 2018 20:45: >> Run the build command. Conf/target.txt controls the default arguments >> passed to build. >> >> Sourcing edksetup.sh should set your path. Did you miss the =E2=80=9C.= =E2=80=9D or get an >> error? >> . edksetup.sh BaseTools >> >> Sent from my iPad >> >> > On Nov 24, 2018, at 10:03 AM, Peter Wiehe > > > wrote: >> > >> > OK, thanks! Done that. >> > >> > But how do I get to build the MdeModulePkg? I did setup as mentioned >> > in >> > https://github.com/tianocore/tianocore.github.io/wiki/Common-instructi= ons >> > >> > >> > Peter >> > >> > 2018-11-24 18:57 GMT+01:00, stephano > > >: >> >> Hey Peter, >> >> >> >> We're still using GCC5 for most of our testing. Try building with tha= t >> >> release: >> >> >> >> apt install gcc-5 >> >> >> >> Then in Conf/target.txt: >> >> TOOL_CHAIN_TAG =3D GCC5 >> >> >> >> Cheers, >> >> Stephano >> >> >> >>> On 11/24/2018 9:23 AM, Peter Wiehe wrote: >> >>> OK >> >>> >> >>> Building went well to a certain point. I successfully git cloned. I >> >>> built the BaseTools. >> >>> >> >>> I (seemingly successfully) setup the build shell environment. (I got >> >>> no >> >>> errors.) >> >>> >> >>> 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". >> >>> >> >>> 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..."). >> >>> >> >>> What can I do? >> >>> >> >>> Greetings >> >>> Peter >> >>> >> >>> 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-instru= ctions >> >>>> >> >>>> >> >>>> Note: Be sure the TARGET_ARCH is set correctly. (E.g. TARGET_ARCH = =3D >> >>>> x64) >> >>>> >> >>>> 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= /bios.bin: >> >>>>> Could not open >> >>>>> '/home/peter/Schreibtisch/edk2-master/Build/OvmfX64/DEBUG_GCC5/QEM= U/bios.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 >> >>> >> >>> >> >> >> > _______________________________________________ >> > edk2-devel mailing list >> > edk2-devel@lists.01.org >> > https://lists.01.org/mailman/listinfo/edk2-devel >> > > >