On Mar 16, 2009, at 4:48 PM, Yves Dorfsman wrote:
> Beyond that... everything just worked fine.
My $.02: The biggest x86_64 problem I ran into on the RH-derived
variants -- and I second your caveat that it's been a little while
since I did this but the fundamentals haven't changed afaik -- was
that i386 and x86_64 builds of the same package are allowed to
overwrite each other's files. So you end up with the really bad
situation where
# tail -1 ~/.rpmmacros
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
# rpm -q -f /usr/bin/mysql_config
mysql-5.0.22-2.2.el5_1.1.i386
mysql-5.0.22-2.2.el5_1.1.x86_64
# mysql_config --libs
-L/usr/lib64/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib64 -
lssl -lcrypto
and there's no way to get your i386 program back or use autoconf to
build new stuff linked against it.
There's been some discussion about this around the net; the ones I
bookmarked are
http://lwn.net/Articles/184092/
http://www.mail-archive.com/[email protected]/msg10394.html
This is the situation I have the most direct experience with, but I
think other mixed-arch systems have similar problems. If you can run a
no-i386 setup (I think there's a 'pure64' Debian option) that'd be
ideal; personally I haven't had that luxury at work so I am stuck in
i386 userland.
-=Eric
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
