unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Fix compiling on CentOS 7.
Date: Sat, 27 Aug 2016 02:16:47 +0200	[thread overview]
Message-ID: <878tvjxdzk.fsf@gnu.org> (raw)
In-Reply-To: <878tvjglfw.fsf@we.make.ritual.n0.is>


ng0 writes:

> Roel Janssen <roel@gnu.org> writes:
>
>> From dcbf57e6b7e6798a321d599390a052953ab3a75a Mon Sep 17 00:00:00 2001
>> From: Roel Janssen <roel@gnu.org>
>> Date: Fri, 26 Aug 2016 15:22:00 -0400
>> Subject: [PATCH] Changes to compile it on Centos 7.
>>
>> ---
>>  doc/local.mk   |   84 +--
>>  emacs/local.mk |   74 +--
>>  gnu/local.mk   | 1712 ++++++++++++++++++++++++++++----------------------------
>>  nix/local.mk   |  134 ++---
>>  4 files changed, 1002 insertions(+), 1002 deletions(-)
>
> ...
>
>> Dear Guix,
>>
>> Due to an old Automake version (1.13), running the `./configure' phase on
>> CentOS 7 fails with:
>>
>>> autoreconf: running: automake --add-missing --copy --force-missing
>>> configure.ac:21: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
>>> configure.ac:21: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
>>> configure.ac:21: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
>>> Makefile.am:422: warning: AM_GNU_GETTEXT used but 'po' not in SUBDIRS
>>> automake: error: cannot open < ./%D%/guix.texi: No such file or directory
>>> autoreconf: automake failed with exit status: 1
>>
>> (It does not replace %D% with the appropriate directory..)
>>
>> The attached patch replaces each instance of %D%, which I believe stands
>> for the current subdirectory from the project root, with the appropriate
>> directory.  With these changes, I've been able to compile GNU Guix on
>> CentOS 7.
>>
>> I am not sure how this change impacts custom configure options, so I
>> would like to ask someone with more Automake knowledge and experience to
>> elaborate on the possible downsides of applying this patch.
>>
>> If this change is acceptable to the project, I will update the commit
>> message to a more detailed and conforming message.  Suggestions are
>> welcome here though.
>>
>> What do you think about making Guix compilable on this "stable"
>> distribution? :-)
>>
>> Thanks!
>>
>> Kind regards,
>> Roel Janssen
>
> On the one hand it's nice to have Guix run everywhere, on the other hand
> why is CentOS using this old automake? Can't this be fixed in another
> way in CentOS itself, or is CentOS stable like Debian stable with their
> release and update cycles? My debian has 1.14.1 automake.

Thanks for your quick response.

Yes, CentOS is just like Red Hat Enterprise Linux (in fact, they are
almost identical distributions), and RHEL has support for up to 10 years
on major releases!  I don't think we can convince Red Hat that they need
to upgrade Automake on RHEL 7, so that CentOS 7 gets an updated Automake.

The patch is actually quite simple (I used four replace-all actions) and
I don't think it negatively impacts the building (but I'm no expert on
custom configuration stuff).  I think it's good for GNU Guix to support
older versions when the cost is low (which is the case here).

Kind regards,
Roel Janssen

  reply	other threads:[~2016-08-27  0:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 19:48 [PATCH] Fix compiling on CentOS 7 Roel Janssen
2016-08-26 23:27 ` ng0
2016-08-27  0:16   ` Roel Janssen [this message]
2016-08-27  6:14 ` Ricardo Wurmus
2016-08-27  6:57 ` Tomáš Čech
2016-08-27  8:39   ` Alex Kost
2016-08-27  8:51     ` Roel Janssen
2016-08-27 10:28       ` Florian Paul Schmidt
2016-08-27 23:33         ` Roel Janssen
2016-08-28  8:11           ` Tomáš Čech
2016-08-28  9:34             ` Efraim Flashner
2016-08-28  9:53               ` Tomáš Čech
2016-08-28 14:13                 ` Roel Janssen
2016-08-28 14:42                   ` Mathieu Lirzin
2016-08-27 13:06       ` Mathieu Lirzin
2016-08-28 20:11       ` Ludovic Courtès
2016-08-28 20:32         ` Roel Janssen
2016-08-29 12:51           ` Ludovic Courtès

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=878tvjxdzk.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.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).