Date: Fri, 25 Jun 2004 00:04:16 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 397 ************************************************** Thursday 24 June 2004 Number 397 ************************************************** Subjects for today 1 Server problems : John Poltorak 2 Re: Pine 4.60 is here : John Poltorak 3 Re: Python 2.3.4 for OS/2+EMX now available. : John Poltorak 4 Re: Pine 4.60 is here : Nicholas Sheppard 5 linker errors : Pete Milne **= Email 1 ==========================** Date: Wed, 23 Jun 2004 18:00:06 +0100 From: John Poltorak Subject: Server problems Apologies to anyone who has tried sending msgs to the list over the last week or so. My main server hung and then subsequently kept trapping in HPFSMINI during a reboot. I finally cracked the problem by ignoring it completely for a couple of days and trying again and today everything came up without any problems so I have no idea about what went wrong or why. Oh - the joys of computing! Anyway the list is back up now... -- John **= Email 2 ==========================** Date: Wed, 23 Jun 2004 18:08:50 +0100 From: John Poltorak Subject: Re: Pine 4.60 is here On Sun, May 30, 2004 at 10:17:54PM +0000, Nicholas Sheppard wrote: > Hi all. > > I've just uploaded Pine 4.60 for OS/2 to Hobbes. This is a revised port > that brings the OS/2 version closer to the Unix and NT versions. It has > become fairly stable in testing over the past year or so but nonetheless > it may introduce some new issues that weren't in Pine 4.58. > > In particular, either the bugs are getting harder or I am getting > stupider because there are some bugs that I wasn't able to fix between > 4.58 and 4.60 being released: > > * crash when composing mail if IMAP addressbooks are present but > unopened (also a 4.58 bug) > > * crash when accessing Unix-format mailboxes (I have one report of > this working okay but it doesn't work for me) > > * intermittent crashes with very large mailboxes (also a 4.58 bug) > > * SSL/TLS is untested > > Some people may prefer to stick with Pine 4.58 until Pine 4.6x gets > smoothed out, but 4.60 is working fine for everyday e-mail for me. > > Because of the problem with Unix-format mailboxes, I haven't yet made > a binary distribution of the UW POP3 and IMAP servers though they can > be compiled using the source code patches available from the OS/2 Pine > site. If anyone is interested I can send you the executables privately. > I will make them publically available once I have fixed the Unix-format > bug. I would really like to get this built from source but have never managed to do so. I tried following the build instructions for 4.58 but never managed it. Is there a simple script I can run? > As usual, all the most recent information about and source code for Pine > for OS/2 is available from my web site at > > http://www.zeta.org.au/~nps/software/pine/en/index.html > > Nicholas S. -- John **= Email 3 ==========================** Date: Wed, 23 Jun 2004 18:03:41 +0100 From: John Poltorak Subject: Re: Python 2.3.4 for OS/2+EMX now available. Great! I look forward to giving it a try. Is there any chance it might fix the problems I was having with Mailman? Also, can I expect to build it from source using the standard configure and make procedure? On Sun, Jun 06, 2004 at 11:08:32PM +1000, Andrew MacIntyre wrote: > I've uploaded a binary distribution of the Python 2.3.4 EMX port to > Hobbes, and it is also available from my Python page. > > I've also released a binary package of psyco 1.2 for the Python 2.3.x EMX > port, superceding the psyco 1.1.1 package previously available. > > Enjoy! > Andrew. > > -- > Andrew I MacIntyre "These thoughts are mine alone..." > E-mail: andymac at bullseye.apana.org.au (pref) | Snail: PO Box 370 > andymac at pcug.org.au (alt) | Belconnen ACT 2616 > Web: http://www.andymac.org/ | Australia -- John **= Email 4 ==========================** Date: Thu, 24 Jun 2004 08:51:56 +1000 (EST) From: Nicholas Sheppard Subject: Re: Pine 4.60 is here On Wed, 23 Jun 2004, John Poltorak wrote: > > I would really like to get this built from source but have never managed > to do so. I tried following the build instructions for 4.58 but never > managed it. > > Is there a simple script I can run? From go to woah, no. Pine doesn't use a configure script so you have to set up all the paths and programme names for your local system manually. Once you have done that, you can just run `build.cmd' and it will build. I made some improvements to build.cmd for 4.60 to make it a little easier but there might still be improvements to be made. Nicholas S. **= Email 5 ==========================** Date: Thu, 24 Jun 2004 12:12:33 +0100 From: Pete Milne Subject: linker errors Can anyone help? I have resumed battle with an old foe (gnotepad+ 1.3.3.) When I do configure --without-included-gettext then add "-lintl -lpthrdrtl -lcExt" to LIBS in the makefile, then make I get the following error from the linker: gcc -D__EMX__ -DOS2 -Zmtd -D__ST_MT_ERRNO__ -Zexe -O2 -fomit-frame-pointer -Zmt -D__ST_MT_ERRNO__ -DNEED_GNOMESUPPORT_H -Ij:/XFree86/include/gtk12 -Ij:/XFree86/include/glib12 -Ij:/XFree86/include -Zmtd -D__ST_MT_ERRNO__ -O2 -s -Zsysv-signals -Zstack 512 -lcExt -lstcExt -Zmtd -Zsysv-signals -Zbin-files -Lj:/XFree86/lib -o gnp -Zmtd -Zsysv-signals -Zbin-files -lgnomeui -lart_lgpl -lgnome -lregex -ldb -lgdk_imlib -lSM -lICE -lgtk-xmhtml -lgnomesupport -lpng -ltiff -ljpeg -lgif -lz -lXpm -lgtk12 -lgdk12 -lXext -lX11 -lshm -lglib12 -lbsd -lsocket -lintl -lpthrdrtl -lcExt file.o: Undefined symbol _pthread_sleep referenced from text segment shellcmd.o: Undefined symbol _pthread_read referenced from text segment sleep() and read() are redefined by pthread.h to pthread_sleep and pthread_read; however, pthrdrtl (according to its properties notebook) doesn't export these two symbols. Is it likely to be safe to remove these two #defines? If I try linking statically with pthread.a I get even more undefined symbols: J:/emx/lib/mt/pthread.a(uthread_read.o): Undefined symbol _recv referenced from text segment J:/emx/lib/mt/pthread.a(uthread_read.o): Undefined symbol _recvfrom referenced from text segment J:/emx/lib/mt/pthread.a(uthread_read.o): Undefined symbol _accept referenced from text segment Where am I going wrong? tia Pete