Subject: Re: Pine crashes immediately on NetBSD

From: Art McGee <[email-masked]>
Date: Sun, 18 Jan 2004 05:21:32 -0500 (EST)

> I am using NetBSD and I am having problems compiling Pine
> successfully...

Robert, you forgot to mention that you are using NetBSD on
a DEC Alpha system (I'm also a member of SDF), which is an
important distinction. The problems with compiling PINE
only seem to manifest under NetBSD on an Alpha. Other
NetBSD systems (x86, etc.), are not as trouble prone.

I've seen it mentioned in other forums that compiling
statically instead of dynamically might solve the problem.

Art

---

From: Robert Pendell <[email-masked]>
Date: Sun, 18 Jan 2004 08:11:38 -0500

Art McGee wrote:
|>I am using NetBSD and I am having problems compiling Pine
|>successfully...
|
|
| Robert, you forgot to mention that you are using NetBSD on
| a DEC Alpha system (I'm also a member of SDF), which is an
| important distinction. The problems with compiling PINE
| only seem to manifest under NetBSD on an Alpha. Other
| NetBSD systems (x86, etc.), are not as trouble prone.
|
| I've seen it mentioned in other forums that compiling
| statically instead of dynamically might solve the problem.
|

LOL.  Yes.  You are right.  I forgot to mention that indeed.  How would
I make sure the build is compiling statically instead of dynamically?
At the moment I would not be sure which way it is compiling.  Likewise
there is some clarification in order.  The compile finishes alright but
it is when I go and run the program that it just crashes right from the
start.

- --
Robert Pendell
[email-masked]

---

From: Matt Ackeret <[email-masked]>
Date: Mon, 19 Jan 2004 11:14:43 -0800 (PST)

>it is when I go and run the program that it just crashes right from the

gdb pine
run

and when it crashes, do
thread apply all bt

in gdb, and send the output?

At least that'll show _where_ it's crashing.

---

From: Robert Pendell <[email-masked]>
Date: Mon, 19 Jan 2004 14:36:14 -0500

Well, I did finally figure it out.  Really simple.  I had to include
signal.h into one of the files.  Well, actually another fellow user that
was also trying to compile on the same system figured it out.  That user
just forwarded the info to me.

| The "trick" was to actually read the output from the build script.  In the
| stderr, there is a warning regarding  "sigaction()"; it suggests "include
| <signal.h> for correct reference".

Heh.  It was simple.

- --
Robert Pendell
[email-masked]

Matt Ackeret wrote:
| On Sun, 18 Jan 2004, Robert Pendell wrote:
|
|>LOL.  Yes.  You are right.  I forgot to mention that indeed.  How would
|>I make sure the build is compiling statically instead of dynamically?
|>At the moment I would not be sure which way it is compiling.  Likewise
|>there is some clarification in order.  The compile finishes alright but
|>it is when I go and run the program that it just crashes right from the
|>start.
|
|
| gdb pine
| run
|
| and when it crashes, do
| thread apply all bt
|
| in gdb, and send the output?
|
| At least that'll show _where_ it's crashing.

---

From: Jeff Franklin <[email-masked]>
Date: Thu, 22 Jan 2004 14:09:04 -0800 (PST)

> just forwarded the info to me.

We've changed pine source to include signal.h instead of sys/signal.h in
pico/osdep/os-neb.h.  Looks like that should work for all flavors of
NetBSD.

Jeff

---

From: Robert Pendell <[email-masked]>
Date: Thu, 22 Jan 2004 22:27:50 +0000

> pico/osdep/os-neb.h.  Looks like that should work for all flavors of

Great to hear that.

-- 
Robert Pendell
[email-masked]