Subject: Pine and Data General Aviion

From: [email-masked] (Mike Reardon)
Date: Tue, 28 Nov 1995 12:17:19 -0600

I am having difficulty compiling Pine to run on a Data General Aviion machine.

Anyone else running under DG/UX?

Mike

---

From: "Brian P. Hampson" <[email-masked]>
Date: Wed, 29 Nov 1995 08:44:08 -0800 (PST)

> Anyone else running under DG/UX?

Errors?  What are you getting?

B.

   ------------------------------------------------------------------------
   |Brian P. Hampson                  Internet: [email-masked]      |
   |System Administrator,                                                 |
   |Analytical Service Labs           Fidonet : Brian Hampson 1:153/733   |
   |Vancouver, BC                                                         |
   |+604-253-4188                                                         |
   |               Specialists in Environmental Chemistry                 | 
   |                                                                      |
   ------------------http://www.asl-labs.bc.ca/----------------------------

---

From: [email-masked] (Joe Cygan)
Date: 29 Nov 1995 17:05:49 GMT

Mike Reardon ([email-masked]) wrote:
: I am having difficulty compiling Pine to run on a Data General Aviion machine.

: Anyone else running under DG/UX?

: Mike

Yes.  I puchased the other machine they sold last year.  And, no, I cannot get
it to compile either.  You havig the problem with c-client as well?  On mine
I'm trying pine3.91 and "build d-g" seems to work fine on pico and most of
the source.  But, with c-client it gets stuck on os_d-g.c with the "times" 
definition.  Then ... BOOM>

If you can find anything, please let me know.  There was some traffic on this
subject about a year ago in comp.sys.m88k.

Joe

---

From: [email-masked] (Mike Reardon)
Date: Wed, 29 Nov 1995 15:02:13 -0600

> subject about a year ago in comp.sys.m88k.

The following was sent to me by [email-masked]:

add a line to c-client/os_d-g.c:

   #include "log_std.c"
   #include "gr_waitp.c"
   #include "tz_sv4.c"
+  #include <utime.h>

   #undef utime

This worked here this morning...

---

From: "Brian P. Hampson" <[email-masked]>
Date: Wed, 29 Nov 1995 14:40:05 -0800 (PST)

> add a line to c-client/os_d-g.c:

Try putting the <utime.h> at the TOP of the file...before other includes.
Then I don't think you need the undef.  Then things should work...Replies 
et al, from what I recall.

B.

   ------------------http://www.asl-labs.bc.ca/----------------------------

---

From: [email-masked] (Mike Reardon)
Date: Wed, 29 Nov 1995 14:56:14 -0600

> Errors?  What are you getting?

I am able to compose and send mail, read mail, forward mail, but NOT reply
to mail.  I get a core dump and Pine croaks at that point.  Forwarding
works fine, but not replying.

Anyone have any ideas?

---

From: [email-masked] (Mike Reardon)
Date: Wed, 29 Nov 1995 14:57:23 -0600

Anyone have any ideas?

---

From: [email-masked] (Mike Reardon)
Date: 30 Nov 1995 00:36:30 GMT

In article <Pine.D-G.3.91.951129143904.295A-100000@asl3>, 
[email-masked] says...

>et al, from what I recall.

I'll try that in the morning.  Thanks for the suggestion!

---

From: [email-masked] (Jason Baker)
Date: 30 Nov 1995 17:22:12 GMT

>et al, from what I recall.

I've been having a bear of a time getting 3.91 to compile on an AV5500
as well, and until I can get a version of Pine that lets me tell it how
to handle wierd mime types (like Content-Type: application/pgp; 
format=text; x-action=sign) I can't use the full features of ELM. *sigh*

Anyways, enough whining...

It sounds like where I'm having the problem is not unique - I try to reply
to a message, and it crashes.  I've tried adding extra debug messages to
the source, to isolate exactly where I get the failure, but so far it
seems to get to the end of end_tty_driver and vanishes.  This is *after*
it's gone through auger_in_signal from signal.c.

Here's a quick snippet:
*****
=== send called ===

  ---- COMPOSER ----
auger_in_signal()			<- Mine
about to end_tty_driver
post raw(0) call			<- Mine
Pine Panic: Received abort signal

save_debug_on_crash: Version 3.91: debug level 2

                   : Wed Nov 29 23:06:32 1995

Attempting to save debug file to /home/bm11455/.pine-crash
*****

Am I correct in thinking you've seen this before, or something similar
to it?
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 [email-masked]                    | To err is human; to really
 Systems Administrator, Information Systems    | bugger things up requires
 BC Family Maintenance Enforcement Program     | the root password.

 print unpack("u","92G5S\=\"!A;F]T:&5R(\'!E<FP\@:&%C:V5R\"\@\`\`");