You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(14) |
Dec
(23) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(10) |
Feb
(1) |
Mar
|
Apr
(4) |
May
(2) |
Jun
|
Jul
(7) |
Aug
|
Sep
(6) |
Oct
(13) |
Nov
(4) |
Dec
(12) |
2003 |
Jan
(12) |
Feb
(12) |
Mar
(22) |
Apr
(22) |
May
(1) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
2004 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2005 |
Jan
|
Feb
|
Mar
(11) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
2006 |
Jan
(3) |
Feb
|
Mar
(3) |
Apr
(1) |
May
(8) |
Jun
(6) |
Jul
(1) |
Aug
(5) |
Sep
(1) |
Oct
(26) |
Nov
(26) |
Dec
(9) |
2007 |
Jan
(5) |
Feb
(5) |
Mar
(26) |
Apr
(13) |
May
(11) |
Jun
(7) |
Jul
(20) |
Aug
(32) |
Sep
(10) |
Oct
(14) |
Nov
(8) |
Dec
(7) |
2008 |
Jan
(5) |
Feb
(11) |
Mar
(34) |
Apr
(21) |
May
(19) |
Jun
(14) |
Jul
(30) |
Aug
(16) |
Sep
(16) |
Oct
(17) |
Nov
(48) |
Dec
(67) |
2009 |
Jan
(64) |
Feb
(19) |
Mar
(18) |
Apr
(40) |
May
(121) |
Jun
(91) |
Jul
(75) |
Aug
(24) |
Sep
(18) |
Oct
(31) |
Nov
(4) |
Dec
(15) |
2010 |
Jan
(11) |
Feb
(4) |
Mar
(43) |
Apr
(54) |
May
(60) |
Jun
(61) |
Jul
(48) |
Aug
(58) |
Sep
(20) |
Oct
(6) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Michael S. <mi...@ea...> - 2003-03-31 15:48:10
|
Mark Hamzy wrote: > > > > > Mike, > > Do you know what is causing this error? > Google searches seem to indicate that it might be because the cups driver > in ghostscript is not installed. But Rafael seems to be using it. > ... Well, without knowing how your current filter is interfaced to CUPS, I can only guess that the ghostscript-cups package (which has the pstoraster script and pstoraster.convs files that CUPS is looking for) is not installed... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com Printing Software for UNIX http://www.easysw.com |
From: Mark H. <ha...@us...> - 2003-03-31 15:36:10
|
Mike, Do you know what is causing this error? Google searches seem to indicate that it might be because the cups driv= er in ghostscript is not installed. But Rafael seems to be using it. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ ----- Forwarded by Mark Hamzy/Austin/IBM on 03/31/2003 09:27 AM ----- = Rafael Avila de Esp=EDndola = <raf...@ic... To: = omn...@li... > cc: = Sent by: Subject: = [Omniprint-user] strange problem with CUPS omn...@li...ur = ceforge.net = = = 03/30/2003 02:03 PM = = = With the latest OMNI from the CVS I am having some troubles with CUPS. When printing a ps file, /etc/cups/error_log will report: StartJob(7, 0x8086ec0) D [30/Mar/2003:12:31:11 -0300] StartJob() id =3D 7, file =3D 0/1 E [30/Mar/2003:12:31:11 -0300] Unable to convert file 0 to printable fo= rmat for job 7! I [30/Mar/2003:12:31:11 -0300] Hint: Do you have ESP Ghostscript instal= led? D [30/Mar/2003:12:31:11 -0300] CancelJob: id =3D 7 I have espgs installed (7.05.6) and I can generate a printer file with gs -sDEVICE=3Domni -sDeviceName=3DXMLOmniDevice -sproperties=3D'XMLMasterFile=3D"Epson LQ-570+.xml"' -sOutputFile=3Dtem= p.lpr temp.ps OmniDeviceTester also works. Thanks for any help. (See attached file: atty1r9f.dat)= |
From: Rafael A. de <raf...@ic...> - 2003-03-30 16:03:26
|
With the latest OMNI from the CVS I am having some troubles with CUPS. When printing a ps file, /etc/cups/error_log will report: StartJob(7, 0x8086ec0) D [30/Mar/2003:12:31:11 -0300] StartJob() id = 7, file = 0/1 E [30/Mar/2003:12:31:11 -0300] Unable to convert file 0 to printable format for job 7! I [30/Mar/2003:12:31:11 -0300] Hint: Do you have ESP Ghostscript installed? D [30/Mar/2003:12:31:11 -0300] CancelJob: id = 7 I have espgs installed (7.05.6) and I can generate a printer file with gs -sDEVICE=omni -sDeviceName=XMLOmniDevice -sproperties='XMLMasterFile="Epson LQ-570+.xml"' -sOutputFile=temp.lpr temp.ps OmniDeviceTester also works. Thanks for any help. |
From: Mark H. <ha...@us...> - 2003-03-25 15:30:50
|
> Fatal error: Creating a new device with "dither=DITHER_STUCKI_DIFFUSION form=FORM_LETTER > media=MEDIA_PLAIN orientation="portrait dither=DITHER_STUCKI_DIFFUSION form=na_letter_8.50x11.00in > tray=TRAY_REAR_CONTINUOUS media=MEDIA_PLAIN resolution=360x360 printmode=PRINT_MODE_1_ANY > bidirectional=true XMLMasterFile="Epson LQ-570+.xml"" printmode=PRINT_MODE_1_ANY > resolution=RESOLUTION_360_X_180 tray=TRAY_REAR_CON) " failed Hey Rafael, I have found and fixed the error. Please get the latest CVS and try it again. Thanks, Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Rafael A. de <raf...@ic...> - 2003-03-20 10:16:36
|
> > Hey Rafael, > > It does handle imedded quotes. However, the following looks strange > ... orientation="portrait ... > > Did you cut and paste that correctly? Yes, I have verified. > > I am still investigating your other note about OMNI_XML_ROOT_PATH. > > Mark > My /etc/cups/ppd/lq570.ppd has the line: *ShortNickName: "libXMLOmniDevice.so%20orientation=portrait%20dither=DITHER_STUCKI_DIFFUSION%20form=na_letter_8.50x11.00in%20tray=TRAY_REAR_CONNUOUS%20media=MEDIA_PLAIN%20resolution=360x360%20printmode=PRINT_MODE_1_ANY%20bidirectional=true%20XMLMasterFile=%22Epson%20LQ-570+.xml%22" When I try to print something with lpr I have the following error: Fatal error: Creating a new device with "dither=DITHER_STUCKI_DIFFUSION form=FORM_LETTER media=MEDIA_PLAIN orientation="portrait dither=DITHER_STUCKI_DIFFUSION form=na_letter_8.50x11.00in tray=TRAY_REAR_CONTINUOUS media=MEDIA_PLAIN resolution=360x360 printmode=PRINT_MODE_1_ANY bidirectional=true XMLMasterFile="Epson LQ-570+.xml"" printmode=PRINT_MODE_1_ANY resolution=RESOLUTION_360_X_180 tray=TRAY_REAR_CON) " failed Finally, the OmniDeviceTester works if I use the above line without the quote after orientation=. Do you know ware this quote came from? It is not in ShortNickName!!! Thanks, Rafael. |
From: Mark H. <ha...@us...> - 2003-03-19 22:23:05
|
I just tested the following and it generated a print file. OmniDeviceTester --drawbox --driver libXMLOmniDevice.so -sproperties='orientation=portrait dither=DITHER_STUCKI_DIFFUSION form=na_letter_8.50x11.00in tray=TRAY_REAR_CONTINUOUS media=MEDIA_PLAIN resolution=360x360 printmode=PRINT_MODE_1_ANY bidirectional=true XMLMasterFile="/opt/Omni/share/Epson LQ-570+.xml"' --cout output24.prn --cerr output24.err Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Mark H. <ha...@us...> - 2003-03-19 21:31:07
|
Hey Rafael, It does handle imedded quotes. However, the following looks strange ... orientation="portrait ... Did you cut and paste that correctly? I am still investigating your other note about OMNI_XML_ROOT_PATH. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Rafael A. de <raf...@ic...> - 2003-03-19 14:22:18
|
The cups device for ghostscript is working. If I create a printer file with: gs -sDEVICE=omni -sDeviceName=XMLOmniDevice -sproperties='XMLMasterFile="Epson LQ-570+.xml"' -sOutputFile=temp.lpr ~/unicamp/iniciacao/mad-0.14.2b/libmad/synth.c.ps It will print without problems. But if try to use CUPS with the generated PPD, I found this error in the log file: D [19/Mar/2003:11:11:41 -0300] [Job 135] Error: XMLMasterFile="..." must be specified in the job properties! E [19/Mar/2003:11:11:41 -0300] [Job 135] Fatal error: Creating a new device with "dither=DITHER_STUCKI_DIFFUSION form=FORM_LETTER media=MEDIA_PLAIN orientation="portrait dither=DITHER_STUCKI_DIFFUSION form=na_letter_8.50x11.00in tray=TRAY_REAR_CONTINUOUS media=MEDIA_PLAIN resolution=360x360 printmode=PRINT_MODE_1_ANY bidirectional=true XMLMasterFile="/home/rafael/cvs1/Omni/debian/tmp/usr/share/Epson LQ-570+.xml"" printmode=PRINT_MODE_1_ANY resolution=RESOLUTION_360_X_180 tray=TRAY_REAR" failed It looks like the problem is with nested quotes around XMLMasterFile. Thanks for any help. |
From: Mark H. <ha...@us...> - 2003-03-18 00:06:21
|
Hrm... It could be a problem with not specifying -sOutputFile=output24.prn I will have to investigate it further. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Rafael A. de <raf...@ic...> - 2003-03-17 17:54:05
|
I am having some trouble with the XMLOmniDevice. When I execute: gs -sDEVICE=omni -sDeviceName=XMLOmniDevice -sproperties='XMLMasterFile="Epson LQ-570+.xml"' teste.ps The following is displayed: ESP Ghostscript 7.05 (2003-02-05) Copyright (C) 2002 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Loading NimbusMonL-Regu font from /var/lib/defoma/gs.d/dirs/fonts/n022003l.pfb... 2039724 662361 1642520 354036 0 done. Loading NimbusSanL-Bold font from /var/lib/defoma/gs.d/dirs/fonts/n019004l.pfb... 2120108 719613 1702808 396573 0 done. Loading NimbusSanL-Regu font from /var/lib/defoma/gs.d/dirs/fonts/n019003l.pfb... 2160300 768094 1702808 400039 0 done. Loading NimbusRomNo9L-ReguItal font from /var/lib/defoma/gs.d/dirs/fonts/n021023l.pfb... 2240684 832359 1722904 406707 0 done. Loading NimbusMonL-Bold font from /var/lib/defoma/gs.d/dirs/fonts/n022004l.pfb... 2300972 861567 1722904 380151 0 done. Loading NimbusMonL-ReguObli font from /var/lib/defoma/gs.d/dirs/fonts/n022023l.pfb... 2361260 922121 1722904 383757 0 done. Loading NimbusMonL-BoldObli font from /var/lib/defoma/gs.d/dirs/fonts/n022024l.pfb... 2441644 992749 1722904 387089 0 done. Unrecoverable error: typecheck in aload Operand stack: --nostringval-- Unexpected interpreter error -20. Error object: (f80)op(560:aload)0x80bd920 Operand stack at 0x861ed28: 0x861338c: 0x0e null --F------ 0x085f 0xbfffed40 Execution stack at 0x861ecec: 0x8614cf4: 0x0f oper --F---e-- 0x0000 0x080b2940 = %interp_exit 0x8614cfc: 0x0d name --S---e-- 0x03a6 0x08602d0c = .runexec2 0x8614d04: 0x03 file --G-rx--- 0x0001 0x0871c934 0x8614d0c: 0x05 mpry --G-rxe-- 0x0006 0x086535be 0x8614d14: 0x0e null --F---e-- 0x0003 0x080bf890 0x8614d1c: 0x0e null --F------ 0x085f 0xbfffed40 0x8614d24: 0x0b int --F------ 0x0000 0x00000002 = 2 0x8614d2c: 0x0f oper --F---e-- 0x0000 0x080bedf0 = %stopped_push 0x8614d34: 0x03 file --G-rxe-- 0x0001 0x0871c934 0x8614d3c: 0x05 mpry --G-rxe-- 0x0002 0x08653d78 0x8614d44: 0x06 spry --G-rxe-- 0x0002 0x08653d3e 0x8614d4c: 0x04 arry --L-rxe-- 0x0004 0x08739b94 0x8614d54: 0x04 arry --L-rxe-- 0x000a 0x08739ae8 0x8614d5c: 0x04 arry --L-rxe-- 0x0004 0x08739924 0x8614d64: 0x04 arry --L-rxe-- 0x0003 0x08739830 0x8614d6c: 0x05 mpry --G-rxe-- 0x0039 0x0865413a Dictionary stack at 0x861ec94: 0x861e994: 0x02 dict --Gwrx--- 0x0000 0x086054e4 0x861e99c: 0x02 dict --Gwrx--- 0x0000 0x08667c6c 0x861e9a4: 0x02 dict --Lwrx--- 0x0000 0x0860ef3c 0x861e9ac: 0x02 dict --Gwrx--- 0x16c4 0x086054e4 0x861e9b4: 0x02 dict --Lwrx--- 0x0000 0x0860f330 0x861e9bc: 0x02 dict --Lwrx--- 0x16c4 0x08739bc8 I am not sure if the problem is with Omni or with espgs. I will compile the cvs version of espgs. If anything different happens I report. |
From: Mark H. <ha...@us...> - 2003-03-12 23:24:29
|
Hi Torsten, The omni driver uses different ghostscript parameters. Look at the docs/Usage file for an explination of the parameters http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/omniprint/Omni/docs/Usage?rev=1.6&content-type=text/vnd.viewcvs-markup Hope this helps, Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Torsten <tor...@ep...> - 2003-03-12 17:00:24
|
Hello, I have a problem when using omni. Here is a description of my situation: There is a server runnig SuSE 8.1 (Kernel 2.4.19). This machine already h= osts=20 5 printers with cups (Laserprinters with and without postscript capabilit= ies=20 and one OfficeJet). Everything is working fine. Now I try to add an EPSON DFX-8000 printer. I installed the RPM version o= f=20 OMNI (Omni-0.7.3-1.i386.rpm) and the package OmniEpson-cups-0.7.3-1.i386.= rpm. I installed one more printer using the following ppd file:=20 /usr/share/cups/model/foomatic/Epson/Epson-Epson_DFX_8000-omni-cups.ppd.g= z Now, I have got a funny behaviour:=20 * When an ESC/P File is printed (via Samba to CUPS) the printer works. * When a postscript file is printed (directly) via CUPS the job stays for= a=20 few seconds in the queue and is then marked as completed. The printer, of= =20 course, didn't do anything. I use ESP Ghostscript 7.05.3. 'omni' is listed when I use 'gs -h'. But when I try to issue a command like: "gs -sDEVICE=3Domni -sDeviceManufacturer=3D"Epson" -sDeviceModel=3D"Epson= DFX-8000"=20 -dNOPAUSE -dSAFER -sOutputFile=3D"test.gs" test.ps -c quit" I get the following response: ESP Ghostscript 7.05 (2002-06-28) Copyright (C) 2002 artofcode LLC, Benicia, CA. All rights reserved. This software comes with NO WARRANTY: see the file COPYING for details. <<<<<<<<<<<<<<<<<<<<<< ERROR >>>>>>>>>>>>>>>>>>>>>>> Error: -sDeviceName=3DXXX was not defined srv0001:/home/tloehr # Maybe there is a link here... Can somebody help me ? Bye, Torsten... |
From: Mark H. <ha...@us...> - 2003-03-11 21:46:33
|
Hi Rafael, > I have found one more problem. The generated PPD have the ShortNickName > hard-coded. For example, the Epson-Epson_LQ_570_-omni-cups.ppd.gz has > *ShortNickName: "libXMLOmniDevice.so%20XMLMasterFile=%22/home/rafael/cvs/Omni/Epson/Epson%20LQ-570+.xml%22" I am currently working on that code after your note. A little architecture explination: The XMLMasterFile="..." will tell the XML device which device to emulate. A fully qualified file like that will work if it exists and fail otherwise. A non-qualified file will work if the standard omni directory structure exists (/opt/Omni/share). I had intended OMNI_XML_ROOT_PATH to handle the special scenario of using a build tree as source but generating an install tree as the target. > if I move this file, cups will fail with I assume that you have installed the driver somewhere and then removed/renamed your build directory to test it? What path do you use as a share directory? I have updated CVS with my current source. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Mark H. <ha...@us...> - 2003-03-10 21:38:12
|
Hey Rafael, It looks like I've regressed the device options. I'm working on it now... Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Rafael A. de <raf...@ic...> - 2003-03-09 01:41:35
|
On Sat, 8 Mar 2003 09:07:37 -0300 Rafael Avila de Esp=EDndola <raf...@ic...> wrote: > I solved the problem by updating the ppd that cups was using. Now the >on= ly problem I have is that the lines "@EJL 1284.4" and "@EJL" are >printed a= t the beginning of the page. This appears to come from the >cmdUSBInit tag = in the "Epson\ Generic\ ESC2P\ Commands.xml" file.=20 I have found one more problem. The generated PPD have the ShortNickName hard-coded. For example, the Epson-Epson_LQ_570_-omni-cups.ppd.gz has=20 *ShortNickName: "libXMLOmniDevice.so%20XMLMasterFile=3D%22/home/rafael/cvs/= Omni/Epson/Epson%20LQ-570+.xml%22" if I move this file, cups will fail with [Job 97] Fatal error: Creating a new device with "XMLMasterFile=3D"/home/ra= fael/cvs/Omni/Epson/Epson LQ-570+.xml" dither=3DDITHER_STUCKI_DIFFUSION for= m=3DFORM_LETTER media=3DMEDIA_PLAIN printmode=3DPRINT_MODE_1_ANY resolution= =3DRESOLUTION_360_X_180 tray=3DTRAY_REAR_CONTIN=F9 " failed |
From: Rafael A. de <raf...@ic...> - 2003-03-08 12:11:13
|
I solved the problem by updating the ppd that cups was using. Now the only problem I have is that the lines "@EJL 1284.4" and "@EJL" are printed at the beginning of the page. This appears to come from the cmdUSBInit tag in the "Epson\ Generic\ ESC2P\ Commands.xml" file. |
From: Rafael A. de <raf...@ic...> - 2003-03-08 03:57:16
|
I have updated omni from the CVS and now a get the following error: Omni::openLibrary: g_module_error returns /usr/lib/libEpson_LQ_570_.so: undefined symbol: _ZN11PrintDevice15hasDeviceOptionEPc Omni::openLibrary: pszLibName = libEpson_LQ_570_.so Someone can help? Thanks. |
From: <tdl...@ya...> - 2003-03-07 11:15:08
|
Thank you two a lot. Now it is working. I had not tested the CUPS and foomatic, but the espgs is working and I could print a PS file. Thiago A. M. Delatorre (tdlt) _______________________________________________________________________ Busca Yahoo! O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra. http://br.busca.yahoo.com/ |
From: John T C. <jo...@ne...> - 2003-03-06 18:33:27
|
Thiago A. M. Delatorre wrote: >Is there someone whose has the gs+omni working for >Epson LQ 1070+ printer ? > >My command line is: > >"gs -sDEVICE=omni >-sDeviceManufacturer="HEWLETT-PACKARD" >-sDeviceModel="EPSON LQ1070+" -dNOPAUSE -dSAFER >-sOutputFile="/dev/lp0" file.ps -c quit" > >I've tried with the gs-esp-7.05 in debian package and >with gs-7.04 + omni-0.7.3 (compiled following their >own instructions) but it had no worked (gs says >"Error: Could not load libomni.so") > >Does someone know what is happening? > >Thank's a lot. This is my first message to the list. > >Thiago A. M. Delatorre (tdlt) > > >_______________________________________________________________________ >Busca Yahoo! >O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra. >http://br.busca.yahoo.com/ > > >------------------------------------------------------- >This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger >for complex code. Debugging C/C++ programs can leave you feeling lost and >disoriented. TotalView can help you find your way. Available on major UNIX >and Linux platforms. Try it free. www.etnus.com >_______________________________________________ >Omniprint-user mailing list >Omn...@li... >https://lists.sourceforge.net/lists/listinfo/omniprint-user > > > As Rafael says: Use the espgs from the CVS. I have the little brother of your printer (LQ-570+) I had the same error: "Error: Could not load libomni.so" Using the espgs from the CVS fixed it. I have a Panasonic KX-P2124 which can emulate a an LQ-860. If you check the mailing lists archive there are several messages relating to the "load libomni.so" error. JohnC |
From: Rafael A. de <raf...@ic...> - 2003-03-06 10:00:26
|
Use the espgs from the CVS. I have the little brother of your printer (LQ-570+). |
From: <tdl...@ya...> - 2003-03-06 01:10:12
|
Is there someone whose has the gs+omni working for Epson LQ 1070+ printer ? My command line is: "gs -sDEVICE=omni -sDeviceManufacturer="HEWLETT-PACKARD" -sDeviceModel="EPSON LQ1070+" -dNOPAUSE -dSAFER -sOutputFile="/dev/lp0" file.ps -c quit" I've tried with the gs-esp-7.05 in debian package and with gs-7.04 + omni-0.7.3 (compiled following their own instructions) but it had no worked (gs says "Error: Could not load libomni.so") Does someone know what is happening? Thank's a lot. This is my first message to the list. Thiago A. M. Delatorre (tdlt) _______________________________________________________________________ Busca Yahoo! O serviço de busca mais completo da Internet. O que você pensar o Yahoo! encontra. http://br.busca.yahoo.com/ |
From: Mark H. <ha...@us...> - 2003-02-10 22:41:29
|
Hi Frank, Omni requires autoconf version 2.52 or higher. We use configure.ac instead of configure.in. Hope this helps, Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Mark H. <ha...@us...> - 2003-02-10 22:37:46
|
Thanks Rafael, > Fine. I have add some commands to debian/rules so that it manages the switch. I have switched Omni over from data to share. > By the way, could you make debian/rules executable? Done. What is your sorceforge id? Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ |
From: Frank P. <fp...@ss...> - 2003-02-10 22:23:54
|
Hey everybody. I've recently tried to install the latest (0.7.1 'n 0.7.2) Omni-packages onto my Mandrake 8.2 running machine, but during the execution of the setupOmni I encountered following Error: --- [root@yoda Omni]# ./setupOmni CONFIGURE_ARGS= MAKE_ARGS= Running aclocal... Running autoheader... /usr/bin/m4: configure.in: No such file or directory Running automake... Running autoreconf... ls: ./acinclude.m4: No such file or directory automake: Makefile.am: required file `./INSTALL' not found Running configure ... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes ... Building with CUPS: Yes checking for gtkmm-config... no configure: WARNING: Please install gtkmm development package the JobDialog. checking for gtk-config... /usr/bin/gtk-config checking for sigc-config... no configure: WARNING: Please install sigc development package to build the JobDialog. checking supported compiler flags... -Wall -Wstrict-prototypes -Wmissing-declarations -Wmissing-prototypes -fno-builtin -fno-common ...done. ... config.status: creating test/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands Running make ... cd . && /bin/sh /home/yoda/Files/Omni/missing --run autoconf autoconf: configure.in: No such file or directory make: *** [configure] Error 1 --- (If somebody is interested in the entire output, I can certainly post it) Any help or suggestions are greatly appreciated. - Frank Prager |
From: Rafael A. de <raf...@ic...> - 2003-02-08 17:18:23
|
On Wed, 5 Feb 2003 11:16:07 -0600 > > Thanks Rafael, > > I have added the debian/* to CVS. If you want I can add you as a developer > to sourceforge so that you can checkin an changes for debian support. I have fixed some problems with the debian support. debian/rules now calls setupOmni (instead of configure) and correctly sets CUPSEXEROOT and CUPSDATAROOT. I will contact the debian-devel mailing-list about adding omni to the official debian distribution so the write access to debian/* might be useful. > I am still considering the /opt/Omni/data/ to /opt/Omni/share/ switch... Fine. I have add some commands to debian/rules so that it manages the switch. By the way, could you make debian/rules executable? > > Mark > > Take a look at the Linux Omni Printer Driver Framework at > http://www.ibm.com/linux/ltc/projects/omni/ > Rafael. |