Subject: Re: Building emacs 20.2 fails while linking
To: None <erik@mediator.uni-c.dk>
From: Todd Vierling <tv@pobox.com>
List: current-users
Date: 04/06/1998 16:48:38
On Sun, 5 Apr 1998 erik@mediator.uni-c.dk wrote:

: By the way: the reason that I have brought this up, is that I first got this
: link problem with a pretest version of Emacs 20.3 (which I should probably
: not mention here :-)) and then noticed the same problem with the latest release
: of Emacs, i.e. 20.2, and I would prefer to be able to tell RMS that on
: post 1.3 versions of NetBSD, -nostdlib requires a -L/usr/lib -- but I will
: hate to tell him this unless it's really true. Even if we have a working
: package system, we should still make it possible to build utilities like
: Emacs out of the box.

You should probably let whomever you're doing pretest evaluation with know
that the appropriate thing to do is this--I've changed my local pkgsrc to
patch up emacs 20.2 properly and will commit it when the cvs server comes
back:

- use -nostartfiles instead of -nostdlib
- do not specify -lc or try to find the path to libgcc
- do not try to specify -L/usr/lib

I do not know if this breaks older gcc's.  That's "not my department," but
the above actions do make the build more "appropriate," where system
libraries are still searched like they should be (some systems may at some
point need to include more than just -lc by default such as -lgcc), and the
C runtime file(s) are left out so that emacs can put its pre-crt0 where it
wants to. 

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)