Compiling Pine 4.44 with Jaguar
rhoge
> *** Saul Good (saul...@yahoo.com) wrote in comp.mail.pine on Aug 7, 2002:
>
> :) Hello, I am trying to compile Pine with Jaguar and gcc3.1, but I get the
> :) following errors:
> :)
> :) Making Pico and Pilot
> :) make CC=cc -f makefile.osx
> :) rm -f os.h
> :) ln -s osdep/os-osx.h os.h
> :) cc -g -DDEBUG -Dbsd -DJOB_CONTROL -c -o main.o main.c
> :) In file included from headers.h:31,
> :) from main.c:38:
> :) os.h:184: conflicting types for `sys_nerr'
> :) /usr/include/stdio.h:265: previous declaration of `sys_nerr'
> :) make: *** [main.o] Error 1
>
> Quite interesting. Edit the file pine4.44/pico/os.h and remove the
> definition of sys_nerr. That should fix this problem.
>
>
I recently got pine4.44 to build under Jaguar - the pine binary that
came with 10.1 would not run under 10.2 for me. Here are the changes
I had to make to the 4.44 source tree - note that I am using the new
developers tools that came in the Jaguar box (based on gcc v3.1):
tar -zxvf pine.tar.Z
mkdir /usr/local/certs
(we don't use certs - this just avoids a warning, probably not needed.
you still get a nonfatal warning about missing factory.pem...)
modify pine4.44/pine/makefile.osx:
STDLIBS= -lncurses
(add ncurses libs)
modify pine4.44/pico/osdep/os-osx.h:
#include <sys/unistd.h> // add this line after #include <sys/dir.h>
...
// extern int sys_nerr; // this is already defined - comment out
modify pine4.44/pico/makefile.osx:
LIBS= $(EXTRALDFLAGS) -lncurses
(add ncurses libs)
cd pine4.44
./build SSLCERTS=/usr/local/certs \
SSLINCLUDE=/usr/include/openssl \
SSLLIB=/usr/lib osx
this built ok for me. Of course emacs also died and had to futz around
with that also... worked in the end.
Rick
Christopher W Aiken
> On Thu, 8 Aug 2002, Eduardo Chappa wrote:
>
>> *** Saul Good (saul...@yahoo.com) wrote in comp.mail.pine on Aug 7, 2002:
>>
>> :) Hello, I am trying to compile Pine with Jaguar and gcc3.1, but I get the
>> :) following errors:
>> :)
>> :) Making Pico and Pilot
<SNIP>
>
> I recently got pine4.44 to build under Jaguar - the pine binary that
> came with 10.1 would not run under 10.2 for me. Here are the changes
> I had to make to the 4.44 source tree - note that I am using the new
> developers tools that came in the Jaguar box (based on gcc v3.1):
>
> tar -zxvf pine.tar.Z
>
> mkdir /usr/local/certs
> (we don't use certs - this just avoids a warning, probably not needed.
> (add ncurses libs)
>
<SNIP>
>
> this built ok for me. Of course emacs also died and had to futz around
> with that also... worked in the end.
>
> Rick
>
Thanks Rick!! Works like a charm. My trusty pine is back up and running.
--
-=[cwa]=-
e-Mail: cwaiken at roadlynx dot net
e-Mail: cwa at cwaiken dot net
Home: www.cwaiken.net
Jeffrey Goldberg
> I recently got pine4.44 to build under Jaguar
Just confirming (and testing) a "me, too". Thanks for your outstanding
post.
Note that I haven't properly set my configuration correctly. So this
message isn't really properly set up. Time to start using "configuration
on IMAP server" features that I've always thought were great in principle,
but never played with.
[snip of fixes that need to be made to various makefiles and osdep files]
> ./build SSLCERTS=/usr/local/certs \
> SSLINCLUDE=/usr/include/openssl \
> SSLLIB=/usr/lib osx
>
> this built ok for me.
If you want to populate /usr/local/certs on Jaguar, the following worked
for me.
o get the lastest openssl.tar.gz from www.openssl.org
o unpacking it someplace
tar -zxvf openssl-VERSION.tar.gz
o copy all of the files in openssl-VERSION/certs to /usr/local/certs
cd openssl-VERSION/certs; sudo cp * /usr/local/certs
(you'll get warning about "expired" not being copied. That's fine
unless you want the experired certs there as well)
o Use create hash tool to get the links needed for these
cd ../tools; sudo perl c_rehash certs /usr/local/certs
Then when you compile pine with your instructions, you won't get a warning
about certs not being properly installed. Why Jaguar doesn't have those
installed is a mystery to me.
-j