From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Jiri B <jirib@devio.us>
Cc: bug-grub@gnu.org, The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [openbsd] 2.02-beta3: build fails - getroot.c:(.text+0x2b): undefined reference to `getrawpartition'
Date: Thu, 24 Mar 2016 06:55:09 +0300 [thread overview]
Message-ID: <56F3651D.40209@gmail.com> (raw)
In-Reply-To: <20160314181957.GV17281@wolfman.devio.us>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
14.03.2016 21:19, Jiri B пишет:
>
>>>>> Another thing - 'INSTALL' file says >= autoconf 2.60 is needed but
>>>>> it is >= 2.62 otherwise there is:
>>>>>
>>>>> "error: possibly undefined macro: AS_ECHO"
>>>>>
>>>>
>>>> Indeed. According to git log, AS_ECHO appeared first in 2.61a. What
>>>> version you have?
>>>
>>> IIUC it was firstly available in "normal" autoconf release in 2.62.
>>>
>>
>> This does not answer my question - what autoconf version your system
>> ships with (i.e. - do we need to change configure.ac or simply update
>> INSTALL)?
>
> IMO it would be ok to update INSTALL file. I had following autoconf
> versions:
>
> autoconf-2.13p3
> autoconf-2.52p5
> autoconf-2.59p4
> autoconf-2.60p4
> autoconf-2.61p4
> autoconf-2.62p1
> autoconf-2.63p0
> autoconf-2.65p0
> autoconf-2.67p0
> autoconf-2.68p0
> autoconf-2.69p1
>
It is silly to bump version requirement in this case where AS_ECHO is
not really needed. Could you retest attached patch with 2.60?
[-- Attachment #2: no-as_echo.patch --]
[-- Type: text/x-patch, Size: 966 bytes --]
From: Andrei Borzenkov <arvidjaar@gmail.com>
Subject: [PATCH] configure: replace AS_ECHO with echo in program transform
INSTALL requires autoconf 2.60, but AS_ECHO appeared first in 2.61a. It is
used just once to transform program names; in this case arguments are known
plain string so simple `echo' is safe to use. This avoids bumping required
autoconf version without real reason.
Reported by: Jiri B <jirib@devio.us>
---
acinclude.m4 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/acinclude.m4 b/acinclude.m4
index 526f97a..e659b1e 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -421,5 +421,5 @@ else
dnl Create an output variable with the transformed name of a GRUB utility
dnl program.
AC_DEFUN([grub_TRANSFORM],[dnl
-AC_SUBST(AS_TR_SH([$1]), [`AS_ECHO([$1]) | sed "$program_transform_name"`])dnl
+AC_SUBST(AS_TR_SH([$1]), [`echo [$1] | sed "$program_transform_name"`])dnl
])
--
tg: (f4d35d4..) u/no_as_echo (depends on: master)
prev parent reply other threads:[~2016-03-24 3:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160312165742.GR17281@wolfman.devio.us>
2016-03-12 18:29 ` [openbsd] 2.02-beta3: build fails - getroot.c:(.text+0x2b): undefined reference to `getrawpartition' Andrei Borzenkov
2016-03-12 19:54 ` Jiri B
2016-03-13 5:41 ` Andrei Borzenkov
2016-03-14 18:19 ` Jiri B
2016-03-14 18:46 ` Andrei Borzenkov
2016-03-17 10:12 ` Jiri B
2016-03-17 15:54 ` Andrei Borzenkov
2016-03-17 16:04 ` Vladimir 'phcoder' Serbinenko
2016-03-17 16:07 ` Andrei Borzenkov
2016-03-17 20:56 ` Jiri B
2016-03-18 3:26 ` Andrei Borzenkov
2016-03-18 13:01 ` Jiri B
2016-03-18 16:53 ` Andrei Borzenkov
2016-03-18 19:48 ` Vladimir 'phcoder' Serbinenko
2016-03-22 10:31 ` Jiri B
2016-03-22 17:48 ` Andrei Borzenkov
2016-03-24 3:55 ` Andrei Borzenkov [this message]
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=56F3651D.40209@gmail.com \
--to=arvidjaar@gmail.com \
--cc=bug-grub@gnu.org \
--cc=grub-devel@gnu.org \
--cc=jirib@devio.us \
/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 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.