Oh dang I haven't seen this since I was slavishly following the build 
instructions from the top. Nevermind then :)

Slightly related, how stable do you consider the fastcomp backend? Is it ok 
to pull the latest incoming changes for the emscripten repo without 
updating/recompiling the fastcomp stuff, or are dependent changes to all 3 
repos still common? 

Thanks!
-Floh.

Am Montag, 31. März 2014 16:49:23 UTC+2 schrieb Alon Zakai:
>
> The wiki page
>
> https://github.com/kripken/emscripten/wiki/LLVM-Backend
>
> does currently say that incoming should be used and not master (with 
> fastcomp). Is there somewhere else we should mention it?
>
> - Alon
>
>
>
> On Mon, Mar 31, 2014 at 5:22 AM, Floh <[email protected] <javascript:>>wrote:
>
>> Hi, I've setup my fastcomp build environment last weekend and stumbled 
>> into the same trap as before :)
>>
>> When following the build instructions here: 
>> https://github.com/kripken/emscripten/wiki/LLVM-Backend#getting-fastcomp, 
>> the build fails to compile (I don't have the error at hand but it was 
>> something about a missing LLVM tripe about half-way into the compilation 
>> process), I'm on OSX 10.9.2, but I think it is a universal problem(?)
>>
>> Switching from master to incoming fixes this, and results in a working 
>> build environment. May be it would be good to mention this in the build 
>> instruction, so that newcomers don't walk into the same trap?
>>
>> Cheers,
>> -Floh.
>>
>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "emscripten-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to