--- Comment #28 from Nicolas Chauvet <kwizart(a)gmail.com> 2012-09-15 11:54:07 CEST
(In reply to comment #26)
(In reply to comment #25)
> Hum, be aware if you play with gcc flags to test completely PCSX2. PCSX2 is
> very sensible to gcc behavior and could break and crash very easily. I have
> enough report of real crashes ;)
We are bound to Fedora guidelines and therefore we must use those flags.
sorry but I cannot parse that !
We are only bound to have a brain! and guidelines doesn't mean we cannot use
our mind to solve specific situation.
Specially my position was explained here:
For this case it would simply means:
- We need to use the fedora cflags by default
- PCSX2 can enforce additional cflags (such as -sse2) "IF" when running on a
CPU that doesn't have them, an error is properly output. That will make the
package ExclusiveArch: i686.
- If others cflags from fedora are producing issue with this package, then the
cflags and the related error need to be sorted out from the spec file and
linked to a bug report for a later resolution.
Configure bugmail: https://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.