Hello Julien,
On Sun, 28 Nov 2010, Julien BLACHE wrote:
Tomas Pospisek <[email protected]> wrote:
Hi Tomas,
So I'd say it seems to be a problem with libsane and that the problem
was introduced between 1.0.20-13ubuntu2 and 1.0.21-2ubuntu2 aka
1.0.21-7(debian).
Should I take this to the sane devel list? Or try to compile out of git?
Bisecting isn't going to be easy, due to the insane amount of merge
commits in the tree (I wish people would rebase before pushing...), but
you can give it a try.
There are 50 commits between RELEASE_1_0_20 and RELEASE_1_0_21 affecting
the pixma backend, provided the issue is in the backend and not in
support code (though it's likely in the backend).
Just had a look at a446ecec31744ac57c7d971690eb4c4a843943e6, which
affects the MP600; reverting that is worth a try.
I built with that patch reverted - but the problem persisted.
When building SANE, set BACKENDS=pixma at configure time to restrict the
build to just that backend. Then grab the backend from backend/.libs and
try it out.
That was a valuable advice, thank you! That substantially reduced the
amount of time needed for rebuilding and testing with xsane.
If you have some more suggestions then I'll be very glad to hear them.
Lacking better alternatives I'll try to bisect if I find the time.
Do you advise me to do a 'configure && make' after each bisect or should a
simple 'make' suffice? I have the impression that at some point after
1.0.20 the '--enable-pthreads' parameter for 'configure' was introduced,
which would mean that I will also have to change 'configure' parameters at
each 'git checkout~revision'? Is that correct? Or will I be able to just
make, make, make untill I find the 'bad' commit?
*t
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
