LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-10-2017, 07:11 AM   #1
aeifn
LQ Newbie
 
Registered: Apr 2016
Posts: 17

Rep: Reputation: Disabled
LSBC++


Hi everyone!

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

Where can i get it?

Thanks!
 
Old 07-10-2017, 07:23 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
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

Last edited by Darth Vader; 07-10-2017 at 07:37 AM.
 
Old 07-10-2017, 07:46 AM   #3
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 376

Rep: Reputation: Disabled
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
 
1 members found this post helpful.
Old 07-10-2017, 07:57 AM   #4
aeifn
LQ Newbie
 
Registered: Apr 2016
Posts: 17

Original Poster
Rep: Reputation: Disabled
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.
 
Old 07-10-2017, 08:06 AM   #5
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
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.

Last edited by Darth Vader; 07-10-2017 at 08:12 AM.
 
Old 07-10-2017, 08:32 AM   #6
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 732

Rep: Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553
Hello,

Quote:
Originally Posted by aeifn View Post
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 :

Click image for larger version

Name:	epson-printer-utility.jpg
Views:	27
Size:	39.5 KB
ID:	25440
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

Last edited by phenixia2003; 07-10-2017 at 08:33 AM.
 
6 members found this post helpful.
Old 07-10-2017, 10:23 AM   #7
montagdude
Member
 
Registered: Apr 2016
Posts: 575

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
Quote:
Originally Posted by phenixia2003 View Post
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.
 
Old 07-10-2017, 10:33 AM   #8
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
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 View Post
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.

Last edited by Darth Vader; 07-10-2017 at 10:38 AM.
 
Old 07-10-2017, 03:34 PM   #9
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 152

Rep: Reputation: 27
Excuse my ignorance! For what's good this LSBC++?
 
Old 07-10-2017, 03:47 PM   #10
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
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.

Last edited by Darth Vader; 07-10-2017 at 04:52 PM.
 
Old 07-10-2017, 05:33 PM   #11
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,225

Rep: Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304Reputation: 3304
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.
Attached Files
File Type: txt epson-printer-utility.SlackBuild.txt (5.6 KB, 11 views)
 
6 members found this post helpful.
Old 07-10-2017, 07:57 PM   #12
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
< here was nothing useful for Slackware >

Last edited by Darth Vader; 07-11-2017 at 04:55 AM.
 
Old 07-11-2017, 03:32 AM   #13
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,043
Blog Entries: 4

Rep: Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354Reputation: 1354
[deleted] -- I really shouldn't waste my day arguing

Last edited by 55020; 07-11-2017 at 03:56 AM.
 
Old 07-11-2017, 04:09 AM   #14
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,089

Rep: Reputation: 406Reputation: 406Reputation: 406Reputation: 406Reputation: 406
< deleted because it is a response to a question which was deleted >

Last edited by Darth Vader; 07-11-2017 at 04:51 AM.
 
Old 07-17-2017, 09:22 AM   #15
aeifn
LQ Newbie
 
Registered: Apr 2016
Posts: 17

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off




All times are GMT -5. The time now is 06:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration