From: David Masterson <dsmasterson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Resources for an old newbie ?
Date: Sat, 03 Jun 2023 18:00:30 -0700 [thread overview]
Message-ID: <SJ0PR03MB5455CCC741F6766D4CD94D44A24CA@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <875y89z9m7.fsf@dataswamp.org> (Emanuel Berg's message of "Wed, 31 May 2023 01:24:00 +0200")
Emanuel Berg <incal@dataswamp.org> writes:
> Here are the minimal (?) commands required to install the
> latest Emacs on Debian.
>
> I removed the shell functions in this version, if that is what
> made it so scary last time. (But actually I recommend using
> functions: less error prone, faster and more reliable.)
>
> Anyway, as you now see below beyond doubt, it is
> a trivial affair.
>
> Installing Emacs is step 1-3 and 5, that is 12 commands.
> Upgrading it after that, step 4 and 5, is only 7 commands.
> All of them well familiar to most Joe Unix Hacker on
> the globe.
>
> If one can do it better or shorter, do say! And when we are
> done, we could mail the EmacsWiki maintainers and ask them to
> publish the list of commands, if they lack such a page.
>
> # 1. setup directories
> src_dir=~/src
> emacs_dir=${src_dir}/emacs
> mkdir -p $emacs_dir
>
> # 2. get dependencies
> sudo apt-get -qq update
> sudo apt-get install build-essential debian-goodies libgccjit-10-dev
> sudo apt-get build-dep emacs
This pulled in a *LOT* of stuff.
> # 3. get source
> cd $src_dir
> git clone https://git.savannah.gnu.org/git/emacs.git
>
> # 4. refresh source/upgrade
> cd $emacs_dir
> git fetch
> git merge
I modified this to 'git pull' as previously suggested. There was
nothing to pull.
> # 5. compile and install
> autogen.sh
> configure --with-x-toolkit=no --with-native-compilation
> make
> sudo make install
Gave this a try. Still having problems:
1. with-x-toolkit=no means no Lucid or GTK -- the process gets much more
complex for dependency if you want a toolkit (I think Lucid is easier
than GTK)
2. autogen.sh and configure need "./" in front of them (you never know
what PATH the user is using).
3. The GNUMakefile in the Emacs distribution seems to rerun configure
with no options, so your "configure" is NO-OP.
4. You can add arguments to the configure in the make step by passing
'configure="--ARG1..."' to make.
5. Even so, after doing everything else you listed and using your
configure options, I got these libraries missing with configure
suggesting how to get around it:
libXpm libjpeg libgif/libungif libtiff gnutls
6. Oops -- missed the build-dep step! Got thru configure and it's
building properly, but it's gonna take awhile... ;)
7. Probably should've tee'd the output of make to a log file... :(
I'm building on a Chromebook with a basic Debian v11.7.
> https://dataswamp.org/~incal/conf/.zsh/install-emacs
> (with functions, recommended)
>
> https://dataswamp.org/~incal/scripts/emacs-install-minimal
> (as a script)
--
David Masterson
next prev parent reply other threads:[~2023-06-04 1:00 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 0:44 Resources for an old newbie ? Frederick Bartlett
2023-05-22 0:50 ` Eduardo Ochs
2023-05-22 1:30 ` Michael Heerdegen
2023-05-22 1:39 ` Michael Heerdegen
2023-05-22 6:33 ` Basile Starynkevitch
2023-05-23 0:11 ` Michael Heerdegen
2023-05-23 5:31 ` Emanuel Berg
2023-05-23 20:19 ` Philip Kaludercic
2023-05-25 0:55 ` Emanuel Berg
2023-05-23 23:09 ` Michael Heerdegen
2023-05-25 1:13 ` Emanuel Berg
2023-05-26 3:28 ` Michael Heerdegen
2023-05-27 5:41 ` Emanuel Berg
2023-05-28 1:50 ` Michael Heerdegen
2023-05-28 21:23 ` Emanuel Berg
2023-05-24 4:25 ` tomas
2023-05-25 1:25 ` Emanuel Berg
2023-05-25 4:01 ` tomas
2023-05-26 1:26 ` David Masterson
2023-05-26 3:36 ` Michael Heerdegen
2023-05-26 4:13 ` Robby Zambito
2023-05-27 4:09 ` David Masterson
2023-05-27 5:29 ` Emanuel Berg
2023-05-29 22:13 ` David Masterson
2023-05-27 5:48 ` Emanuel Berg
2023-05-29 22:14 ` David Masterson
2023-05-27 17:48 ` Robby Zambito
2023-05-29 22:23 ` David Masterson
2023-05-28 2:12 ` Michael Heerdegen
2023-05-28 21:26 ` Emanuel Berg
2023-05-29 22:21 ` David Masterson
2023-05-29 22:52 ` Michael Heerdegen
2023-05-30 2:18 ` Emanuel Berg
2023-06-03 21:40 ` David Masterson
2023-05-30 23:24 ` Emanuel Berg
2023-05-31 3:12 ` Platon Pronko
2023-05-31 3:20 ` Emanuel Berg
2023-05-31 22:07 ` Michael Heerdegen
2023-06-03 21:45 ` David Masterson
2023-06-03 22:03 ` Michael Heerdegen
2023-06-03 22:39 ` David Masterson
2023-06-03 23:19 ` Michael Heerdegen
2023-06-04 1:00 ` David Masterson [this message]
2023-06-04 1:31 ` Emanuel Berg
2023-06-04 2:15 ` Michael Heerdegen
2023-06-04 5:23 ` David Masterson
2023-06-04 2:21 ` Emanuel Berg
2023-06-04 21:05 ` David Masterson
2023-06-06 16:45 ` Emanuel Berg
2023-06-04 3:02 ` Emanuel Berg
2023-06-04 21:01 ` David Masterson
2023-06-04 5:25 ` Eli Zaretskii
2023-06-04 7:08 ` Basile Starynkevitch
2023-06-04 20:35 ` David Masterson
2023-06-04 7:26 ` David Masterson
2023-06-04 7:37 ` Eli Zaretskii
2023-06-04 10:45 ` Emanuel Berg
2023-06-04 20:07 ` David Masterson
2023-06-04 22:12 ` Michael Heerdegen
2023-06-04 22:36 ` David Masterson
2023-06-05 20:34 ` Emanuel Berg
2023-06-05 20:35 ` Emanuel Berg
2023-06-04 10:39 ` Emanuel Berg
2023-06-04 20:23 ` David Masterson
2023-06-05 0:29 ` Michael Heerdegen
2023-06-05 2:22 ` David Masterson
2023-06-05 2:59 ` Michael Heerdegen
2023-06-06 1:19 ` Emanuel Berg
2023-06-06 16:35 ` Emanuel Berg
2023-06-11 3:14 ` Michael Heerdegen
2023-06-11 4:48 ` David Masterson
2023-06-11 6:02 ` Emanuel Berg
2023-06-11 23:33 ` Michael Heerdegen
2023-06-11 23:41 ` Emanuel Berg
2023-06-16 2:22 ` Michael Heerdegen
2023-06-16 2:27 ` Michael Heerdegen
2023-06-11 5:54 ` Emanuel Berg
2023-06-11 23:42 ` Michael Heerdegen
2023-06-11 23:56 ` Emanuel Berg
2023-06-05 20:41 ` Emanuel Berg
2023-06-03 21:33 ` David Masterson
2023-05-26 4:28 ` tomas
2023-05-26 11:34 ` Robert Pluim
2023-05-26 12:06 ` tomas
2023-05-26 14:11 ` Robert Pluim
2023-05-26 21:40 ` Emanuel Berg
2023-06-08 8:39 ` Emanuel Berg
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=SJ0PR03MB5455CCC741F6766D4CD94D44A24CA@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).