emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Greg Troxel <gdt@ir.bbn.com>
To: emacs-orgmode@gnu.org, Achim Gratz <Stromeko@Stromeko.DE>
Subject: makefile regression
Date: Tue, 22 May 2012 10:43:52 -0400	[thread overview]
Message-ID: <rmimx505l93.fsf@fnord.ir.bbn.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]


For a long time, I've been updating org from git every week or two via:

  update-org () {
      (cd $HOME/SOFTWARE/EMACS/org-mode && git pull && make)
  }

and I have emacs pointed at that directory.   This is on NetBSD where
"make" is BSD make.

Today, I updated again and got:

  make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 6: Need an operator
  make: "/home/gdt/SOFTWARE/EMACS/org-mode/Makefile" line 87: Need an operator
  make: Fatal errors encountered -- cannot continue

  make: stopped in /home/gdt/SOFTWARE/EMACS/org-mode

and it seems recent changes have required beyond-POSIX-make features.

This seems unfortunate; I don't understand why building org has to be so
complicated.  If it is complicated, it seems best to use
autoconf/automake, which already have worked out most of the portability
issues.

At the very least a dependency on GNU make should be documented, if that
is indeed an intentional decision by the community.   (I haven't seen
any discussion, but I confess to not quite keeping up with with
emacs-orgmode traffic.)

Greg


[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]

next             reply	other threads:[~2012-05-22 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 14:43 Greg Troxel [this message]
2012-05-22 16:20 ` makefile regression Bastien
2012-05-24  6:00 ` Achim Gratz
2012-05-24  9:05   ` Bastien
2012-05-24 12:12   ` Greg Troxel
2012-05-24 17:15     ` Achim Gratz
2012-05-25  0:08       ` [PATCH] Add section describing prerequisites Greg Troxel
2012-05-25 22:33         ` Bastien
2012-05-25 23:52           ` Greg Troxel
2012-05-25  0:12       ` makefile regression Greg Troxel
2012-05-25 18:43         ` Achim Gratz

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=rmimx505l93.fsf@fnord.ir.bbn.com \
    --to=gdt@ir.bbn.com \
    --cc=Stromeko@Stromeko.DE \
    --cc=emacs-orgmode@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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).