From: Tim McNamara <timmcn@bitstream.net>
Subject: Re: Emacs from CVS question
Date: Sun, 30 Nov 2003 13:36:58 -0600 [thread overview]
Message-ID: <m2d6b9d4x1.fsf@bitstream.net> (raw)
In-Reply-To: m3oeutj4aa.fsf@ID-177771.users.individual.de
Martin Stemplinger <mstemplingerNOSPAM@gmx.de> writes:
> On Sam Nov 29 2003 at 16:56, Tim McNamara <timmcn@bitstream.net> wrote:
>
>> 4. The Xaw3d toolbars are missing from my build of 21.3, but are
>> present in the 21.2 build from fink. My impression was that this
>> should have been included in the build automagically, but wasn't.
>>
> Did you include the option --with-x-toolkit to configure
> (./configure --help tells you all options that you can use)?
I didn't explicitly invoke that, although configure indicated it would
build Emacs wth the "lucid" toolkit. However, the Xaw3d libraries
might be installed in a non-standard location my fink and perhaps the
compiler didn't find them. I'll have to hunt around some more. The
directories where fink puts stuff are a separate directory tree in
/sw; /sw is in my $PATH but perhaps that didn't help the compiler.
This compiling stuff is an interesting adventure for a long-time Mac
user! Unix users seem to be well-accustomed to this set of skills,
but it's alien territory for us Mac-heads.
next prev parent reply other threads:[~2003-11-30 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-29 15:56 Emacs from CVS question Tim McNamara
2003-11-30 6:20 ` Eli Zaretskii
[not found] ` <mailman.805.1070176829.399.help-gnu-emacs@gnu.org>
2003-11-30 6:54 ` Tim McNamara
2003-11-30 7:12 ` Eli Zaretskii
2003-11-30 12:43 ` Glenn Morris
2003-11-30 19:30 ` Tim McNamara
2003-11-30 13:20 ` Piet van Oostrum
2003-11-30 19:32 ` Tim McNamara
2003-11-30 14:54 ` Martin Stemplinger
2003-11-30 19:36 ` Tim McNamara [this message]
2003-11-30 20:30 ` Hugh Wolf
2003-11-30 22:03 ` Tim McNamara
2003-11-30 22:45 ` Hugh Wolf
2003-12-01 1:21 ` Tim McNamara
2003-12-02 0:08 ` Hugh Wolf
2003-12-02 0:39 ` Tim McNamara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d6b9d4x1.fsf@bitstream.net \
--to=timmcn@bitstream.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).