bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1191: How to contribute back changes for Emacs on Solaris


From: Ali Bahrami
Subject: bug#1191: How to contribute back changes for Emacs on Solaris
Date: Thu, 23 Oct 2008 00:45:43 -0600
User-agent: Thunderbird 2.0.0.12 (X11/20080228)

Dan,

   I made the changes you suggested to the src/s/sol2-10.h. I
pulled a copy of CVS head, and produced diffs for configure.in based
on that. Both items are below, delimited by '=======' lines.

configure.in has changed since emacs 22.1, and there's a lot
less cruft there. As a result, this version of the change is simpler
than the previous one.

I've build the result on Nevada Solaris (OpenSolaris) and on Solaris 9,
and both work as expected.

-----

FYI: CVS HEAD does not build on Solaris 10. This is not due to my changes,
as I tried it on an unmodified workspace as well. The end of the
output is:

        checking for SmcOpenConnection in -lSM... no
        checking whether netdb declares h_errno... no
        checking for working alloca.h... no
        checking for alloca... no
        checking whether `alloca.c' needs Cray hooks... no
        checking stack direction for C alloca... -1
        configure: error: a system implementation of alloca is required

Solaris has alloca, so something is up with the test being used.
However, the changes I'm proposing here are orthogonal to whatever
is happening with that.

- Ali


=========================================================================
/* Handle Solaris 2.10 */

#include "sol2-6.h"

/*
 * Use the native system malloc()
 */
#define SYSTEM_MALLOC

/*
 * Use the Solaris dldump() function, called from unexsol.c, to dump
 * emacs, instead of the generic ELF dump code found in unexelf.c.
 * The resulting binary has a complete symbol table, and is better
 * for debugging and other observabilty tools (debuggers, pstack, etc).
 *
 * If you encounter a problem using dldump(), please consider sending
 * a message to the OpenSolaris tools-linking mailing list:
 *      http://mail.opensolaris.org/mailman/listinfo/tools-linking
 *
 * It is likely be that dldump() works with older Solaris too,
 * but this has not been tested, and so, this change is for
 * Solaris 10 and newer only at this time.
 */
#undef UNEXEC
#define UNEXEC unexsol.o
=========================================================================
*** configure.in.orig   Wed Oct 22 20:40:42 2008
--- configure.in        Wed Oct 22 20:53:20 2008
***************
*** 442,449 ****
    ;;

    *-sun-solaris* \
!     | i[3456]86-*-solaris2* | i[3456]86-*-sunos5* | powerpc*-*-solaris2* \
!     | rs6000-*-solaris2*)
      case "${canonical}" in
        i[3456]86-*-* )     machine=intel386 ;;
        amd64-*-*|x86_64-*-*)   machine=amdx86-64 ;;
--- 442,450 ----
    ;;

    *-sun-solaris* \
!     | i[3456]86-*-solaris2* | i[3456]86-*-sunos5* \
!     | x86_64-*-solaris2*    | x86_64-*-sunos5*    \
!     | powerpc*-*-solaris2*  | rs6000-*-solaris2*)
      case "${canonical}" in
        i[3456]86-*-* )     machine=intel386 ;;
        amd64-*-*|x86_64-*-*)   machine=amdx86-64 ;;
***************
*** 471,480 ****
                NON_GNU_CPP=/usr/ccs/lib/cpp
                RANLIB="ar -ts"
                ;;
!       *-sunos5* | *-solaris* )
                opsys=sol2-6
                emacs_check_sunpro_c=yes
                NON_GNU_CPP=/usr/ccs/lib/cpp
                ;;
      esac
      ## Watch out for a compiler that we know will not work.
--- 472,486 ----
                NON_GNU_CPP=/usr/ccs/lib/cpp
                RANLIB="ar -ts"
                ;;
!       *-sunos5.[7-9]* | *-solaris2.[7-9]* )
                opsys=sol2-6
                emacs_check_sunpro_c=yes
                NON_GNU_CPP=/usr/ccs/lib/cpp
+               ;;
+       *-sunos5* | *-solaris* )
+               opsys=sol2-10
+               emacs_check_sunpro_c=yes
+               NON_GNU_CPP=/usr/ccs/lib/cpp
                ;;
      esac
      ## Watch out for a compiler that we know will not work.
=========================================================================






reply via email to

[Prev in Thread] Current Thread [Next in Thread]