Hi André, Sorry about the delay, I've been trying to get X working in a chroot but a known bug is making the keyboard and mouse not work... Copying my sid chroot into its own partition now to try to boot and test there. On Thu, 2010-03-11 at 17:23 +0100, Andre Espaze wrote: > > > The last working version was actually the -4: > > > > > > c56f196854092f0dc0d222de71de1a4532f214ec > > > Release 5.1.3-4 "Look ma, it builds!" > > > > That's what I thought. I tried that one today (backported to Ubuntu > > Karmic), and it didn't work. I guess I'll have to bring X up in the > > chroot to check it there, then start the bisect process. > It still does not work but I wanted to let you know where I am. > I have worked at revision: > 862cebe157a4ce50984d6fc15758da7d3ca96e2a > Thu Mar 4 20:29:30 2010 > By applying the following patches on the KERNEL module: > kernel-safe-include.patch > kernel-mpi-includes.patch > kernel-mpi-libs.patch > kernel-hdf5-needs-mpi.patch > kernel-remove-mpi-undefs.patch > and: > gui-mpich-mpi.patch > on the GUI one, it works when installing it by hand in a local > directory (I have used ~/sroot/). However it does not work when > following the debian/rules install path. I thought that lines 206 > and 207 of debian/rules where the problem: > > mv debian/tmp/usr/bin/*.py \ > $(CURDIR)/debian/tmp/usr/lib/python2.5/*-packages/salome/ > chmod -x $(CURDIR)/debian/tmp/usr/lib/python2.5/*-packages/salome/* > > but it is not enough to make it works. I thought that might be an issue too. You might also try commenting the lines which delete the .pyc (and maybe .pyo) files from /usr/bin. Together they are supposed to make the package more efficient by shipping just .py files and having them compile at install time, but it seems like it will take some time to let Salomé know that those files are not in /usr/bin. > For all the processing at > line 200, I do not understand where the files are. By running for > example: > > find /usr/ -name config_appli.xml > > I do not find anything however I can find this file in my local ~/sroot > directory. However I may have messed the install process, I am running > a new build now. > > Then I guess that we need to build Salome with hdf5 including mpi > because we can not force the user to use libhdf5-serial when he will > want to install Salome. Dealing with patches make the debuging harder > for getting a first running version but I think that you have solved the > problem. I have tried with and without hdf5 and I get the same behavior > for the KERNEL part. Indeed. I am still waiting for the HDF5/GIS team to fix bug 510057 which has had a patch for six weeks now, so we can upload the new MED and not have to use out-of-archive packages... > I keep you in touch once my new version is running, I am getting > more confortable with the Debian packaging tools. Thanks, I'll let you know if I can test the unstable packages, so we can start a git bisect. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/
Attachment:
signature.asc
Description: This is a digitally signed message part