rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
David Woodhouse
dwmw2 at infradead.org
Sun Feb 13 13:12:24 UTC 2005
- Previous message: rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Next message: rpms/qemu - New directory
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Sun, 2005-02-13 at 13:43 +0100, Thorsten Leemhuis wrote:
>No, from my point it can stay ATM as it does not compile on x86_64
>anyway. If I get it to compile I can also fix that.
Good luck :)
>But I noticed something else in between. Those folks that come from
>gentoo might want to compile the package for i686... So is this
No, sod 'em. Unless they actually have sufficient wit to change the ezm3
compiler to output i686 code, compiling for i686 isn't going to make
_any_ difference anyway. And if they can manage to really make it
optimise for i686 then I'm sure they're capable of changing the specfile
accordingly.
--
dwmw2
- Previous message: rpms/cvsup/devel cvsup-ppc.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp-bootstrap.patch, NONE, 1.1 ezm3-1.2-PPC-setjmp.patch, NONE, 1.1 ezm3-1.2-ppc-jmpbufsize.patch, NONE, 1.1 .cvsignore, 1.2, 1.3 cvsup.spec, 1.5, 1.6 sources, 1.2, 1.3
- Next message: rpms/qemu - New directory
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the scm-commits
mailing list