Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!math.ohio-state.edu!usc!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hasty
From: hasty@netcom.com (Amancio Hasty Jr)
Subject: Re: FreeBSD: emacs: missing library!?
Message-ID: <hastyCsG4n9.ACw@netcom.com>
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
References: <2va3j1$5f0@agate.berkeley.edu> <2va64i$5d9@ohlone.kn.PacBell.COM> <JKH.94Jul5010029@whisker.hubbard.ie>
Date: Tue, 5 Jul 1994 02:37:57 GMT
Lines: 63
In article <JKH.94Jul5010029@whisker.hubbard.ie> jkh@whisker.hubbard.ie (Jordan Hubbard) writes:
>In article <2va64i$5d9@ohlone.kn.PacBell.COM> smui@news.kn.PacBell.COM (Sherman Mui) writes:
>
> Anthony Monroe (tmonroe@soda.berkeley.edu) wrote:
> : Funny...when I tried to install emacs on my machine (even though I'm not the
> : biggest fan of it) I got the same message every time I tried to run it.
> ^^^^^^^^^^^^^^^^^
> Why not!? :-)
>
> : Well, I can't remember it exactly, but it amounted to "Segmentation fault --
> : core dumped." And it would just put me back at the prompt. And this is
>
> Doesn't that mean it tried to get some memory already taken?
>
>Uhhhh. You guys are all WAY offbase! The `segmentation fault' is caused
>when the program attempts an illegal memory access, not because it
>tried to use memory already allocated to someone else! :-) [All processes
>have their OWN address space]. An example:
>
>jkh@whisker-> cat > foo.c
>main()
>{
> char *foo = 0;
>
> *foo = 10;
>}
>jkh@whisker-> cc foo.c -o foo
>jkh@whisker-> ./foo
>Segmentation fault (core dumped)
>
>Make more sense?
>
>So the emacs problem is not the result of trying to use `already
>allocated memory' or `trying to use too much memory' (I run emacs + X
>in 8MB all the time, for what it's worth), it's a bogus installation
>of emacs! To put it more bluntly: When Antony attempted to install
>emacs, he blew it somewhere..
>
I have had strange problems similar to the ones described in the
original postings:
1) When using flexfax it failed to find the default libraries for
gs. I made all directories in the path to the gs libraries "a+rx".
That did the trick.
2) Make sure that you have the appropiate default path for all the
libraries. If not then emacs will failed to see the library.
So do: "ldconfig -r" to find out if the emacs libraries are
included. If, the command does not show the emacs' libraries,
Read ldconfig to find out how to configure the search path
for shared libraries.
Enjoy,
Amancio
--
FREE unix, gcc, tcp/ip, X, open-look, netaudio, tcl/tk, MIME, midi,sound
at freebsd.cdrom.com:/pub/FreeBSD
Amancio Hasty, Consultant |
Home: (415) 495-3046 |
e-mail hasty@netcom.com | ftp-site depository of all my work:
| sunvis.rtpnc.epa.gov:/pub/386bsd/X