kencu

here's a build file for llas.cpp as a separate project

9

I threw this together for a quick test of llas against an installed llvm. This should allow llas to be used as an assembler without a full clang install on...

patch for LLVM-7-branch/compiler-rt/lib/builtins/os_version_check.c to make it work on Leopard and below

1

As you probably know we have clang/llvm up to clang-devel r357237 working and distributed to users on Leopard and above. I also have clang-5.0 working on 10.5 PPC but not...

async/await using external mozjs?

3

mozjs52, 60, and 68 all build on 10.6.8 now via MacPorts, and up to 60 are available for ppc Tiger I believe. Those js versions all fully support the async/await...

Building TenFourFox PPC on Leopard

18

At present, there are two hiccups with building TFF on LeopardPPC, for anyone who is interested in this. Follow all instructions as outlined to build TFF on PPC Tiger as...

please consider a short note about where patches are found and process to apply

1

I have not really understood exactly where the new changes come from upstream, and how to screen them to apply them to this codebase. Perhaps you might have a moment...

TenFourFox built with gcc 6.4.0 causes bus error in XUL nsCSSFrameConstructor::ProcessChildren

38

Looking towards a day when TenFourFox might be built with gcc6. A debug build with gcc6, generic G3 has a bus error on launch: ====== mozconfig ``` . $topsrcdir/browser/config/mozconfig export...

./compile.sh always seems to rebuild absolutely everything ...

4

Is it just me? It seems that when subprojects have been built, and are without any changes, running ./compile.sh to fix up some issue (eg when I was working on...

big endian detection fails on stock Apple compilers (gcc 4.2 and less) on PPC

2

I noticed that on some older PPC systems I have, the SHA1 hashes created in git were failing since this code was included. When built with newer gcc compilers (e.g....

known_fail should not be seen as a build success

6

when a port sets known_fail on a system version, it should be displayed as a fail in the webapp, not a success

Use ghc::filesystem as a substitute for std::filesystem transparently?

1

Is there some way that a build written to use ```std::filesystem::``` calls might transparently substitute ```ghc::filesystem::``` calls without patching the code?