Hallo, Hugo, Du meintest am 06.06.12:
>>> However, the third line with the problem looks like something out >>> of date. Possibly a mis-merge? >> >> Where should I search? > Well, the first thing would be to try a completely new clone of > the repo, then git co integration-20120605, and run make again. I had a brand new git clone. Produced with [...] git clone http://git.darksatanic.net/repo/btrfs-progs-unstable.git cd btrfs-progs-unstable git checkout integration-20120605 (and "btrfs-progs-unstable" had been empty before "checkout") > If > that's OK, then take a look with gitk in the broken repo and see what > kind of history you've got in there -- it should be a single unbroken > sequence from "master" (1957076ab4fefa47b6efed3da541bc974c83eed7) to > "integration-20120605" (d4c539067d1cb2476c7fb6003625de26e84059af). I don't know much about working with git ... but I suppose I'm not working with such things as a (broken) repo. It's the same way I had successfully compiled your version from 20111012 and from 20111030. Is there any change compiling the new version? Viele Gruesse! Helmut -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
