On Apr 2, 2014, at 4:41 AM, Reza Jelveh <reza.jel...@tuhh.de> wrote:

> On 02/04/14 01:22, Andrew Fish wrote:
>> I’ve been meaning to add an Xcode5 target that has the different arg to the 
>> template file. What OS version are you running on? I’m on OS X 10.9.2. 
> i'm using 10.9.2, i have xcode 5, but yes, I was using xcode 4.6 binutils
> since i'm on gentoo prefix, and stock xcode 5 doesn't work. i just tried it.

OK then this may be fixable.  Use Xcode 5 for C code and then point 
*_*_*_ASM_PATH to your binutils version of as. 

*_XCLANG_*_ASM_PATH = /usr/local/bin/as


>> 
>> I’ve not seen an issue with Xcode 5 and Xcode 5.1 tools. 
> xcode 5 definitely fails with missing retf here. if I don't patch the cctools
> i need to patch exceptionhandler.s to use lret instead, and then it'll fail
> with:
> 
> ld: illegal text-relocation to '_CommonInterruptEntry' in 
> /Users/timebomb/git/gsoc/edk2/Build/OvmfX64/DEBUG_XCLANG/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/DxeCpuExceptionHandlerLib.lib(ExceptionHandlerAsm.obj)
>  from 'Exception0Handle' in 
> /Users/timebomb/git/gsoc/edk2/Build/OvmfX64/DEBUG_XCLANG/X64/UefiCpuPkg/Library/CpuExceptionHandlerLib/DxeCpuExceptionHandlerLib/OUTPUT/DxeCpuExceptionHandlerLib.lib(ExceptionHandlerAsm.obj)
>  for architecture x86_64 
> 
> downloading 5.1 atm.
> 
>> With Mavericks and the current versions of Xcode you can install as many
>> versions as you want and switch between the different versions.
> i believe that only works if you have a paid developer account.
> 

No that is just how it works in Mavericks. Xcode is now a pure application and 
the real version of the tools live under the Application. You can just drag the 
application to a new location and use xcode-select to make it active.  You can 
always download the latest from the App store. 

Thanks,

Andrew Fish

>> Maybe the version of clang is ahead of the version of ld64? 
> maybe, any chance you'll release the new ldtools anytime soon?
> 
>> What do you see if you nm IoLibGcc.obj
> looks the same as yours. I think it might be a clang 3.4 bug. 
>>>>> ld: warning: can't parse dwarf compilation unit info in 
> 
> nm
> Build/OvmfX64/DEBUG_XCLANG/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic/OUTPUT/IoLibGcc.obj
> 0000000000000738 s EH_frame0
> 000000000000021a s L_.str
> 0000000000000265 s L_.str1
> 0000000000000275 s L_.str2
> U _DebugAssert
> U _DebugAssertEnabled
> 0000000000000050 T _IoRead16
> 0000000000000790 S _IoRead16.eh
> 0000000000000140 T _IoRead32
> 00000000000007e0 S _IoRead32.eh
> 0000000000000000 T _IoRead8
> 0000000000000750 S _IoRead8.eh
> 00000000000000c0 T _IoWrite16
> 00000000000007b8 S _IoWrite16.eh
> 00000000000001b0 T _IoWrite32
> 0000000000000808 S _IoWrite32.eh
> 0000000000000020 T _IoWrite8
> 0000000000000770 S _IoWrite8.eh
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

Reply via email to