> From [EMAIL PROTECTED] Mon Feb 18 14:03:36 2002
> Date: Mon, 18 Feb 2002 22:10:12 +0100
> From: Hans Peter Verne <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: LPRng 3.8.6 compile problems
>
> Hans Peter Verne wrote:
> > 
> > Hi Patrick,
> > 
> > I think you once said this was the appropriate place to post bug reports.
> > LPRng 3.8.6 has some compile issues I think you should know about.
>
> So does ifhp 3.5.4, or at least a minor bug.
>
> On the alpha, cc insists that (the line of the beast):
>
> cc: Error: ../../src/perlobj.c, line 666: In this statement, "p->info.array.value" 
>and "len" cannot be added. (noadd)
                                       ^^^  ARGH... the mark of the beastly code 
segment!
                                            Bring on the Bell, Book, and Candle!

                                       
>                         memmove(p->info.array.value+len, p->info.array.value, olen+1 
>);
> --------------------------------^
>
> As far as I can tell, p->info.array.value is a void*, so adding an int to
> it is not allowed.  I suggest you explicitly cast it to (char *), like in the
> previous line, *((char *)(p->info.array.value)+olen) = 0;
>
> This is also the case in lines 615, 713, 813, and 837.
>
>
> Regards,
> --
> Hans Peter       (Unix/printing sysadm, University of Oslo).

I wonder why GCC did not catch this?

Version ifhp-3.5.5 -
  Lexmark 4039 should be:
    ps_sync=
      serverdict begin 0 exitserver
      statusdict begin true setenginesync end
    ps_async=
      serverdict begin 0 exitserver
      statusdict begin false setenginesync end
  (Reported by: Johan Bengtsson <[EMAIL PROTECTED]>)
 
  On the alpha, cc insists that (the line of the beast):
    > cc: Error: ../../src/perlobj.c, line 666:
         In this statement, "p->info.array.value" and "len" cannot be added. (noadd)
    > memmove(p->info.array.value+len, p->info.array.value, olen+1 );
    > --------^
    > As far as I can tell, p->info.array.value is a void*, so adding an int to
    > it is not allowed.  I suggest you explicitly cast it to (char *), like in the
    > previous line, *((char *)(p->info.array.value)+olen) = 0;
    > This is also the case in lines 615, 713, 813, and 837.
  Fixed.  I wonder why GCC -warn did not catch this?
 
  (Reported by: Hans Peter Verne <[EMAIL PROTECTED]>)

Patrick Powell                 Astart Technologies,
[EMAIL PROTECTED]            9475 Chesapeake Drive, Suite D,
Network and System             San Diego, CA 92123
  Consulting                   858-874-6543 FAX 858-279-8424 
LPRng - Print Spooler (http://www.lprng.com)

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to