Re: [edk2] Xen OVMF early discussions

Subject: Re: [edk2] Xen OVMF early discussions

From: Andrei Warkentin <andreiw@motorola.com>

To: edk2-devel@lists.sourceforge.net

Date: 2011-05-09 20:45:39

On Mon, May 9, 2011 at 11:47 AM, Bei Guan  wrote:
>
>
> 2011/5/10 Jordan Justen 
>>
>> On Mon, May 9, 2011 at 09:33, Bei Guan  wrote:
>> > 2011/5/9 Andrew Fish 
>> >> The DriverName.efi usually comes from the PE/COFF .debug section. =A0=
For
>> >> a
>> >> Visual Studio image the .debug section points to a .pdb file that
>> >> contains
>> >> debug info. For other tool chains it points to dwarf2, or the original
>> >> ELF
>> >> or Mach-O image that contain dwarf.
>> >
>> > Yes, I also have found the following code. My platform is Fedora, so,
>> > how
>> > can I make the=A0DriverName.efi printed? Does it need to set some conf=
ig
>> > file?
>>
>> When you build OVMF and run it for QEMU, do the filenames appear?
>
> No, it never appeared.
>
>>
>> Which toolchain are you using? =A0(GCC44? =A0UNIXGCC?)
>
> My toolchain is UNIXGCC.
>

What does gcc -v say?

A

---------------------------------------------------------------------------=
---
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network =

management toolset available today.  Delivers lowest initial =

acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel