[SOLVED] LSBC++

aeifn · 07-10-2017, 07:11 AM

Hi everyone!

I need lsbc++ to compile epson-printer-utility on Slackware 14.2.

Where can i get it?

Thanks!

Darth Vader · 07-10-2017, 07:23 AM

IF I recall right, Slackware is NOT a LSB compliant distribution, then if your epson-printer-utility ask for a LSB compliant distro, which Slackware is NOT, I guess that you have either to change your printer or your operating system.

For further details: https://wiki.linuxfoundation.org/en/Book/HowToDevel

chris.willing · 07-10-2017, 07:46 AM

I just had a look at Epsom's web page for this software and it doesn't look any more utilitarian or advanced than what's is available directly from my Epsom WF-2630 by just pointing a browser at the printer's ip address. I had to install a driver (http://www.slackware.com/~alien/slac...pr/pkg64/14.2/) for it to be fully incorporated by the "Print Settings" applet.

chris

aeifn · 07-10-2017, 07:57 AM

Actually, i don`t want to change Slackware because everything else works perfect.

I use Epson L800 with USB connection and really need epson-printer-utility for filling continuous ink system.

Darth Vader · 07-10-2017, 08:06 AM

In the mean time, a small excerpt from LSB developing tutorial, previously noted:

Quote:

makelsbpkg

LSB currently suggests to use RPM format to package the applications.

You see the light?

Again, IF this epson-printer-utility ask for a LSB compliant distribution, I am afraid that you have to chose between using Slackware or this tool.

phenixia2003 · 07-10-2017, 08:32 AM

Hello,

Quote:

Originally Posted by aeifn

Actually, i don`t want to change Slackware because everything else works perfect.

I use Epson L800 with USB connection and really need epson-printer-utility for filling continuous ink system.

Here is something that you can try.

1. Go here, accept the license. If you're on Slackware 32-bit, download epson-printer-utility-1.0.2-1lsb3.2.i486.rpm
, otherwise (ie. Slackware 64-bit), download epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm.

2. Convert the rpm package you downloaded into a tgz Slackware package :

Code:

# if you are on Slackware 32-bit
$ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.i486.rpm

# if you are on Slackware 64-bit
$ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm

3. Install the generated slackware package :

Code:

# if you are on Slackware 32-bit
$ installpkg epson-printer-utility-1.0.2-1lsb3.2.i486.tgz

# if you are on Slackware 64-bit
$ installpkg epson-printer-utility-1.0.2-1lsb3.2.x86_64.tgz

4. Create the symlink below which is required by LSB :

Code:

# if you are on Slackware 32-bit   
$ ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

# if you are on Slackware 64-bit   
# ln -sf /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

For epson-printer-utility to work, you first need to start /usr/lib/epson-backend/ecbd as root :

Code:

$ su -
$ /usr/lib/epson-backend/rc.d/ecbd start

Now, epson-printer-utility can be started :

Code:

$ /opt/epson-printer-utility/bin/epson-printer-utility

Here is a screenshot :

Note that I don't have any epson printer, so I can't go any further. Furthermore, it would be better to write a slackbuild to repackage all of this into a real slackware package.

--
SeB

montagdude · 07-10-2017, 10:23 AM

Quote:

Originally Posted by phenixia2003

Hello,

Here is something that you can try...

--
SeB

But why do all that when you could just tell the user not to use Slackware?

Thanks for the helpful post, as usual.

Darth Vader · 07-10-2017, 10:33 AM

Like the title says, the OP ask for LSBC++, then about compilation from sources of this printer tool.

I responded literally to his literal question; as he wants this LSBC++. Also, I given him a hint about RPM usage by a LSB compliant distribution.

To quote myself:

Quote:

Originally Posted by Darth Vader

Again, IF this epson-printer-utility ask for a LSB compliant distribution, I am afraid that you have to chose between using Slackware or this tool.

The keyword is IF, as is very clear that Slackware is not a LSB compliant distribution.

LuckyCyborg · 07-10-2017, 03:34 PM

Excuse my ignorance! For what's good this LSBC++?

Darth Vader · 07-10-2017, 03:47 PM

Gods know...

BUT, something tell me that on next several years, LSB would become a subject so controversial on this forum, that in comparation, those SystemD candid debates would be remembered like some innocent kids play.

volkerdi · 07-10-2017, 05:33 PM

I thought I'd take a look at this, since generally it's not that hard to force something to compile with the native libraries and include files rather than using the LSB stuff. I've attached my SlackBuild-in-progress.

What I ran into that finally brought the attempt to an end, was that several files had been generated by the moc shipped with qt-4.2.3. This led to many errors like this one:

Code:

c++ -DHAVE_CONFIG_H -DX86_64 -DQT_NO_DEBUG_OUTPUT   -I/usr/lib64/qt/include/QtCore -I/usr/lib64/qt/include/QtCore
 -I/usr/lib64/qt/include/QtGui -I/usr/lib64/qt/include/QtGui -I/usr/lib64/qt/include/QtNetwork -I/../EPUCommon
 -I/.. -I/usr/include -I../EPSCommonLib/ -I../EPSCommonLib/escpr-lib/inc -I../EPSCommonLib/epsmp/linux
 -I../EPSCommonLib/epsmp  -g -w  -O2 -fPIC -fpermissive -MT __EPS_PREFIX__utility-moc_EPUMaintenanceGuideView.o
 -MD -MP -MF .deps/__EPS_PREFIX__utility-moc_EPUMaintenanceGuideView.Tpo -c
 -o __EPS_PREFIX__utility-moc_EPUMaintenanceGuideView.o
 `test -f 'moc_EPUMaintenanceGuideView.cpp' || echo './'`moc_EPUMaintenanceGuideView.cpp
moc_EPUMaintenanceGuideView.cpp:14:2: error: #error "This file was generated using the moc from 4.2.3. It"                                                                           
#error "This file was generated using the moc from 4.2.3. It"                                                                                                                        
^~~~~                                                                                                                                                                             
moc_EPUMaintenanceGuideView.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt."                                                                 
#error "cannot be used with the include files from this version of Qt."                                                                                                              
^~~~~                                                                                                                                                                             
moc_EPUMaintenanceGuideView.cpp:16:2: error: #error "(The moc has changed too much.)"

OK, so normally one would make sure that any old generated files are gone, and then use qmake to generate them again. Trying this, I get:

Code:

# qmake                                                                                                                  WARNING: Failure to 
find: EPUCommonUtility.cpp                                                                                                                                      
WARNING: Failure to find: EPUMonitorStatusView.cpp                                                                                                                                  
WARNING: Failure to find: EPUNozzleCheckResultView.cpp                                                                                                                              
WARNING: Failure to find: EPUHeadCleaningView.cpp                                                                                                                                   
WARNING: Failure to find: EPUCommonUtility.h                                                                                                                                        
WARNING: Failure to find: EPUMonitorStatusView.h                                                                                                                                    
WARNING: Failure to find: EPUNozzleCheckResultView.h                                                                                                                                
WARNING: Failure to find: EPUHeadCleaningView.h                                                                                                                                     
WARNING: Failure to find: ../EPSCommonLib/reply-parser/inc/epson-ijpl-rp-def.h                                                                                                      
WARNING: Failure to find: ../EPSCommonLib/common/inc/epson-escpr-media.h                                                                                                            
WARNING: Failure to find: ../EPSCommonLib/common/inc/epson-ijpl-dbg.h                                                                                                               
WARNING: Failure to find: ../EPSCommonLib/common/inc/epson-ijpl-err.h                                                                                                               
WARNING: Failure to find: ../EPSCommonLib/common/inc/epson-ijpl-status.h                                                                                                            
WARNING: Failure to find: ../EPSCommonLib/common/inc/epson-ijpl-typedefs.h                                                                                                          
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-ijpl-comm-def.h                                                                                                    
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-cbt.h                                                                                                              
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-ijpl-comm-api.h                                                                                                    
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-ijpl-comm-pvt.h                                                                                                    
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-ijpl-comm-utl.h                                                                                                    
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-net-lpr.h                                                                                                          
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-net-snmp.h                                                                                                         
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-net-upnp.h                                                                                                         
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-net-upnp-media.h                                                                                                   
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-protocol.h                                                                                                         
WARNING: Failure to find: ../EPSCommonLib/communicator/inc/epson-usb.h

And... missing source files. Unfortunately this is not an uncommon thing when we see LGPL source code released by a large company such as Epson, and anyone who has worked with (for example) LGPL/GPL sources from router manufacturers will be familiar with this. The sources we get are those released for license compliance, as an afterthought. In this case, I don't think that it was done on purpose, but the sources that were published online are not complete and without the missing files can't be compiled against a newer version of Qt.

At this point it would seem that converting the binary RPM and implementing the ld symlink hack are your best bet.

Darth Vader · 07-10-2017, 07:57 PM

< here was nothing useful for Slackware >

55020 · 07-11-2017, 03:32 AM

[deleted] -- I really shouldn't waste my day arguing

Darth Vader · 07-11-2017, 04:09 AM

< deleted because it is a response to a question which was deleted >

aeifn · 07-17-2017, 09:22 AM

I used ld symlink hack and program starts, but does not work properly... But it is a subject for new thread, i assume...