News for hackers. Stuff that matters.
Re:Welcome Debian riscv64 by totetsu on Monday July 24, 2023 @04:59AM (#36844837)
What kind of assumptions would badly-written applications make to make themselves impractical to cross-build?
Re:Welcome Debian riscv64 by ilyt on Monday July 24, 2023 @05:45AM (#36845194)
Assembler optimizations without fallback to pure C for other architectures for example.
Re:Welcome Debian riscv64 by sanxiyn on Monday July 24, 2023 @05:55AM (#36845297)
All Debian packages are built natively. There is no cross build going on here.
Re:Welcome Debian riscv64 by pabs3 on Monday July 24, 2023 @10:14AM (#36848340)
During the initial port bootstrap process, the initial package set is cross-built using rebootstrap:

https://wiki.debian.org/PortsDocs/New#Bootstrap

Perhaps in the future Debian will be able to have cross-build-only architectures, that have hardware too slow to build software.

Re:Welcome Debian riscv64 by bregma on Monday July 24, 2023 @06:39AM (#36845665)
Othar than word size (eg. i386 vs. x86_64), endianness (eg. PPC vs. x86), alignment (eg. ARM vs. x86) there's plenty of other low-level issues like parameter passing conventions, call frame handling, exception handling, presence or absence of optional instructions or registers, and a number of other subtle gotchas that could affect a port. Instruction probing is one of the ones we run into where everything builds find and fails at runtime.

If you're working at a high enough level you're probably fine. Like the difference between being an auto mechanic and using the app to hail a ride.

Re:Welcome Debian riscv64 by smallpipe on Monday July 24, 2023 @08:44AM (#36847088)
You're missing the biggest one, concurrency model.
Re:Welcome Debian riscv64 by capitol_ on Monday July 24, 2023 @11:07AM (#36849227)
In my packaging work I encounter hard coded assumptions about pointer width, endianness and presence of atomic operations.