Re: compiling C source for HP850C ghostscript driver from OS/2 or DOS on Linux

1997-04-19 Thread Bruce Perens
I think this user has to run "fromdos" (in the sysutils package) on the
files, to replace the MS-DOS CR-NL line endings with just plain CR.

Thanks

Bruce
-- 
Bruce Perens K6BP   [EMAIL PROTECTED]   510-215-3502
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6  1F 89 6A 76 95 24 87 B3 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: compiling C source for HP850C ghostscript driver from OS/2 or DOS on Linux

1997-04-19 Thread Geoff R Deasey
> >... what I tried to do was delete all "^M" chars and
> >all backslashes at the ends of lines.  Even this wasn't enough.

are you using a make file ?

I had a problem that with the ^M in the make file made it 
not work properly.  What was the exact error message ?


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: compiling C source for HP850C ghostscript driver from OS/2 or DOS on Linux

1997-04-18 Thread Chris Hanson
   Date: Fri, 18 Apr 97 20:24 GST
   From: Alan Eugene Davis <[EMAIL PROTECTED]>
   To: debian-user@lists.debian.org

   MOre than once I have tried compiling C source on linux, using gcc,
   that generated alot of error messages, including many concerning
   backslashes at the ends of lines.  An example is an existing
   ghostscript driver for the HP850C Deskjet into ghostscript.  The main
   problem I had was with this source code, that I suspected was
   developed on MSDOG or OS/2.  It had a lot of "^M" like characters in
   it.  

   Can anyone provide the slightest clue?   What's special about MSDOG
   source code files that would result in many error messages?  At least
   a clue, otherwise, what I tried to do was delete all "^M" chars and
   all backslashes at the ends of lines.  Even this wasn't enough.

In C code, a backslash at the end of a line is a special hack.  What
it usually means is "replace the backslash, newline, and immediately
following whitespace with a single space".  When the C parser sees a
^M following the backslash, it gets upset.

What you should do is replace all instances of ^M^J with ^J (i.e.
delete all ^M characters appearing at the end of a line).  DO NOT
delete the backslashes, because they are important.


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: compiling C source for HP850C ghostscript driver from OS/2 or DOS on Linux

1997-04-18 Thread Dima
In message <[EMAIL PROTECTED]> you wrote:
>
>MOre than once I have tried compiling C source on linux, using gcc,
>that generated alot of error messages, including many concerning
>backslashes at the ends of lines. 
...
>Can anyone provide the slightest clue?   What's special about MSDOG
>source code files that would result in many error messages?  

I think it's not MS-DOG source code, it's MS-DOG C compilers that
usually are to blame.

>... what I tried to do was delete all "^M" chars and
>all backslashes at the ends of lines.  Even this wasn't enough.

^M's shouldn't matter; use something like dos2unix if you want to get
rid of them.  I don't quite understand the bit about backslashes:
do you mean strings like
" blah blah blah \
more blah"; 
or something else?

Dimitri
.sig  sigh


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


compiling C source for HP850C ghostscript driver from OS/2 or DOS on Linux

1997-04-18 Thread Alan Eugene Davis

MOre than once I have tried compiling C source on linux, using gcc,
that generated alot of error messages, including many concerning
backslashes at the ends of lines.  An example is an existing
ghostscript driver for the HP850C Deskjet into ghostscript.  The main
problem I had was with this source code, that I suspected was
developed on MSDOG or OS/2.  It had a lot of "^M" like characters in
it.  

Can anyone provide the slightest clue?   What's special about MSDOG
source code files that would result in many error messages?  At least
a clue, otherwise, what I tried to do was delete all "^M" chars and
all backslashes at the ends of lines.  Even this wasn't enough.

Thanks for any clude.  Any.

Alan Davis

-- 
 Alan Eugene Davis  Marianas High School  15o 8.8'N   GMT+10
 [EMAIL PROTECTED]  AAA 196 Box 10,001145o 42.5'E 
Saipan, MP  96950
Northern Mariana Islands   

  
"Woe be unto those who lay house to house and field unto field that
the Earth be laid to waste."
   -- Isaah.








--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .