Cups-canon-3.00 build issue
Hi, I'm having trouble installing this package cups-canon-3.00 from AUR, here is the entire output http://pastebin.com/Ya1d2u0D .
I modified the PGKBUILD from:
MODELS=(ip1900 ip3600 ip4600 mp190 mp240 mp540 mp630)
to
MODELS=(mp240)
to build only for my printer but gives the same error if I leave it unchanged.
At the end (almost, line 929) it complains about an unrecognized option:
configure: WARNING: unrecognized options: --enable-progpath
If you have an idea about my problem please leave a reply.
Thanks in advance.
The package updated an now it builds correctly.
Similar Messages
-
Could not build cups-canon-3.00 from AUR
Hi!
I'm coming from linux mint and I'm totally amazed by simplicity of Arch Linux. However, I have problem with installing my printer (Canon IP1900). I'm unable to install canon-cups-3.00 from AUR (using yaourt). It gives me this error:
==> Zaczynam build()
patching file backend/src/cnij_backend_common.c
patching file cngpijmon/src/bjcupsmon_cups.c
......... libs
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:4: 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...
configure.in:4: 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 configure.in
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal)
configure.in:9: installing './install-sh'
Makefile.am: installing './COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your project uses
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
buftool/Makefile.am:1: error: library used but 'RANLIB' is undefined
buftool/Makefile.am:1: The usual way to define 'RANLIB' is to add 'AC_PROG_RANLIB'
buftool/Makefile.am:1: to 'configure.in' and run 'autoconf' again.
buftool/Makefile.am: installing './depcomp'
/usr/share/automake-1.13/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.13/am/depend2.am: to 'configure.in' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.13/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.13/am/depend2.am: AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.13/am/depend2.am: AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.13/am/depend2.am: to 'configure.in' and run 'aclocal' and 'autoconf' again
paramlist/Makefile.am:1: error: Libtool library used but 'LIBTOOL' is undefined
paramlist/Makefile.am:1: The usual way to define 'LIBTOOL' is to add 'LT_INIT'
paramlist/Makefile.am:1: to 'configure.in' and run 'aclocal' and 'autoconf' again.
paramlist/Makefile.am:1: If 'LT_INIT' is in 'configure.in', make sure
paramlist/Makefile.am:1: its definition is in aclocal's search path.
Running autoconf ...
configure.in:2: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:4: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:11: error: possibly undefined macro: AM_PROG_LIBTOOL
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
configure: WARNING: unrecognized options: --enable-progpath
./configure: line 2181: syntax error near unexpected token `buftool,'
./configure: line 2181: `AM_INIT_AUTOMAKE(buftool, 1.0.0)'
==> BŁĄD: Wystąpił błąd w build().
Przerywam...
==> ERROR: Makepkg was unable to build cups-canon-3.00.
I tried downgrading automake to 1.11 from AUR, but then, when I try to compile cups-canon-3.00 it just gives me error, that I don't have automake (yes, I did "export automake=automake-1.11").
I'm fighting with it for hours, and still nothing...It looks like this time it changed something so I gave it two tries again:
Before 1st autogen:
==> Zaczynam build()
patching file backend/src/cnij_backend_common.c
patching file cngpijmon/src/bjcupsmon_cups.c
......... libs
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:2: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_INIT_AUTOMAKE-invocation
configure.in:11: installing './config.guess'
configure.in:11: installing './config.sub'
configure.in:2: installing './install-sh'
configure.in:2: installing './missing'
Makefile.am: installing './COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your project uses
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
buftool/Makefile.am: installing './depcomp'
Running autoconf ...
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
configure: WARNING: unrecognized options: --enable-progpath
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for dup2... yes
checking for memset... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating buftool/Makefile
config.status: creating paramlist/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --enable-progpath
Now type `make' to compile buftool
make all-recursive
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
Making all in paramlist
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c -o paramlist.lo paramlist.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c paramlist.c -fPIC -DPIC -o .libs/paramlist.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c paramlist.c -o paramlist.o >/dev/null 2>&1
mv -f .deps/paramlist.Tpo .deps/paramlist.Plo
/bin/sh ../libtool --tag=CC --mode=link gcc -O2 -Wall -O2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o libparamlist.la paramlist.lo
libtool: link: ar cru .libs/libparamlist.a .libs/paramlist.o
libtool: link: ranlib .libs/libparamlist.a
libtool: link: ( cd ".libs" && rm -f "libparamlist.la" && ln -s "../libparamlist.la" "libparamlist.la" )
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
Making all in buftool
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -MT buftool.o -MD -MP -MF .deps/buftool.Tpo -c -o buftool.o buftool.c
mv -f .deps/buftool.Tpo .deps/buftool.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -MT buflist.o -MD -MP -MF .deps/buflist.Tpo -c -o buflist.o buflist.c
mv -f .deps/buflist.Tpo .deps/buflist.Po
rm -f libbuftool.a
ar cru libbuftool.a buftool.o buflist.o
ranlib libbuftool.a
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
Making install in paramlist
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
Making install in buftool
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
......... cngpij
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:2: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_INIT_AUTOMAKE-invocation
configure.in:20: installing './config.guess'
configure.in:20: installing './config.sub'
configure.in:2: installing './install-sh'
configure.in:2: installing './missing'
cngpij/Makefile.am: installing './depcomp'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoconf ...
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for main in -lcups... yes
checking for main in -lparamlist... no
checking for main in -lpopt... yes
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for socket... yes
checking for strdup... yes
checking for strrchr... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating cngpij/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Now type `make' to compile
make all-recursive
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
Making all in cngpij
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../include/cncl -I../include/misc -I../../libs/paramlist -O2 -MT bjcups.o -MD -MP -MF .deps/bjcups.Tpo -c -o bjcups.o bjcups.c
mv -f .deps/bjcups.Tpo .deps/bjcups.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../include/cncl -I../include/misc -I../../libs/paramlist -O2 -MT getipc.o -MD -MP -MF .deps/getipc.Tpo -c -o getipc.o getipc.c
getipc.c: In function ‘GetIPCData’:
getipc.c:63:48: warning: passing argument 3 of ‘accept’ from incompatible pointer type [enabled by default]
In file included from /usr/include/netinet/in.h:24:0,
from /usr/include/arpa/inet.h:22,
from getipc.c:21:
/usr/include/sys/socket.h:244:12: note: expected ‘socklen_t * __restrict__’ but argument is of type ‘size_t *’
mv -f .deps/getipc.Tpo .deps/getipc.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../include/cncl -I../include/misc -I../../libs/paramlist -O2 -MT bjutil.o -MD -MP -MF .deps/bjutil.Tpo -c -o bjutil.o bjutil.c
mv -f .deps/bjutil.Tpo .deps/bjutil.Po
/bin/sh ../libtool --tag=CC --mode=link gcc -O2 -Wall -I../include/cncl -I../include/misc -I../../libs/paramlist -O2 -L../../libs/paramlist -Wl,-O1,--sort-common,--as-needed,-z,relro -o cngpij bjcups.o getipc.o bjutil.o -lpopt -lcups -lparamlist -lpopt -lcups
libtool: link: gcc -O2 -Wall -I../include/cncl -I../include/misc -I../../libs/paramlist -O2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o cngpij bjcups.o getipc.o bjutil.o -L../../libs/paramlist /tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist/.libs/libparamlist.a -lpopt -lcups
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
Making install in cngpij
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
/usr/bin/mkdir -p '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/bin'
/bin/sh ../libtool --mode=install /usr/bin/install -c cngpij '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/bin'
libtool: install: /usr/bin/install -c cngpij /tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/bin/cngpij
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij/cngpij'
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/cngpij'
......... pstocanonij
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:2: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_INIT_AUTOMAKE-invocation
configure.in:22: installing './config.guess'
configure.in:22: installing './config.sub'
configure.in:2: installing './install-sh'
configure.in:2: installing './missing'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
filter/Makefile.am: installing './depcomp'
Running autoconf ...
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for ranlib... ranlib
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... (cached) ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for main in -lcups... yes
checking for main in -lparamlist... no
checking for main in -lpopt... yes
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for dup2... yes
checking for memset... yes
checking for socket... yes
checking for strdup... yes
checking for strrchr... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating filter/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Now type `make' to compile
make all-recursive
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
Making all in filter
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../../libs/buftool -O2 -MT pstocanonij.o -MD -MP -MF .deps/pstocanonij.Tpo -c -o pstocanonij.o pstocanonij.c
pstocanonij.c: In function ‘get_ps_params’:
pstocanonij.c:249:3: warning: pointer targets in passing argument 1 of ‘buflist_new’ differ in signedness [-Wpointer-sign]
In file included from pstocanonij.c:35:0:
../../libs/buftool/buflist.h:38:10: note: expected ‘unsigned char *’ but argument is of type ‘char *’
pstocanonij.c:299:5: warning: value computed is not used [-Wunused-value]
pstocanonij.c:385:3: warning: pointer targets in passing argument 1 of ‘buflist_new’ differ in signedness [-Wpointer-sign]
In file included from pstocanonij.c:35:0:
../../libs/buftool/buflist.h:38:10: note: expected ‘unsigned char *’ but argument is of type ‘char *’
pstocanonij.c: In function ‘make_cmd_param’:
pstocanonij.c:905:6: warning: format ‘%s’ expects argument of type ‘char *’, but argument 4 has type ‘char (*)[256]’ [-Wformat]
pstocanonij.c:906:6: warning: format ‘%s’ expects argument of type ‘char *’, but argument 4 has type ‘char (*)[256]’ [-Wformat]
pstocanonij.c:935:6: warning: format ‘%s’ expects argument of type ‘char *’, but argument 4 has type ‘char (*)[256]’ [-Wformat]
pstocanonij.c:936:6: warning: format ‘%s’ expects argument of type ‘char *’, but argument 4 has type ‘char (*)[256]’ [-Wformat]
pstocanonij.c: In function ‘exec_filter’:
pstocanonij.c:1133:6: warning: variable ‘status’ set but not used [-Wunused-but-set-variable]
mv -f .deps/pstocanonij.Tpo .deps/pstocanonij.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../../libs/buftool -O2 -MT canonopt.o -MD -MP -MF .deps/canonopt.Tpo -c -o canonopt.o canonopt.c
mv -f .deps/canonopt.Tpo .deps/canonopt.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -I../../libs/buftool -O2 -MT paramlist.o -MD -MP -MF .deps/paramlist.Tpo -c -o paramlist.o paramlist.c
mv -f .deps/paramlist.Tpo .deps/paramlist.Po
/bin/sh ../libtool --tag=CC --mode=link gcc -O2 -Wall -I../../libs/buftool -O2 -L../../libs/buftool -Wl,-O1,--sort-common,--as-needed,-z,relro -o pstocanonij pstocanonij.o canonopt.o paramlist.o -lcups ../../libs/buftool/libbuftool.a -lpopt -lcups
libtool: link: gcc -O2 -Wall -I../../libs/buftool -O2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o pstocanonij pstocanonij.o canonopt.o paramlist.o -L../../libs/buftool ../../libs/buftool/libbuftool.a -lpopt -lcups
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
Making install in filter
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
/usr/bin/mkdir -p '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/filter'
/bin/sh ../libtool --mode=install /usr/bin/install -c pstocanonij '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/filter'
libtool: install: /usr/bin/install -c pstocanonij /tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/filter/pstocanonij
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij/filter'
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/pstocanonij'
......... backend
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:2: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_INIT_AUTOMAKE-invocation
configure.in:19: installing './config.guess'
configure.in:19: installing './config.sub'
configure.in:2: installing './install-sh'
configure.in:2: installing './missing'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
src/Makefile.am: installing './depcomp'
src/Makefile.am:10: warning: 'CFLAGS' is a user variable, you should not override it;
src/Makefile.am:10: use 'AM_CFLAGS' instead
Running autoconf ...
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for main in -lcups... yes
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for socket... yes
checking for strdup... yes
checking for strrchr... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Now type `make' to compile
make all-recursive
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
Making all in src
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -MT cnij_backend_common.o -MD -MP -MF .deps/cnij_backend_common.Tpo -c -o cnij_backend_common.o cnij_backend_common.c
mv -f .deps/cnij_backend_common.Tpo .deps/cnij_backend_common.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -MT cnij_usb.o -MD -MP -MF .deps/cnij_usb.Tpo -c -o cnij_usb.o cnij_usb.c
cnij_usb.c: In function ‘main’:
cnij_usb.c:97:7: warning: unused variable ‘port’ [-Wunused-variable]
cnij_usb.c:94:4: warning: unused variable ‘username’ [-Wunused-variable]
cnij_usb.c:93:4: warning: unused variable ‘hostname’ [-Wunused-variable]
cnij_usb.c:92:7: warning: unused variable ‘method’ [-Wunused-variable]
mv -f .deps/cnij_usb.Tpo .deps/cnij_usb.Po
/bin/sh ../libtool --tag=CC --mode=link gcc -O2 -Wall -Wl,-O1,--sort-common,--as-needed,-z,relro -o cnijusb cnij_backend_common.o cnij_usb.o -lcups -lcups
libtool: link: gcc -O2 -Wall -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o cnijusb cnij_backend_common.o cnij_usb.o -lcups
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
Making install in src
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
/usr/bin/mkdir -p '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/backend'
/bin/sh ../libtool --mode=install /usr/bin/install -c cnijusb '/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/backend'
libtool: install: /usr/bin/install -c cnijusb /tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/pkg/usr/lib/cups/backend/cnijusb
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend/src'
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/backend'
. ip1900
.......... lgmon
processing .
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:12: 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...
configure.in:12: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: error: echo failed with exit status: 1
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
autoheader: error: AC_CONFIG_HEADERS not found in configure.in
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal)
src/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
src/Makefile.am: installing './depcomp'
/usr/share/automake-1.13/am/depend2.am: error: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'am__fastdepCC' is to add 'AC_PROG_CC'
/usr/share/automake-1.13/am/depend2.am: to 'configure.in' and run 'aclocal' and 'autoconf' again
/usr/share/automake-1.13/am/depend2.am: error: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.13/am/depend2.am: The usual way to define 'AMDEP' is to add one of the compiler tests
/usr/share/automake-1.13/am/depend2.am: AC_PROG_CC, AC_PROG_CXX, AC_PROG_OBJC, AC_PROG_OBJCXX,
/usr/share/automake-1.13/am/depend2.am: AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.13/am/depend2.am: to 'configure.in' and run 'aclocal' and 'autoconf' again
Running autoconf ...
configure.in:11: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:12: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:27: error: possibly undefined macro: AM_PROG_CC_STDC
configure.in:31: error: possibly undefined macro: AM_PATH_GTK_2_0
Running ./configure --prefix=/usr --enable-libpath=/usr/lib/bjlib --enable-binpath=/usr/bin --enable-progpath=/usr/bin --program-suffix=ip1900 ...
configure: WARNING: unrecognized options: --enable-libpath, --enable-binpath
./configure: line 1886: syntax error near unexpected token `lgmon{program_suffix},'
./configure: line 1886: `AM_INIT_AUTOMAKE(lgmon{program_suffix}, 3.00-1)'
==> BŁĄD: Wystąpił błąd w build().
Przerywam...
Before both:
==> Zaczynam build()
patching file backend/src/cnij_backend_common.c
patching file cngpijmon/src/bjcupsmon_cups.c
......... libs
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
Running automake --gnu ...
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:2: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated. For more info, see:
configure.in:2: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_INIT_AUTOMAKE-invocation
configure.in:11: installing './config.guess'
configure.in:11: installing './config.sub'
configure.in:2: installing './install-sh'
configure.in:2: installing './missing'
Makefile.am: installing './COPYING' using GNU General Public License v3 file
Makefile.am: Consider adding the COPYING file to the version control system
Makefile.am: for your code, to avoid questions about which license your project uses
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
buftool/Makefile.am: installing './depcomp'
Running autoconf ...
Running ./configure --prefix=/usr --enable-progpath=/usr/bin ...
configure: WARNING: unrecognized options: --enable-progpath
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for dup2... yes
checking for memset... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating buftool/Makefile
config.status: creating paramlist/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --enable-progpath
Now type `make' to compile buftool
make all-recursive
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
Making all in paramlist
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c -o paramlist.lo paramlist.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c paramlist.c -fPIC -DPIC -o .libs/paramlist.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -O2 -Wall -O2 -MT paramlist.lo -MD -MP -MF .deps/paramlist.Tpo -c paramlist.c -o paramlist.o >/dev/null 2>&1
mv -f .deps/paramlist.Tpo .deps/paramlist.Plo
/bin/sh ../libtool --tag=CC --mode=link gcc -O2 -Wall -O2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o libparamlist.la paramlist.lo
libtool: link: ar cru .libs/libparamlist.a .libs/paramlist.o
libtool: link: ranlib .libs/libparamlist.a
libtool: link: ( cd ".libs" && rm -f "libparamlist.la" && ln -s "../libparamlist.la" "libparamlist.la" )
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
Making all in buftool
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -MT buftool.o -MD -MP -MF .deps/buftool.Tpo -c -o buftool.o buftool.c
mv -f .deps/buftool.Tpo .deps/buftool.Po
gcc -DHAVE_CONFIG_H -I. -I.. -O2 -MT buflist.o -MD -MP -MF .deps/buflist.Tpo -c -o buflist.o buflist.c
mv -f .deps/buflist.Tpo .deps/buflist.Po
rm -f libbuftool.a
ar cru libbuftool.a buftool.o buflist.o
ranlib libbuftool.a
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
Making install in paramlist
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/paramlist'
Making install in buftool
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs/buftool'
make[1]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Wejście do katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[2]: Nie ma nic do zrobienia w `install-exec-am'.
make[2]: Nie ma nic do zrobienia w `install-data-am'.
make[2]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
make[1]: Opuszczenie katalogu `/tmp/yaourt-tmp-kierek/aur-cups-canon-3.00/src/cnijfilter-common-3.00/libs'
......... cngpij
processing .
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
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 configure.in and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
Running aclocal ...
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Running autoheader...
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation. -
My setup: iMac hardline to Canon i960 printer. Issue: endless printing of the same document. The printer window states that the pinter is in use and there is nothing listed in the Print Queue. How can I stop printing the document?
Soution: Delete the printer and add the same printer back in, therefore creating a new print queue.
-
My T420 (4177 CTO) is still under factory warrenty, so it is less than a year old. There are two build issues that I have so far ignored, but I am wondering if they are "normal."
The laptop does not rest level on a flat surface. Three of the rubber grips on the underside touch the surface, but the front, left grip is so far off the surface that you can slide a piece of paper under it without resistence. When I rest my left hand on the palmrest, the chassis audibly "creaks" and visibly moves as the rubber grip comes to rest on the surface.
Just recently permanent friction marks have appeared on the left half of my screen, clearly caused by months of rubbing against the keyboard. I have tried cleaning them per Lenovo's instructions, to no avail.
I am beginning to think that the chassis is deformed, and that it has been this way since I received the machine. Both issues have been present since the start, but the marks on the screen could be easily wiped off until recently.
Are these issues "normal," or am I suffering from a defective machine?
Thanks for your opinion or any information!My T420 has spent its life in a backpack, as did the T400 and T61 before it. I've never noticed this kind of problem.
Have you taken a careful look at the sides of the laptop to verify that the keyboard bezel and bottom plastic are snapped together correctly? Any gaps or bulges?
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество -
Week 25 Whine, Heat, Build Issues Finally Fixed!
I received a week 25 MBP yesterday and I can say that Apple has finally got it right.
I have had numerous problems with previous machines ranging from bad video cards, dropped wifi connections, broken latches and the infamous heat and whine problems.
This new machine is absolutely perfect. Here are my observations:
- Absolutely no whine under battery or while plugged in (even when the machine is idle)
- Heat does not exceed 42c on normal tasks and the machine idles at 37c-40c.
- The case is barley warm to the touch.
- Wifi range and performance is excellent.
- No cosmetic build issues such as warped lid or broken latch.
I wholehartedly recommdend people who have been waiting to go ahead and make your purchases.it appears apple has fianlly figured out new power cicutry for the mobo to cpu that no longer whines. there's an article about a macintouch editor (or writer i forget, he works for them) who just got it back with a letter, and no longer has any whine, at all.
I'm going to talk to my apple place this week adn see if i can get htem to replace it again, its clearly a whine on my new logic board, so i don't see why they wouldnt - i'll jsut tell them ti is loud as they know, just hopw they wont say something like 'no, we already did it'.
anyway, good luck everyone ill wait a week ro so to try to help get the very newest rev of mobo
edit: forgot the link! http://macdailynews.com/index.php/weblog/comments/10076/ -
Hello!
I'm stuck on something pertaining to my release build. It's not working. I know there could be a lot of reasons for this, most related to path dependencies within my code. In my troubleshooting, however, I've stumbled across an issue that I think is at the root of the problem. I'm hoping someone has a solution!
Here it is:
I'm using Flex Builder 3, and it's an AS3 project. Running the project is no problem. Works great from the bin-debug folder. As soon as I pull the files in the bin-debug folder into another folder, however, it no longer runs. I'm doing this in the most basic way possible. Here are the steps I'm taking:
1. create a new folder at the same level as bin-debug. Calling it, creatively, bin-debug2.
2. copying all the files in bin-debug and pasting them in bin-debug2.
3. opening my browser and surfing to bin-debug/project.html - works perfect.
4. opening my browser and surfing to bin-debug2/project.html - doesn't work.
How is it possible for the exact same files not to work just because the parent folder has a different name?
I believe answering this will solve my release build issues.
Thanks!!Hi Greg,
Thank you for taking time to help me troubleshoot this.
Running the bin-debug version of the projects main .html page in a browser works. Meaning, the page loads, I see the default background color I've set in the compiler, and the opening animation starts.
Then I copy and paste all of the files in bin-debug to bin-debug2. Try running the exact same .html file. The page opens in the browser and I see the default background color I've set in the compiler. The opening animation never starts.
Thanks,
Jake -
Canon Vixia HV30 capture issue on CS6 (Mac OSX)
This might be (hopefully) something in setup, but under Mac OSX Lion (10.7.4) / Premiere CS6, i am unable to capture video from my Canon Vixia HV30 - it's either i get a monstruous noise or simply get a 'capture device offline' message.
No one ever had a similar problem even withanother cam here? I posted weeks ago but never got any reply.
Am using the same cam under Windows with Premiere CS4 and never faced such an issue.
Matter of some sort of CODEC ? Does not seem to require any specific driver for Mac based on Canon website.
Any suggestion?
Thanks,
RobSolved... (Almost!)
Someone pointed out that Canon has a software (they said there was no driver for Mac OS X so I had stopped looking...) But if it may help others, there is a ''CameraWindow'' for Mac OS X 10.6, 10.7 and 10.8 available.
As soon as I installed it, I could capture both from Adobe Premiere CS6 and iMovie.
One problem remaining though : the noise (feedback-like) that gets out from... the system's sound card ! (when capture is ongoing). I have to shut down the volume completely. Never had this issue under Windows, need to figure out why this happens now.
Jeff thanks again for your assistance, even though the solution was somewhere else.
If anyone has a clue for the noise issue ... please let me know
Rob -
Report Service And Report Builder Issue
SQL SERVE 2012
In our web site project we use ReportingService2010 Methods to show and operate folder and report which stored in Report Service, in our project configuration file, we use windows authentication mode for Report Service.
In requirement
User can show and operate folder “A” and folder “B” (we can create and delete report or folder) in web site.
User can’t use “Report Builder” to save reports which created by Report Builder to folder “B”, Reports which created by Report Builder only can be saved in folder “A”.
[User click “Report Builder” button in our web page to start Report Builder, use
“Report Builder” to create report, if user want to save report, we need to hidden folder “B” in “Report Builder” or we need to remove some operate right from folder “B”.]
We have no solution for this requirement, could you help us?Thank you for your replay, but I don't understand it very clearly.
Please check the first requirement:
User can show and operate folder “A” and folder “B” (we can create and delete report or folder) in web site.
For example, I login my PC with account "lfang", in report server, we grand "Browse" permission on both folder and grand only "Publish" permissions for folder "A", report builder can't save report into folder "B",
it's correct.
But our web site has create report function, that means in our web site we want to create report for both folder "A" and "B", that is the issue, if we don't give "Publish" permissions to folder
"B", we can't create report in our web site.
Is there any method to run "report builder" use specified account? then we can only give folder "A" "Publish" permissions with specified account. -
Hey folks, looking for some insight here.
I've an implementation that contains some custom Enterprise columns mapped to lookup tables. In the instance I'm working with now, it looks like there was/is an issue with one of those columns. In this scenario, I have a column named
ProjectType, created initially with that name, mapped to a lookup table. This field's name was then changed to
Project Type. After that, it looks like another column was created, also called
ProjectType. So now, we have what I would have originally thought was two distinct columns, even though the names used are the same.
Below is the error we're currently getting during the Cube Build Process...
PWA:http://ps2010/PWA, ServiceApp:Project Web App, User:DOMAIN\user, PSI: SqlException occurred in DAL: <Error><Class>1</Class><LineNumber>1</LineNumber><Number>4506</Number><Procedure>MSP_EpmProject_OlapView_B8546719-4D4C-473A-84B1-89DEDA2307E0</Procedure>
<Message> System.Data.SqlClient.SqlError: Column names in each view or function must be unique. Column name 'ProjectType' in view or function 'MSP_EpmProject_OlapView_B8546719-4D4C-473A-84B1-89DEDA2307E0' is specified more than once. </Message>
<CallStack>
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureNoResult(String storedProcedureName, SqlParameter[] parameters) </CallStack> </Error>
I've tried deleting the one column, but the build still gives the above error.
Any thoughts as to how the above could be resolved?
Thanks! - M
Michael Mukalian | Jan 2010 - Dec 2010 MVP SharePoint Services | MCTS: MOSS 2007 Configuration | http://www.mukalian.com/blogWe tried taking it out of the cubes, and it builds fine. The challenge we're having is in building the cubes with that custom field "ProjectType". It's as if the cubes still hold some reference to it even when it's deleted.
Since the OLAP View ('MSP_EpmProject_OlapView_{guid}') is recreated, would it be as simple as deleting that View, and trying to recreate?
Thanks - M
Michael Mukalian | Jan 2010 - Dec 2010 MVP SharePoint Services | MCTS: MOSS 2007 Configuration | http://www.mukalian.com/blog -
Labview 2012 Installer builder issues with Windows 7 64 bit
I have a clients project application program I am working on and am having a lot of trouble getting installed applications to work on Windows 7 properly. The Labview Installer sets the default installation directory to "c:\Program Files\" on Windows Xp and on Windows 7 64bit this defaults to "C:\Program Files (x86). When I install the application on Windows 7 and run it, because Windows 7 64 bit unreasonably protects this directory and every folder under it, if you try to write file to any subdirectory under it (like a reports directory), windows 7 will not let the file write to the directory and the file(s) disappear and you get permission errors. This has been difficult to address. Even logging in as administrator, I have difficulty changing the folder permissions. In addition, when I am in the file write process, if the default directory is coded to come up in the file Open/Save dialog, will not properly
go to and display these protected directories. So thinking that OK, I'll just chage the install directory to something direct to the C: drive and not the Program Files (x86) directory, so I have better control of the folder permissions. Now the Installer build gives errors. It built, but the install fails. Looks like National did not test this for Windows 7 very well. I have run into just about every issue possible with Windows 7 and Labview. Clearly Labview was not very well tested with Windows 7 6 bit. I do not have the Internet toolkit added to the application, only the VISA 5.2 driver. Anyone else having application issues with Labview and Windows 7 and have ideas how to work around this??
Attachments:
BuildErrors.txt 11 KBIt's no NI's fault and has nothing to do with 64 Bit either. It is something MS changed starting with Vista, namely tightening security of the whole system to a similar level as was usual on more professional OSes like Unix 20 years earlier. A user has not rights anymore to write into the location where applications are installed. This is for one reason to protect installed applications from being modified by malicious code.
Instead every application should write its runtime data in one of the user writable loacations such as the user's Documents directory for data files, or in the user's or the machine's configuration directory for configuration settings. For single installations you could always set the directory which your application got installed into to be user writable by changing the rights of that directory afterwards but for applications that get installed on normal user computers this is a VERY hacky and discouraged move. Same about installing your application into the root of your system drive. I think it was an oversight by MS to not protect that directory too from user modifications, but was most likely unavoidable to allow DOS application installations to still work.
LabVIEW has functions to retrieve a whole bunch of those preconfigured and user writeable locations and you really should change your application to make use of those locations, instead of trying to write into the installation directory or installing the application into the root location of the system drive, if you want to be compatible with Windows Vista/7/8.
Windows 7 also requires for a number of actions such as installing programs or drivers so called elevated rights. This means that even if you are logged in as administrator you have to explicitedly provide the admin password again to be able to perform the action. This can be done by starting the program as administrator, when this is available in the right click pop-up menu, and is also sometimes done automatically for applications that Windows determines to need those rights such as setup programs for installations.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Acrobat 9 and Canon iR-ADV C2030 issues
I have a user running 10.7.5 on a 2ghz MacBook Pro who constantly has issues printing PDFs to various printers. When she prints tabloid PDFs to our copier (Canon iR-ADV C2030), the prints come out fine. When she prints tabloid PDFs to any of our other printers (Xerox Phaser 7750 & 7800, HP LaserJet 5200) the prints come out the wrong size. It looks fine in the preview before she prints. I had reset her printing system, gone into the localhost settings and wiped her preferences. Only happens with PDFs, but it took a while to properly diagnose the issue (very busy user).
After much testing, this is what I've come up with: It ONLY happens with Adobe Acrobat 9, and only after printing to the Canon. The user can first print a tabloid PDF to our HP and Xerox machines with no issue. She can then print to the Canon with no ill effects. But once she prints there, it messes up the Acrobat preferences and she can no longer print tabloid correctly to any other printer but the Canon. The PDFs come out on letter at tabloid size (i.e., top corner oreinted with the rest of the image off the paper). Odd one. The problem does not occur with Acrobat X.Based on what you have written the ADV C5035 does not have the optional Postscript (PS) kit installed. It has nothing to do with any Mavericks update.
So you will have to use the UFR2 driver you mention, which is a Canon proprietary printer language and the default printer kit in the Canon iR devices.
Note that when creating the network print queue you must use the HP Jetdirect-Socket protocol. IPP is not supported by the driver and some users have had issues with the LPD protocol. -
Hello, all. I created a thread with this similar issue a few months ago but never really got it resolved. Instead of reviving an old thread, I decided to just recreate it with updated information.
I have the new Canon S100 and I am having an issue with how the RAW files appear in Lightroom.
I import the photos into a Lightroom catalog and they all look fine within the importer window (which shows essentially what a JPEG would look like), but when I click on the photo in Library or Develop, once the photo finishes loading, the red saturation goes through the roof.
Any photo that already had a little bit of warmth to it exploded with red.
Whereas any photo taken in normal light gains a little more warmth and exposure.
Here are a couple examples of the JPEG preview (also how it looks in-camera) compared with what the RAW looks like once it's been loaded in Lightroom. (The above or left photo is the “normal” version, the bottom/2nd image is the RAW)
It’s sort of difficult to tell with some of the photos by looking at them side-by-side. I also have the individual photos if you want to A/B them to see the changes that are actually occurring.
There are no presets being applied upon import.
The only solution I've found is to convert them all into JPEGs using Canon's software (which does not alter the images as seen above), and edit them in Lightroom as JPEGs, but that completely eliminates the point of buying a camera that is capable of shooting in RAW.
I’ve been having this issue since the S100 first came out (when I purchased it) with Lightroom 3.6RC and was told that it would be fixed in Lightroom 3.6… which it wasn’t… nor was it fixed in Lightroom 4.
I decided to just go ahead and convert all my photos to JPEGs until I found a fix to this so I could at least have my photos (I had photos from my anniversary with my girlfriend in November that I couldn’t do anything with so I was sick of waiting).
I figured I’d wait till more people had the camera, expecting this issue to be more widespread… but now that a lot of people have the S100, I’ve looked around and found no other instances of this happening… so I’m worried it’s something on my end.
I have a 2008 13” MacBook Pro running OSX 10.7.3 and I have the latest version of Lightroom (4.0) and Camera Raw (7.0) installed. I’ve tried the photos in Photoshop CS5 and it does the same thing. When this first happened back in December I tried the photos in Aperture as well and it did the same thing.
The only software that seems to recognize the true color of the photos is Canon’s horrible “professional editing” software.
Thanks in advance.
-PatrickI recently bought an S100 and encountered the same problem. With Camera Standard in Lightroom, Reds are too bright, greens are shifted towards yellow, and some yellows are shifted towards orange.
I have been using Lightroom since the beta, with different cameras from different manufacturers. The camera profiles for the S100 are the worst I have experienced by far. The profiles, particularly all of the profiles that start with "Camera," do not fit this camera. I believe somebody made a mistake. It could have been someone at Canon, it could have been someone at Adobe. I don't expect this mistake to be fixed, or even acknowledged.
Moving on, here is my workaround:
Start with the Powershot S110 Camera Standard profile.
Use dcpTool to decompile the profile.
Open the decompiled profile in a text editor.
At the top, change the name to S110 Standard.
At the bottom, set the baseline exposure offset to zero.
At the bottom, change the model restriction from S110 to S100
Use dcpTool to compile the modified profile. Give the resulting .dcp file a different name than the original.
Put the new .dcp file in the appropriate directory, open Lightroom and apply the S110 Standard profile to your S100 images.
dcpTool is here:
http://dcptool.sourceforge.net/Introduction.html
This hacked S110 profile gets rid of the blazing reds. It does have some problems with yellows and greens. I solve this in Lightroom by using +20 in Camera Calibration: Green Primary: Hue. I haven't had my camera very long, and I may end up making other adjustments in Lightroom. But using the Powershot S110 Camera Standard profile seems like the best place to start.
I tried using Adobe's DNG Profile Editor app on the S110 "Camera" profiles, but did not get good results. From what others have posted on Adobe's forums, this is to be expected. A lot of the "Camera" profiles are too complicated for DNG Profile Editor to work well on. Both the S100 and S110 Camera Standard profiles have over 23,000 lines of code when decompiled!
I also tried dcpTool (and DNG Profile Editor) with some of the other S series and G series profiles, without finding anything that works better than the S110 Camera Standard profile. -
Multi Source execution plan build issue
Hi,
I am trying to create/build a multi source (homogenous) execution plan in DAC from 2 containers for 2 of the same subject areas (Financial Payables) from 2 different EBS sources. I successfully built each individual subject area in each container and ran an executin plan for each individually and it works fine. Now I am trying to create 1 execution plan based on the DAC steps. So far I have done the following:
- Configured all items for both subject areas in the DAC (tables, tasks, task groups, indexesconnections, informatica logical, physical folders, etc)
- Assigned EBS system A a sifferent priority than EBS system B under Setup->Physical Data Sources
- I noticed that I have to change the Physical Folder priorities for each informatica folder (SDE for Container A versus SDE for Container B). I assigned system A a higher priority
- Build the Execution plan..
I am able to build the execution plan successfully but I have the following issues/questions:
1) I assumed that by doing the steps above..it will ONLY execute the extract (SDE) for BOTH system containers but only have ONE Load (SIL and PLP)..and I do see that the SDEs are ok..but I see the SIL for Inder Row in RunTABLE running for BOTH...why is this? When I run the EP...I get an unique constraint index error..since its entering two records for each system. Isnt the DAC suppose to include only one instance of this task?
2) When I build the execution PLAN, it is including the SILOS and PLP tasks from BOTH source system containers (SILOS and PLP folders exist in both containers)...why is this? I thought that there is only one set of LOAD tasks and only SDE are run for each (as this is a homogenous load).
3) What exactly does the Physical folder Priority do? How is this different than the Source System priority? When I have a multi source execution plan, do I need to assign physical folder priorites to just the SDE folders?
4) When we run a multi source execution plan, after the first full load, can we somehow allow Incremental loads only from Container A subject area? Basically, I dont want to load incrementally from source sytem A after the first full load.
4) Do I have to set a DELAY? In my case, my systems are both in the same time zone..so I assume I can leave this DELAY option blank. Is that correct?
Thanks in advance
Edited by: 848613 on May 26, 2011 7:32 AM
Edited by: 848613 on May 26, 2011 12:24 PMHi
you are having 2 sources like Ora11510 and OraR1211 so you will be having 2 DAC containers
You need these below mandatory changes
for your issue
+++++++++++++++++++++++++++++++++
Message: Database errors occurred:
ORA-00001: unique constraint (XXDBD_OBAW.W_ETL_RUN_S_U2) violated while inserting into W_ETL_RUN_S
You need to Inactivate 2 tasks in R12 container.
#1 Load Row into Run Table
#2 Update Row into Run Table
+++++++++++++++++++++++++++++++++
There are other tasks that has to be executed only once
(ie Inactivate the Below in One of the container)
SIL_TimeOfDayDimension
SIL_DayDimension_GenerateSeed
SIL_DayDimension_CleanSeed
SIL_TimeOfDayDimension
SIL_CurrencyTypes
SIL_Stage_GroupAccountNumberDimension_FinStatementItem
SIL_ListOfValuesGeneral_Unspecified
PLP_StatusDimension_Load_StaticValues
SIL_TimeDimension_CalConfig
SIL_GlobalCurrencyGeneral_Update <dont Inactivate this> <check for any issues while running>
Update Parameters <dont Inactivate this> <check for any issues while running>
+++++++++++++++++++++++++++++++++++
Task :SDE_ORA_EmployeeDimension_Addresses
Unique Index Failure on "W_EMP_D_ADR_TMP_U1"
As you are load from 11.5.10 & R12 , for certain data which is common across the systems the ETL index creation Fails.
Customize the Index Creation in DAC with another unique columns (data_source_numID).
++++++++++++++++++++++++++++++++++++
Task :SDE_ORA_GeoCountryDimension
Unique Index Failure on "W_GEO_COUNTRY_DS_P1 " As you are loading from 11.5.10 & R12 , for certain data which is common across the systems the ETL index creation Fails.
Option1) Customize the Index Creation in DAC with another unique columns (data_source_numID)
++++++++++++++++++++++++++++++++++
This changes were mandate
Regards,
Kumar -
Hi,
We are having troubles uploading to Folio Builder. We've tried different computers, different networks, different InD versions (CS6, CC, CC 2014).... we can only get 4-6 articles in on a multiple article upload before it crashes InDesign (no error message). Is anyone else having issues?
Any help greatly appreciated. ThanksI am experiencing the exact same issue. Trying to update or upload articles and it just crashes out. I also have some bizarre flickering box appearing in the middle of my folio builder window!? Yesterday, initially I was getting to upload/update about 5 articles before it would crash out and by the end of the day I couldn't get any.
-
Hi Experts,
We are having issue with the local build of DC in NWDS.
We are having a Track which contains few SCs, now a new SC has been created and further new DCs in the newly created SC. Now when I am trying to build the new DC it is giving me the below error.
No 'default' JDK defined, will use running VM.
Error: com.sap.tc.buildplugin.util.BuildPluginException: No 'javac' found for JDK home path 'C:\Java\SAPJVM6\sapjvm_6\jre'.
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaCompiler(JavaMacroContextProvider.java:276)
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaEnvironment(JavaMacroContextProvider.java:186)
at com.sap.tc.buildplugin.JavaMacroContextProvider.execute(JavaMacroContextProvider.java:40)
at com.sap.tc.buildplugin.PrepareContextBuildStep.prepareTechnologySpecificData(PrepareContextBuildStep.java:193)
at com.sap.tc.buildplugin.PrepareContextBuildStep.setupBuildFileCreatorContext(PrepareContextBuildStep.java:95)
at com.sap.tc.buildplugin.PrepareContextBuildStep.execute(PrepareContextBuildStep.java:56)
at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:99)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:73)
at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:59)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1750)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:6004)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.buildDCsForDevConfig(BuildAction.java:307)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction.access$200(BuildAction.java:58)
at com.sap.ide.eclipse.component.provider.actions.dcproject.BuildAction$1.run(BuildAction.java:212)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Error: Build stopped due to an error: No 'javac' found for JDK home path 'C:\Java\SAPJVM6\sapjvm_6\jre'.
I have checked the build variant for the track in SLD and it is maintained as :
com.sap.jdk.home_path_key = JDK1.5.0_HOME.
I have also maintained the Installed JRE in NWDS as JDk 1.5.
Strange part is now if I create the DCs in the old(already present) SC it is working fine and getting built without any error.
Please help!
Regards,
Pankajwhat's the version of your nwds?
you have specify the jdk path not the jre
put the following in your ini file which is located in the nwds installation folder
-vm
C:/jdk1.6x86/bin/javaw.exe (your jdk path)
the following configuration should also help.
Maybe you are looking for
-
Mac OS X Lion and Lightroom 3 import issue
Hi, I upgraded to Lion and migrated my applications and data through the migration assistant. Now I have a problem with importing. I use to import by converting to dng from cr2 (Canon EOS 350D), using a card reader. Nothing changed in my setup from S
-
Nokia C7-00 Audio connection with in-car 3.5mm jac...
Hi, I wanna play my mp3 songs, so I tried to connect the C7 to my in-car audio system (aux-in) via 3.5mm cable. But, somehow, everytime I connect, there was this voice activation that keep recycles on the phone. How to fix that? Is there anything on
-
What is the best third part converter to use with my IPad2 in order to import my videos from my PC?
I have 70 videos I use in my work and want to import them into my IPad2. What is the best third party converter to use?
-
Only some movies I have placed in iTunes "Movies" are viewable via Apple TV. Why? Also some movies have blue dots in front of their titles and some don't . Why?
-
Photoshop Elements 11 will not read the new Nikon Raw/NEF
Photoshop Elements 11 will not read the new Nikon Raw/NEF (from Nikon D750) files even though codec has been downloaded - what do I do?