Re: how to do science with amd64 lenny

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Fri, Jun 18, 2010 at 02:57:16PM +0200, Dimitris Lampridis wrote:
> I was about to suggest something similar:
> 
> 1) Add the deb-src for debian testing in your sources.list
> 2) apt-get update
> 3) apt-get source mpich2
> 4) apt-get build-dep mpich2
> 5) cd mpich2-1.2.1.1 (or whatever the name of the created folder)
> 6) dpkg-buildpackage -uc -us
> 7) cd ..
> 8) dpkg -i *.deb

If you are doing that then you can do:
1) Add the deb-src for debian testing in your sources.list
2) apt-get update
3) apt-get build-dep mpich2
4) apt-get source mpich2 -b
5) dpkg -i *.deb

> So you first add the source packages of debian testing, you update, you pull 
> the source package of mpich2, then you pull all the required packages to build 
> mpich2, and finally you build it. If all goes well, the deb packages will be 
> produced in the parent folder.
> 
> There is one catch: in the 4th step, where you pull the build dependencies, it 
> could be that you are missing something in the stable distribution. In that 
> case, you have to "pause" the mpich2 build process, and first do the same 
> trick for any missing packages.

Fortunately my test build seemed to indicate that wouldn't be a problem
in this case.  At least that's what I saw.  I do have a few backported
packages installed already so who knows.

> So, if you are missing some "X" build dependency, then you should first pull 
> the source of "X", its build dependencies, build it, install it and then try 
> again the build-dep command, until it does not complain about anything 
> missing.

-- 
Len Sorensen