Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Re: [Omniprint-user] espgs-7.05.5(omni-0.7.1): could not load libomni.so

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Jason Flatt <jasonflatt AT wizard.com>
  • To: John T Copeland <johnc AT neto.com>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Re: [Omniprint-user] espgs-7.05.5(omni-0.7.1): could not load libomni.so
  • Date: Tue, 24 Dec 2002 23:29:22 +0000

FYI, I'm removing the omni people from this replay as I suspect that they
will
be uninterested in SMGL stuff.


On Tuesday 24 December 2002 05:23 pm, John T Copeland wrote:
>
> Jason, Mark,
> A follow up and final on this. I finally got my printer to work
> properly. I did the following to get there.
> 1) Downloaded omni-0.7.2. Configured, compiled, installed AOK.
> libomni.so showed up in /opt/omni/lib. Mark, I had a small proplem
> here. I deleted all the printers in devices.mak except Panasonic, and
> the compile failed with some error related to Hewlett Packard. I add HP
> back to devices.mak and compile went OK.
> 2) Downloaded espgs-7.05.5 from the CVS, did a makesrcdist, replaced my
> version in /var/spool/sorcery. An install(cast -r -c) of espgs then
> configured, compiled, and installed OK.
> 3) Reviewed all my cupsomatic and PPD stuff
> 4) Printed a simple text file OK
> 5) Tried the test print in CUPS, and it failed looking for a particular
> font.
> 6) Investigation showed the standard ghostscript fonts had disappeard.
> Probably because espgs install had done away with them.
> 7) Installed(cast -r -c) ghostscript-fonts-std, and the CUPS test ,
> print a test page, worked.
>
> Jason, it appears the espgs spell needs to be upgraded for the omniprint
> driver. You copy?
> JohnC


In attempting to provide solution(s) for you (and others who would be
interested in persuing a similar path), I have come up with some questions
for you:

1) Did you build Omni from the source tar, or from CVS?
2) Did you use GCC 2 or 3?
3) Did you answer "y" to including Omni in ESPGS, or not?
4) Did you build Omni as an integral part of ESPGS, ie: copied the Omni
source into the appropriate place within the espgs source, or as a separate
package?
5) Are you suggesting that there may need to be some sort of trigger which
causes ghostscript-fonts-std to be recast after espgs, or was that just a
fluke?

My plan is to create a separate spell for Omni and a dev/cvs spell for espgs.

If Omni does not work correctly (or at all) with the way it is currently
implemented (as an integral part of espgs), then I will remove it.


--
Jason Flatt
E-mail (remove the spaces): jasonflatt @ wizard . com
Voice: +1 702 870 6622
Fax: +1 702 870 3883
Snail Mail: PO Box 44265, Las Vegas, NV 89116-2265, USA





Archive powered by MHonArc 2.6.24.

Top of Page