On Mon, Aug 30, 2010 at 11:59:38PM +0200, Bertrand Juglas wrote: > But it's only built for x86 and not yet for x86_64 as my foresight > laptop is only x86. > After all troves are updated for x86 i will look for a x86_64 machine > to build and commit x86_64 binaries. > I imagine it will be faster to build first only for x86 and after > finishing for x86, to setup a x86_64 to build for x86_64. > Thank you for your friendly support ;)
for testing with cvc cook x86 should be fine. (but don't take my word for it, better let someone like doniphon confirm that :-) for commiting i think it is a good habit to always commit x86_64 and x86 together, to make sure x86_64 is not forgotten. (also, because x86_64 machines can install x86 packages, it could lead to people involuntarily mixing x86_64 and x86.) if you can't make a x86_64 binary you can always just commit the source and let someone else build the binaries. greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix searching contract jobs: debugging, programming, training and administration -- pike programmer working in china community.gotpike.org foresight developer (open-steam|caudium).org foresightlinux.org unix sysadmin iaeste.at realss.com Martin Bähr http://www.iaeste.at/~mbaehr/ is.schon.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
