| View previous topic :: View next topic |
| Author |
Message |
cz0
Apprentice
Joined: 13 Jun 2005
Posts: 280
Location: /earth/russia/moscow
|
 Posted: Tue Jan 23, 2018 8:49 pm Post subject: Files matching a file type that is not allowed?? |
 |
|
Hi.
After portage update I'm not able to install net-print/cndrvcups-common-2.60-r1 (from an overlay) that was successfully compiled and installed many-many times before. Now it looks like this:
| Code: |
Linking library libcanonc3pl.so.1.0.0 ...
>>> Source compiled.
>>> Test phase [not enabled]: net-print/cndrvcups-common-2.60-r1
>>> Install cndrvcups-common-2.60-r1 into /var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image/ category net-print
make[1]: Entering directory '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/work/Linux_CAPT_PrinterDriver_V260_uk_EN/Src/cndrvcups-common-2.60-1/buftool'
/bin/mkdir -p '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image//usr/local/lib'
/usr/lib/portage/python3.5/ebuild-helpers/xattr/install -c -m 644 libbuftool.a '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image//usr/local/lib'
( cd '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image//usr/local/lib' && ranlib libbuftool.a )
/bin/mkdir -p '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image//usr/local/include'
/usr/lib/portage/python3.5/ebuild-helpers/xattr/install -c -m 644 buftool.h buflist.h '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image//usr/local/include'
make[1]: Leaving directory '/var/tmp/portage/net-print/cndrvcups-common-2.60-r1/work/Linux_CAPT_PrinterDriver_V260_uk_EN/Src/cndrvcups-common-2.60-1/buftool'
>>> Completed installing cndrvcups-common-2.60-r1 into /var/tmp/portage/net-print/cndrvcups-common-2.60-r1/image/
* Final size of build directory: 76892 KiB (75.0 MiB)
* Final size of installed tree: 3996 KiB ( 3.9 MiB)
* QA Notice: The following shared libraries lack a SONAME
* /usr/lib32/libcaiousb.so.1.0.0
Files matching a file type that is not allowed:
usr/lib32/libcanonc3pl.so.1.0.0
* ERROR: net-print/cndrvcups-common-2.60-r1::x-portage failed:
* multilib-strict check failed!
*
* Call stack:
* misc-functions.sh, line 666: Called install_qa_check
* misc-functions.sh, line 217: Called source 'install_symlink_html_docs'
* 80multilib-strict, line 46: Called multilib_strict_check
* 80multilib-strict, line 42: Called die
* The specific snippet of code:
* [[ ${abort} == yes ]] && die "multilib-strict check failed!"
|
In the ebuild the line that causes this seems to be the first one that starts with dolib.so:
| Code: |
dolib.so c3plmod_ipc/libcanonc3pl.so.1.0.0
dosym libcanonc3pl.so.1.0.0 /usr/$(get_libdir)/libcanonc3pl.so.1.0
dosym libcanonc3pl.so.1.0.0 /usr/$(get_libdir)/libcanonc3pl.so.1
dosym libcanonc3pl.so.1.0.0 /usr/$(get_libdir)/libcanonc3pl.so
|
This is post-install section.
Cause Canon CAPT drivers seem to be deprecated, I was not able to find a fresh version or a newer ebuild, so fixing this is the only way to get my old and trusty LBP-810 up and running again.
Any ideas? |
|
| Back to top |
|
 |
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Tue Jan 23, 2018 9:25 pm Post subject: |
|
|
You could try
| Code: | | LDFLAGS="-Wl,-Ol -Wl,--as-needed -Wl,-soname,libcanonc3pl.so.1" emerge -1 net-print/cndrvcups-common |
And if it work, build an env that force it for that package. |
|
| Back to top |
|
|
cz0
Apprentice
Joined: 13 Jun 2005
Posts: 280
Location: /earth/russia/moscow
|
| Posted: Wed Jan 24, 2018 6:01 am Post subject: |
|
|
| Nop.. Same result. |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9522
Location: beyond the rim
|
|
| Back to top |
|
|
cz0
Apprentice
Joined: 13 Jun 2005
Posts: 280
Location: /earth/russia/moscow
|
| Posted: Sat Feb 10, 2018 9:51 pm Post subject: |
|
|
It seems to. According to description on Canon page, this are the imageRUNNER and iSENSYS series drivers, non of CAPT devices are listed in support list.
| Genone wrote: | | Random guess: the offending library is actually a 64bit binary, and obviously lib32/ should only contain 32bit binaries. |
Please explain. I have this drivers successfully compiling and installing for years before last portage update. |
|
| Back to top |
|
|
|
Portage & Programming
