Subject: Re: Problem attaching files of type Text/HTML

From: "Eduardo Chappa L." <[email-masked]>
Date: Mon, 26 Jul 1999 09:16:42 -0700 (PDT)

Hello 

  The problem about attachments of HTML files has been a topic of
discussion both in the pine-info list as in comp.mail.pine. The following
message appeared in comp.mail.pine. I tried the patch suggested there and
it worked! In my case uname -a says OSF1 goedel3 V4.0 878 alpha

  Thanks for the patch, it certainly did solve this problem for me.

Eduardo
http://www.math.washington.edu/~chappa/personal.html

*** Jeremy Blackman ([email-masked]) wrote on Jul 25, 1999:

:)>  I reported the same problem a few weeks ago, I received a message
:)> from the pine team asking me for my .pine-debug files, and they
:)> answered me that this one was a difficult one, they hadn't catch it
:)> yet. Up to the moment no one has answered me why this occurs, if
:)> someone lets you know, please let me know. I myself tried several
:)> ways to change the headers, and could not do it.
:) 
:) 
:) Hey, wait, me and one other person not only tracked this down but
:) SUBMITTED A FIX several weeks ago.  <grumble>
:) 
:) It's not, technically speaking, a bug in PINE.  It is a bug in
:) egcs/gcc, where in one particular case, an optimization causes a
:) return result from one of the MIME handler routines to get utterly
:) clobbered.  (This is probably also why it does BASE64 encoding when
:) quoted-printable would be more appropriate, but we didn't bother to
:) try debugging that one. Step-debugging PINE for one bug is pain
:) enough, thank you.)
:) 
:) I know for a fact that this bug affects x86 versions of egcs/gcc
:) after 2.7.2 (because I tried it on a variety of machines), and I've
:) been told by someone that the Alpha architecture also has this
:) problem.  (The bug was submitted to the egcs/gcc team, as well.)  
:) The bug causes the return to contain a '0', no matter what the
:) actual return result was, when the program returns to the calling
:) function - this causes PINE to assume certain (incorrect) defaults.
:) 
:) With a simple alteration to that particular routine in PINE to force
:) egcs/gcc to be unable to optimize that one step (e.g. add
:) 'sleep(0);' before the return), PINE correctly attaches things
:) again.  This particular bug affects several MIME types, text/html is
:) merely the most noticable.
:) 
:) The patch in question can be found at:
:) ftp://ftp.listar.org/pub/listar/other/pine4.10-mimetype.patch
:) 
:) (The bug was discovered while working on the MIME handling for the
:) Listar mailing list package, hence the location of the patch.  
:) There's also a patch to add minimal RFC2369 support to PINE in that
:) same directory, as pine4.10-listserv.patch)
:) 
:) Hope that helps!
:) 
:) 
:) 
:)

---

From: Brian Salter-Duke <[email-masked]>
Date: Tue, 27 Jul 1999 11:38:12 +1100

Greetings Eduardo and other pine users.

Thank you for the patch details. It worked! However, it does raise
wider issues. The information below talks about a problem with gcc
and alpha platforms. I am using a IBM RS6000 running AIX 3.2.5
and compiling with the AIX cc compiler. It looks as if this is
a more general bug in version 4.10. I hope this patch fixes some
related problems, but it certainly fixes the html problem.

Cheers, Brian.

-- 
        Associate Professor Brian Salter-Duke (Brian Duke)
Chemistry, Faculty of Science, IT and Education, Northern Territory University,
  Darwin, NT 0909, Australia.  Phone 08-89466702. Fax 08-89466847
[email-masked]  http://www.smps.ntu.edu.au/school/compchem.html

---

From: Jessica Rasku <[email-masked]>
Date: Mon, 26 Jul 1999 21:15:16 -0700 (PDT)

> related problems, but it certainly fixes the html problem.

	This is a known problem (I believe) with GCC and EGCS (you seem to
be talking about AIX cc causing a similar problem? intresting).  In the
recent Linux Kernel instructions it says to use gcc 2.7.2, as the 2.8
versions do ``bad things''.  Unfortunately, it didn't say what these ``bad
things'' are, and how to over ride them.  Unfortunately other programs
will not compile with gcc 2.7.2, which makes it very difficult to deal
with both of these situations (and in my hunt to do this upgrade I
couldn't locate EGCS, which MAY have allowed me to have that for those
that need the ``modern'' compiler, while having GCC 2.7.2.1 avalable for
programs that don't like the later compilers...).

							Jessica

-- 
Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, 
LinuxBox: (250) 362-9668.

List manager: [email-masked] 
     send command help ---- To get help with majordomo
               or lists ---- To get a list of all lists on server.

WWW: <http://www.geocities.com/RainForest/Andes/8749>

---

From: "Daniel Sands" <[email-masked]>
Date: Tue, 27 Jul 1999 08:14:38 -0600

> programs that don't like the later compilers...).

This is off-topic, but:
EGCS can be found at egcs.cygnus.com

Also, if you upgrade to the 2.2.x kernels, you can build them with the latest
compilers.  So I have thrown away 2.7.x already.