all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: new package build error: archiver requires 'AM_PROG_AR' in 'configure.ac'
Date: Thu, 1 Sep 2016 09:07:27 +0200	[thread overview]
Message-ID: <57C7D3AF.7070800@goebel-consult.de> (raw)
In-Reply-To: <874m60btxq.fsf@elephly.net>


[-- Attachment #1.1: Type: text/plain, Size: 804 bytes --]

Am 31.08.2016 um 21:49 schrieb Ricardo Wurmus:
> I have never seen this before.  Have you tried patching “configure.ac”
> as it says, adding “AM_PROG_AR” somewhere?

For now I worked around this issue by adding this line near the top of
the confiure.ac:

m4_ifdef([AM_PROG_AR], [AM_PROG_AR])


This is what I've found when searching the internet for an solution.

-- 
Schönen Gruß
Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog:
http://www.goebel-consult.de/blog/vortrag-digitalen-selbstverteidigung-fur-unternehmen

Kolumne: http://www.cissp-gefluester.de/2011-11-in-troja-nichts-neues


[-- Attachment #1.2: Type: text/html, Size: 1972 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2430 bytes --]

  parent reply	other threads:[~2016-09-01  7:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 19:08 new package build error: archiver requires 'AM_PROG_AR' in 'configure.ac' Hartmut Goebel
2016-08-31 19:49 ` Ricardo Wurmus
2016-08-31 19:56   ` David Craven
2016-09-01  7:07     ` Hartmut Goebel
2016-09-01  7:07   ` Hartmut Goebel [this message]
2016-09-01 11:44 ` Ludovic Courtès
2016-09-01 12:46   ` Hartmut Goebel

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

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

  git send-email \
    --in-reply-to=57C7D3AF.7070800@goebel-consult.de \
    --to=h.goebel@goebel-consult.de \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.