Le mardi 23 août 2016 à 12:55 -0500, Isaac David a écrit : > Le mar. 23 août 2016 à 4:51, Paul Kocialkowski <cont...@paulk.fr> a > écrit : > > Also, I don't see what problem can arise from this, as it was > > suggested at: > > https://labs.parabola.nu/issues/1039 > > > > ALARM also hardcodes "armv7h" in the distributed pacman.conf, so > > there's no > > specific reason it would cause a problem when migrating. (Or am I > > perhaps > > missing something here ?) > > You should read it as: > > "Using armv7l as the architecture name in pacman is the KISS solution, > but it would cause problems with migrating, etc." > > instead of > > "Hardcoding armv7h would cause problems with migrating, etc."
Ah right, makes more sense. Well, I don't think that using something different from what uname -m returns as arch name is a problem. I think the hard-floating point distinction is more relevant than endianness, because it restricts the scope of possibly supported devices. If anything, I think pacman's autodetection should be fixed to return armv7h when uname -m returns armv7l. I could bring-in that change if you think it's relevant. Maybe upstream would be interested too. -- Paul Kocialkowski, developer of low-level free software for embedded devices Website: https://www.paulk.fr/ Coding blog: https://code.paulk.fr/ Git repositories: https://git.paulk.fr/ https://git.code.paulk.fr/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Dev mailing list Dev@lists.parabola.nu https://lists.parabola.nu/mailman/listinfo/dev
