Package Details: cnijfilter-mp620 3.00-4

Git Clone URL: (read-only, click to copy)
Package Base: cnijfilter-mp620
Description: Canon drivers for the MP610/MP620/MP630 printer/scanner with improved PPD files
Upstream URL:
Licenses: custom
Conflicts: cnijfilter-common, ppd-mp620-630
Submitter: mouse256
Maintainer: None
Last Packager: Bevan
Votes: 7
Popularity: 0.000000
First Submitted: 2010-09-02 18:58
Last Updated: 2015-07-08 12:15

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

Anonymous comment on 2013-01-29 19:36

WORKS!!! Well done and thank you so much! :)

cippaciong commented on 2013-01-27 14:24

You really don't have to worry, the work you are doing with this ia amazing.
Thank you!

mouse256 commented on 2013-01-27 08:42

Sorry for the delay guys, I've been rather busy.
I used a patch from the mp280, it's now compiling again.

mouse256 commented on 2013-01-14 08:36

This package is not out-of-date, there's no new upstream version. It's just not compiling anymore.
I'll try to fix it when I've some time.

Anonymous comment on 2013-01-12 23:22

I try to use de solution for mp250:
1)install the older version of automake-1.11 from AUR
2)add this line to build() {
export CC="gcc -m32 -D_IPP_PRIVATE_STRUCTURES"
mkdir -p ${srcdir}/automake-path
ln -sfn /usr/bin/automake-1.11 ${srcdir}/automake-path/automake
ln -sfn /usr/bin/aclocal-1.11 ${srcdir}/automake-path/aclocal
export PATH="${srcdir}/automake-path:$PATH"
3)you can remove automake-1.11 and install automake-1.13.1-1 from official repository

but it is not the best solution! the problem is the version of automake actually (automake-1.13.1-1).

Anonymous comment on 2013-01-12 22:56

I have this build() error! i'm not able to solve it. i hope that this log can help you!

patching file backend/src/cnij_backend_common.c
patching file cngpijmon/src/bjcupsmon_cups.c
patching file cnijfilter/
patching file cnijfilter/src/bjfimage.c
Hunk #1 succeeded at 1521 (offset 1 line).
Hunk #2 succeeded at 1575 (offset 1 line).
patching file cnijfilter/src/bjfoption.c
patching file canonmp620-630en.ppd
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./'
libtoolize: You should add the contents of the following files to `aclocal.m4':
libtoolize: `/usr/share/aclocal/libtool.m4'
libtoolize: `/usr/share/aclocal/ltoptions.m4'
libtoolize: `/usr/share/aclocal/ltversion.m4'
libtoolize: `/usr/share/aclocal/ltsugar.m4'
libtoolize: `/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in
Running aclocal ...
aclocal: warning: autoconf input should be named '', not '' error: 'AM_CONFIG_HEADER': this macro is obsolete.
You should use the 'AC_CONFIG_HEADERS' macro instead.
/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
Running autoheader...
autoheader: error: AC_CONFIG_HEADERS not found in
Running automake --gnu ...
automake: warning: autoconf input should be named '', not '' error: no proper invocation of AM_INIT_AUTOMAKE was found. You should verify that invokes AM_INIT_AUTOMAKE, that aclocal.m4 is present in the top-level directory, and that aclocal.m4 was recently regenerated (using aclocal) installing './install-sh' installing './COPYING' using GNU General Public License v3 file Consider adding the COPYING file to the version control system for your code, to avoid questions about which license your project uses
automake: warning: autoconf input should be named '', not ''
buftool/ error: library used but 'RANLIB' is undefined
buftool/ The usual way to define 'RANLIB' is to add 'AC_PROG_RANLIB'
buftool/ to '' and run 'autoconf' again.
buftool/ installing './depcomp'
/usr/share/automake-1.13/am/ error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/ The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.13/am/ to '' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.13/am/ error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/ The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.13/am/ AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.13/am/ AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.13/am/ to '' and run 'aclocal' and 'autoconf' again
paramlist/ error: Libtool library used but 'LIBTOOL' is undefined
paramlist/ The usual way to define 'LIBTOOL' is to add 'LT_INIT'
paramlist/ to '' and run 'aclocal' and 'autoconf' again.
paramlist/ If 'LT_INIT' is in '', make sure
paramlist/ its definition is in aclocal's search path.
Running autoconf ... error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation. error: possibly undefined macro: AM_CONFIG_HEADER error: possibly undefined macro: AM_PROG_LIBTOOL
Running ./configure --prefix=/usr ...
./configure: line 2181: syntax error near unexpected token `buftool,'
./configure: line 2181: `AM_INIT_AUTOMAKE(buftool, 1.0.0)'

cippaciong commented on 2013-01-07 19:35

Seems like is not compiling anymore. :s

Running ./configure --prefix=/usr --libdir=/usr/lib32 ...
./configure: line 2181: syntax error near unexpected token `buftool,'
./configure: line 2181: `AM_INIT_AUTOMAKE(buftool, 1.0.0)'
==> ERROR: A failure occurred in build().

Take also a look at this too:

mouse256 commented on 2012-11-30 19:49

I don't think you can rename a package. You can submit a new package with a new name, but that would leave this orphaned and even more confusing. I don't see a way to delete it.
And I added mp610/630 to the description, so it should be fairly easy to find it using the search.

cippaciong commented on 2012-11-30 17:50

@mouse256: Don't know either... =)
Do you think that is advisable to change the name of the package too, making it suitable also for 610 and 630?

mouse256 commented on 2012-11-30 15:53

@Cippaciong: Indeed I remember vague. Don't remember why I did reject it back then...

@Zou: I had to do quite some hacking to get the driver compiling on a recent distribution. And as there is no specific driver for the mp620 for linux, this is exactly the same as the mp610

Anyway: changes:
* put mp610 and mp630 also in the description as the driver works for those too
* added ppd file for the mp610 (the one for the 630 is the same as the 620)
* added udev rules for 610 and 620. I don't know the values for the 630...