Custom Query (344 matches)
Results (103 - 105 of 344)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#164 | wontfix | gcc4.spec: Add gcc-wlink and gcc-wrc dependencies to gcc package | ||
Description |
GCC can use two linkers: ILINK and WLINK (this is controlled by the EMXOMFLD_LINKER and EMXOMFLD_TYPE variables). However, we don't have an RPM package for ILINK (for legal reasons) and ILINK is broken anyway so it makes no sense to use it at all. Therefore, we should force the installation of |
|||
#165 | fixed | Binutils too old to support AVX2 | ||
Description |
While GCC reports AVX2 is available, # gcc -mavx2 -dM -E - < /dev/null | egrep "AVX" | sort #define __AVX__ 1 #define __AVX2__ 1 AS errors out when compiling AVX2 code, eg from flac git head, R:/tmp/ccwvrScM.s:8773: Error: operand type mismatch for `vpsrlq' R:/tmp/ccwvrScM.s:8778: Error: no such instruction: `vpermd %ymm1,%ymm5,%ymm0' R:/tmp/ccwvrScM.s:8859: Error: operand type mismatch for `vpmovzxdq' Our binutils version 2.21 is close to 5 years old and Paul's newest release is binutils v2.25 2015-01-08. |
|||
#166 | duplicate | coexisting packages / legacy packages | ||
Description |
We need a way to have different packages of the same port to be installable. The reason behind it is, when a dll name gets changed, we need to add the old dll somehow still. As other non rpm ports might depend on them. For rpm be just could rebuild all dependent ports and upload the new rpm's. Which is timeconsuming but the right way. This ticket is to decide how we progress on such situations. Do we coexisting packages or legacy packages. With legacy we might end in several legacy packages for the same port, as every new version might bring a new dll name. |