Compiling libtorrent & rtorrent for arch64

Question

rtorrent is a pretty nice Ncurses BitTorrent client based on libTorrent.
3 weeks ago, I built lib+rtorrent-0.6.3 from default aur PKGBUILD under arch64 and it is working fine.
New version 0.6.4 PKGBUILD differs from previous as it gives specific CXXFLAGS options.
Is there any need/interest to switch from "old" (below) to "new" CXXFLAGS style?
build() {
cd $startdir/src/$pkgname-$pkgver
patch -p1 < ../rtorrent.patch
CXXFLAGS="${CXXFLAGS} -fno-strength-reduce -fno-thread-jumps -fno-inline -fforce-addr"
./configure --prefix=/usr --disable-debug
make || return 1
make DESTDIR=$startdir/pkg install
Or switch to new one which I think would be:
if [ "$CARCH" == "x86_64" ]; then
CXXFLAGS="-march=x86_64 -Os -pipe -fno-strength-reduce -fno-thread-jumps -fno-inline -fforce-addr"
./configure --prefix=/usr --disable-debug
else
CXXFLAGS="-march=i686 -Os -pipe -fno-strength-reduce -fno-thread-jumps -fno-inline -fforce-addr"
./configure --prefix=/usr --disable-debug
fi

Answer 1

Cerebral wrote:As for the arch= question, not a lot of package submitters/maintainers in the AUR have an x86_64 system, so they don't know whether or not it compiles on Arch64 - they can't put arch=(x86_64) unless they can verify it in some way.  Also, the arch= tag is fairly new, so I'd imagine some people don't even know it exists - in general they should be using it though.
Oh that makes sense
Haven't had any issue while running rtorrent's built with Arch64's makepkg.conf defaults flags (ok, with 'march=athlon64') as I still use ${CXXFLAGS} even on the latest 0.6.4 release. Maybe I'm lucky.
In fact rtorrent on arch64 is slower to be responsive after it started than on arch i686 (where I use the community package i guess).
Then after a minute it's fully functionnal, and's doing an amazing job here I dunno how to recognize "out-of-memory errors" unless they print something on the console.
codemac : strange. I wouldn't worry if I was you. Some others linuxtracker registered users also use lib/rtorrent. But never one has had version up-to-date to Arch's
:?  pliz excuse my poor English; it's getting pretty late here