From: Mark H. <ha...@us...> - 2002-12-12 22:44:16
|
Hi John, > I am getting this error in my Linux distribution, Source Mage, a source > based distro. I noted your message in the list about this being an > error you fixed in espgs and stored the fix at the omni download page, > the file being: ghostscript-7.05-15omni.i386.rpm. This fixed the error > for one of the users. I have found a couple of scenarios that can cause that error. The first is the lack of libstdc++ compiled into ghostscript and the second is omni changed function naming (removing C++ name mangling). I am currently working on some backwards compatibility for that scenario. Omni's CVS has that checked in. > My problem is my system is source based(not binary), so the library > would need to be compiled along with espgs. We currently get the source > from www.easysw.com's ftp site. My questions: > 1) Does the error in espgs cause the library to not be compiled and > installed? Or is there a special option in configure to compile the > library? I get the following line in my configuration output: > "checking if Omni support can be compiled in... yes" Actually, espgs and omni are two separate projects. In the latest version of espgs, it only checks for glib support for that message. Earlier versions checked for a link to omni source as well. So, one would first build espgs and then build omni. > 2) If so, is there a source patch? > 3) If so, can we get the patch? No. I would recommend that you check out the latest CVS of both projects. > 4) Will we need(have) to wait for espgs-7.xx.x(we use 7.05.5)? Only the current epsgs CVS will work for both 7.3 and 8.0 RedHat systems. > 5) Finally, am I off base here? An if so would you please give me > directions? > > A command, "gs --help" shows an omni device. Hope that helps. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: John T C. <jo...@ne...> - 2002-12-14 16:03:08
|
Mark Hamzy wrote: >Hi John, > > > >>I am getting this error in my Linux distribution, Source Mage, a source >>based distro. I noted your message in the list about this being an >>error you fixed in espgs and stored the fix at the omni download page, >>the file being: ghostscript-7.05-15omni.i386.rpm. This fixed the error >>for one of the users. >> >> > >I have found a couple of scenarios that can cause that error. The first >is the lack of libstdc++ compiled into ghostscript and the second is >omni changed function naming (removing C++ name mangling). > >I am currently working on some backwards compatibility for that scenario. >Omni's CVS has that checked in. > > > >>My problem is my system is source based(not binary), so the library >>would need to be compiled along with espgs. We currently get the source >>from www.easysw.com's ftp site. My questions: >>1) Does the error in espgs cause the library to not be compiled and >>installed? Or is there a special option in configure to compile the >>library? I get the following line in my configuration output: >> "checking if Omni support can be compiled in... yes" >> >> > >Actually, espgs and omni are two separate projects. In the latest version >of espgs, it only checks for glib support for that message. Earlier >versions checked for a link to omni source as well. > >So, one would first build espgs and then build omni. > > > >>2) If so, is there a source patch? >>3) If so, can we get the patch? >> >> > >No. I would recommend that you check out the latest CVS of both projects. > > > >>4) Will we need(have) to wait for espgs-7.xx.x(we use 7.05.5)? >> >> > >Only the current epsgs CVS will work for both 7.3 and 8.0 RedHat systems. > > > >>5) Finally, am I off base here? An if so would you please give me >>directions? >> >>A command, "gs --help" shows an omni device. >> >> > >Hope that helps. > >Mark > >Take a look at the Linux Omni Printer Driver Framework at >http://www.ibm.com/linux/ltc/projects/omni/ > > > > > Thanks Mark. The above helps some, but I am not exactly sure how to proceed yet. 1)Does the build of the Omni Project build the libomni.so library(a shared library I presume)? The library is not currently resident on my system, so I got to build it somehow. The library missing could be my problem. I created dummy libomni.so's in /lib and /usr/lib to see if I would get a different error, but I get the same error, indicating(maybe) that I need the fixes which are in CVS and the tarball on the omni download site? 2)The Omni function compiled into espgs is just an interface to the libomni.so library? 3)Our system, in general does not use the CVS's for standard installation, but rather source(not binary or rpm's)tarballs. I don't know how to use a CVS in any case(guess I could learn tho). 4)You say the latest CVS for both projects has the latest fix you alluded to, so I presume the fixes will show up in espgs 7.05.6 or later? Can you help any here Jason(Jason is our printer guru in SourceMage)? Thanks, JohnC |
From: Jason F. <jas...@wi...> - 2002-12-14 17:27:15
|
On Saturday 14 December 2002 04:14 pm, John T Copeland wrote: > > [ S N I P ] > > Can you help any here Jason(Jason is our printer guru in SourceMage)? > > Thanks, > JohnC Hi, John. I have been ill the last week, and work has piled up. I will look into getting around this problem, but it may be a couple of days before I can get to it. -- Jason Flatt Section maintainer for printer E-mail (remove the spaces): jasonflatt @ wizard . com E-mail (remove the spaces): jflatt @ sourcemage . org IRC: Oadae |
From: John T C. <jo...@ne...> - 2002-12-15 16:24:41
|
Jason Flatt wrote: >On Saturday 14 December 2002 04:14 pm, John T Copeland wrote: > > >>[ S N I P ] >> >>Can you help any here Jason(Jason is our printer guru in SourceMage)? >> >>Thanks, >>JohnC >> >> > > >Hi, John. > >I have been ill the last week, and work has piled up. I will look into >getting around this problem, but it may be a couple of days before I can get >to it. > > > > Hi Jason, Yes I remember you saying something about not feeling well in a previous post. No worries. I have been fooling with this thing off and on for about a week with no success. The espgs downloads the Omni tarball as you well know, but does not install it. I tried to install Omni manually but got some obscure configure? errors. I will keep hacking on it and let you know how it is going. If those fixes Mark Hamzy alluded to are only in the CVS, and if they affect espgs 7.0.5 are we screwed until another release? Meanwhile, GET WELL. JohnC |
From: John T C. <jo...@ne...> - 2002-12-16 21:30:41
|
Jason Flatt wrote: >On Saturday 14 December 2002 04:14 pm, John T Copeland wrote: > > >>[ S N I P ] >> >>Can you help any here Jason(Jason is our printer guru in SourceMage)? >> >>Thanks, >>JohnC >> >> > > >Hi, John. > >I have been ill the last week, and work has piled up. I will look into >getting around this problem, but it may be a couple of days before I can get >to it. > > > > Mark, Jason, As I indicated before I got configure errors trying to compile Omni-0.7.1. I noticed today that there was a new version Omni-0.7.2 available. I downloaded this manually and did a compile/make install/make installLocal, no problems. The libomni.so file was installed into /opt/Omni/lib. When trying to print I still get the error. I may not have my cupsomatic and PATH's set up right. I added /opt/Omni/bin to my PATH. In the /usr/lib/cups/filter/cupsomatic file, I did: my $execpath = "/usr/bin:/bin:/opt/Omni/bin"; Mark, how does the Omni interface know where to look for libomni.so. All the libomni's are installed in /opt/Omni/lib so I tried copying them to /lib but still get the error. Jason, I guess from what Mark told us, the espgs we are installing may have the error in it. Mark, you believe this is a correct assessment based on the above? Or am I missing something. JohnC |
From: John T C. <jo...@ne...> - 2002-12-24 17:12:09
|
Jason Flatt wrote: >On Saturday 14 December 2002 04:14 pm, John T Copeland wrote: > > >>[ S N I P ] >> >>Can you help any here Jason(Jason is our printer guru in SourceMage)? >> >>Thanks, >>JohnC >> >> > > >Hi, John. > >I have been ill the last week, and work has piled up. I will look into >getting around this problem, but it may be a couple of days before I can get >to it. > > > > 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 |