On 04/01/14 17:35, Reza Jelveh wrote: > using VfrCompile on a recent linux distribution such as archlinux yields > ERROR 0003 no matter what Vfr I call it on. does anyone have any hints on how > I can debug this? > > Thanks, > Reza > > "VfrCompile" -l -n --string-db > > /home/dude/OSXGUEST/ovmf-svn/src/tianocore-edk2-svn_build/Build/OvmfX64/RELEASE_GCC48/X64/IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe/OUTPUT/BdsDxeStrDefs.hpk > --output-directory > > /home/dude/OSXGUEST/ovmf-svn/src/tianocore-edk2-svn_build/Build/OvmfX64/RELEASE_GCC48/X64/IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe/DEBUG/DeviceMngr > > /home/dude/OSXGUEST/ovmf-svn/src/tianocore-edk2-svn_build/Build/OvmfX64/RELEASE_GCC48/X64/IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe/OUTPUT/DeviceManagerVfr.i > VfrCompile: ERROR 0003: Error parsing > compile error in file (null)
See: (1) the discussion in <https://aur.archlinux.org/packages/ovmf-svn/?setlang=en>. VfrCompile used to have some memcpy() problems (VfrCompile called memcpy() with overlapping memory areas, see (2) below). Another distro (I think OpenSUSE?) triggered these bugs, and most of them were fixed. We suspect that *maybe* ArchLinux triggers more of the same. For this case I added a test patch to the discussion above, but there has been no feedback yet. Of course it's fully possible that the issue is something else. (2) http://thread.gmane.org/gmane.comp.bios.tianocore.devel/5941 http://thread.gmane.org/gmane.comp.bios.tianocore.devel/5997 (3) If you can provide such instructions for reproducing the problem that I can execute with minimal thinking, and without learning *anything* about ArchLinux, I might give a try to looking into the issue. Your first instruction should be a link to an ArchLinux installer ISO that works in a VM. Thanks Laszlo ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
