Re: unexelf.c failure on IRIX

[Eli Zaretskii]

On Tue, 20 Nov 2001, David Kaelbling wrote:

> I recently built emacs 21.1 on SGI IRIX 6.5, and found that if I
> enabled an x-toolkit (any kind), the resulting dumped emacs would die
> at startup with a bus error.

Thank you for your report.

Could you please send the configuration summary that the configure
script prints before it exist?  Here's an example which I get on SGI
Irix 6.5:

Configured for `mips-sgi-irix6.5'.

  Where should the build process find the source code?    
~eli/gnu/emacs-21/emacs-21.1
  What operating system and machine description files should Emacs use?
        `s/irix6-5.h' and `m/iris4d.h'
  What compiler should emacs be built with?               cc -D_LANGUAGE_C -g3 
-O -OPT:Olimit=3500
  Should Emacs use the GNU version of malloc?             yes
  Should Emacs use a relocating allocator for buffers?    no
  Should Emacs use mmap(2) for buffer allocation?         yes
  What window system should Emacs use?                    x11
  What toolkit should Emacs use?                          LUCID
  Where do we find X Windows header files?                Standard dirs
  Where do we find X Windows libraries?                   Standard dirs
  Does Emacs use -lXaw3d?                                 no
  Does Emacs use -lXpm?                                   no
  Does Emacs use -ljpeg?                                  yes
  Does Emacs use -ltiff?                                  yes
  Does Emacs use -lungif?                                 no
  Does Emacs use -lpng?                                   no
  Does Emacs use X toolkit scroll bars?                   no

I wonder what is different in your case, since I don't have the
problems you describe.

> Some trial and error showed that the
> following patch let it work again:
> 
> --- ./src/unexelf.c   Tue Sep 26 09:01:57 2000
> +++ ../emacs-21.1/./src/unexelf.c     Tue Nov 20 14:23:39 2001
> @@ -994,6 +994,10 @@
>                     ".lit4")
>         || !strcmp ((old_section_names + NEW_SECTION_H (n).sh_name),
>                     ".lit8")
> +#if __sgi
> +       || !strcmp ((old_section_names + NEW_SECTION_H (n).sh_name),
> +                   ".got")
> +#endif
>         || !strcmp ((old_section_names + NEW_SECTION_H (n).sh_name),
>                     ".sdata1")
>         || !strcmp ((old_section_names + NEW_SECTION_H (n).sh_name),
> @@ -1172,6 +1176,10 @@
>                       ".lit4")
>           || !strcmp ((old_section_names + NEW_SECTION_H (nn).sh_name),
>                       ".lit8")
> +#if __sgi
> +         || !strcmp ((old_section_names + NEW_SECTION_H (nn).sh_name),
> +                     ".got")
> +#endif
>           || !strcmp ((old_section_names + NEW_SECTION_H (nn).sh_name),
>                       ".sdata1")
>           || !strcmp ((old_section_names + NEW_SECTION_H (nn).sh_name),

Any idea where did those sections come from?  Are you using some
special compiler or linker?  (I used the native Irix tools.)