FWIW this is a Mer issue, not a Jolla one IMHO mer-core plain gcc should not build fortran - it's not part of the core and adds a lot of overhead in the wrong place my suggested approach (ie how I'd start) is to fork the mer-core gcc package to a gcc-fortran package, copy the spec file to gcc-fortran.spec and modify it so it builds with fortran enabled but no other changes. Package the delta as gcc-fortran and unpackage any std gcc files in a way that doesn't collide with mer-core gcc. Eventually submit to mer-tools