pkg/38613: www/firefox 2.0.0.14: segmentation fault durning compilation

[johan.wallen+gnats%helsinki.fi@localhost]

>Number:         38613
>Category:       pkg
>Synopsis:       www/firefox 2.0.0.14: segmentation fault durning compilation
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 08 18:40:00 +0000 2008
>Originator:     Johan Wallen
>Release:        NetBSD 4.99.62, May 8 06:10 EEST 2008
>Organization:
University of Helsinki
>Environment:
NetBSD enigma.tcs.hut.fi 4.99.62 NetBSD 4.99.62 (ENIGMA) #5: 
Thu May  8 16:36:29 EEST 2008 
johan%enigma.tcs.hut.fi@localhost:/usr/obj/macppc/sys/arch/macppc/compile/ENIGMA
macppc
>Description:
work/mozilla/security/nss/cmd/shlibsign dies with a segmentation fault
when compiling www/firefox (version 2.0.0.14). The backtrace is

  Core was generated by `shlibsign'.
  Program terminated with signal 11, Segmentation fault.
  #0  0xefbf719c in pthread_key_create () from /usr/lib/libpthread.so.0
  (gdb) bt
  #0  0xefbf719c in pthread_key_create () from /usr/lib/libpthread.so.0
  #1  0xefe0cca8 in _PR_InitThreads ()
     from /usr/pkgsrc/www/firefox/work/mozilla/dist/lib/libnspr4.so
  #2  0xefdfd91c in _PR_ImplicitInitialization ()
     from /usr/pkgsrc/www/firefox/work/mozilla/dist/lib/libnspr4.so
  #3  0xefdf70f0 in PR_Calloc ()
     from /usr/pkgsrc/www/firefox/work/mozilla/dist/lib/libnspr4.so
  #4  0xefe5329c in PL_CreateOptState ()
     from /usr/pkgsrc/www/firefox/work/mozilla/dist/lib/libplc4.so
  #5  0x01802bb8 in main ()
>How-To-Repeat:
cd pkgsrc/www/firefox
make patch

  [If needed, edit the `Test for correct temporary object destruction
  order' section in work/mozilla/configure.in, and change the
  AC_MSG_ERROR in that section to AC_MSG_WARN (this seems to be a 
  subtle, but harmles, bug that occur with some versions of firefox
  on some architectures/versions).]

make
>Fix:
Unknown, but it seems to have become manifest after the latest
libpthread changes (say, after mid April), but libpthread is 
probably not the culprit (or at least not the only one).