Mercurial > hg > xemacs-beta

comparison aclocal.m4 @ 5495:1f0b15040456

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Merge.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 01 May 2011 18:44:03 +0100
parents 4dee0387b9de
children
comparison
equal deleted inserted replaced
5494:861f2601a38b 5495:1f0b15040456
1 dnl aclocal.m4 --- Dynamically linked library support for XEmacs 1 dnl aclocal.m4 --- Dynamically linked library support for XEmacs
2 dnl Copyright (C) 1998, 1999 J. Kean Johnston. 2 dnl Copyright (C) 1998, 1999 J. Kean Johnston.
3 dnl Author: J. Kean Johnston <jkj@sco.com>, based on work in libtool. 3 dnl Author: J. Kean Johnston <jkj@sco.com>, based on work in libtool.
4 dnl This file is part of XEmacs. 4 dnl This file is part of XEmacs.
5 5 dnl
6 dnl XEmacs is free software: you can redistribute it and/or modify it
7 dnl under the terms of the GNU General Public License as published by the
8 dnl Free Software Foundation, either version 3 of the License, or (at your
9 dnl option) any later version.
10 dnl
11 dnl XEmacs is distributed in the hope that it will be useful, but WITHOUT
12 dnl ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
13 dnl FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
14 dnl for more details.
15 dnl
16 dnl You should have received a copy of the GNU General Public License
17 dnl along with XEmacs. If not, see <http://www.gnu.org/licenses/>.
6 dnl 18 dnl
7 dnl There are several things we care about here. First, we need to find 19 dnl There are several things we care about here. First, we need to find
8 dnl out how we create an executable that has its symbols exported, so 20 dnl out how we create an executable that has its symbols exported, so
9 dnl that dynamically loaded modules have access to the internal XEmacs 21 dnl that dynamically loaded modules have access to the internal XEmacs
10 dnl symbols. This is stored in ``ld_dynamic_link_flags'' and is used 22 dnl symbols. This is stored in ``ld_dynamic_link_flags'' and is used
201 dnl So, having said all of that, we diverge from libtool significantly 213 dnl So, having said all of that, we diverge from libtool significantly
202 dnl here. We want to try and use the C compiler as much as possible. Only 214 dnl here. We want to try and use the C compiler as much as possible. Only
203 dnl if the C compiler itself cannot create shared libraries do we try to 215 dnl if the C compiler itself cannot create shared libraries do we try to
204 dnl find the linker. 216 dnl find the linker.
205 dnl 217 dnl
206 dnl The other advantage to my scheme is that it removes the dependancy 218 dnl The other advantage to my scheme is that it removes the dependency
207 dnl on a given compiler version remaining static with relation to the 219 dnl on a given compiler version remaining static with relation to the
208 dnl version of XEmacs. With the libtool way, it picks up the linker that 220 dnl version of XEmacs. With the libtool way, it picks up the linker that
209 dnl gcc uses, which can be the internal collect2 that comes with gcc. 221 dnl gcc uses, which can be the internal collect2 that comes with gcc.
210 dnl If the user ever changes their compiler version, the paths will no 222 dnl If the user ever changes their compiler version, the paths will no
211 dnl longer be correct, and ellcc will break. This is clearly unacceptable. 223 dnl longer be correct, and ellcc will break. This is clearly unacceptable.