Trunk will not work with LLVM 2.6.  It will work with LLVM trunk from about a 
week ago.  I fixed a bug in r93052 that is needed for LK to work, so that's 
probably a good revision to try with.  Or you could update LK to work with LLVM 
trunk - it's probably quite a small change...

David

On 1 Feb 2010, at 00:48, Joseph Jones wrote:

> DOH, I replied to my own wrong message.Sigh...
> 
> NP, thanx for the info. Currently building 2.6 to see if I can get over
> that hurdle.
> 
> joe
> 
> 
> On Mon, 2010-02-01 at 00:32 +0000, David Chisnall wrote:
>> On 1 Feb 2010, at 00:27, Joseph Jones wrote:
>> 
>>>     * ModuleProvider has been removed and its methods moved to Module
>>>       and GlobalValue. Most clients can remove uses of
>>>       ExistingModuleProvider, replace getBitcodeModuleProvider with
>>>       getLazyBitcodeModule, and pass their Module to functions that
>>>       used to accept ModuleProvider. Clients who wrote their own
>>>       ModuleProviders will need to derive from GVMaterializer instead
>>>       and use Module::setMaterializer to attach it to a Module.
>> 
>> 
>> This change was only made last week and I haven't got around to updating 
>> LanguageKit for it yet (I've been working on clang and libobjc2 instead).  I 
>> should get it done some time this week, unless someone else fixes it first.
>> 
>> David
>> 
>> -- Sent from my Apple II
>> 
>> 
>> _______________________________________________
>> Etoile-discuss mailing list
>> [email protected]
>> https://mail.gna.org/listinfo/etoile-discuss
> 
> 
> 
> _______________________________________________
> Etoile-discuss mailing list
> [email protected]
> https://mail.gna.org/listinfo/etoile-discuss


-- Sent from my Cray X1


_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss

Répondre à