Comment by munchlax

Comment by munchlax 10 days ago

12 replies

View on Hacker News

Have you tried building AOSP from available sources?

Binaries everywhere. Tried to rebuild some of them with the available sources and noped the f out because that breaks the build so bad it's ridiculous.

zoobab 10 days ago

"Binaries everywhere"

So much for "Open Source"

Reply View 8 replies
  • jeroenhd 10 days ago

    The binaries are open source, but Google doesn't design their build chain to recompile from scratch every time.

    Also, you don't need to compile all of AOSP just to get the toolchain binaries.

    Reply View 1 reply
    • orblivion 10 days ago

      With how strict F-Droid is I would have expected them to build from source all the way down. Though that sounds like a daunting task so I don't blame them.

      Reply View 0 replies
  • gbin 10 days ago

    Everything is open source, if you can read assembly ;)

    Reply View 5 replies
    • bluGill 10 days ago

      Machine code. Assembly is higher level. since data and instructions can be mixed machine code is harder to decode - that might be a byte of data or an instruction. Mel would have [ab]used this fact to make his programs work. It is worse on x86 where instructions are not fixed length but even on arm you can run into problems at times

      Reply View 3 replies
      • snake42 10 days ago

        You can always lift machine code to assembly. Its a 1 to 1 process.

        Reply View 2 replies
    • ignoramous 10 days ago

      ... this is why we get DRM. Source modification is what hurts them.

      Reply View 0 replies
rbanffy 10 days ago

Yes. Sources available means nothing without a reproducible build process.

Reply View 0 replies