From: Eryu Guan <eguan@redhat.com>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v3] Code to allow cros-compilation on chromeOS
Date: Mon, 10 Apr 2017 17:25:28 +0800 [thread overview]
Message-ID: <20170410092528.GE22845@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAMHSBOVYcqdByoCvtow5agrBE+f39M6zTsg1CHGift2d13tgcg@mail.gmail.com>
On Fri, Apr 07, 2017 at 02:41:59PM -0700, Gwendal Grignou wrote:
> Reading stack overflow further, the fact AC_PACKAGE_GLOBALS and
> AC_PACKAGE_UTILITIES are not defined are just the consequence of the
> error.
> When all work fine, the autoconfigued ./aclocal.m4 should contains
> several m4_include and in particular
> m4_include([m4/package_globals.m4])" that will load the definitions
> for these macros.
> I am shooting in the dark, how ./aclocal.m4 compares between RH7.0 and RH6.9?
RHEL6.9:
https://paste.fedoraproject.org/paste/EUo-NKzoZPwbIIhn1bjoJF5M1UNdIGYhyRLivL9gydE=
RHEL7.3:
https://paste.fedoraproject.org/paste/SEhryYO0GXT8VIA0-24q8V5M1UNdIGYhyRLivL9gydE=
> What are the revisions of automake, autoconf, m4 andlibtoolize.
[root@eguan-rhel6 xfstests]# rpm -q automake autoconf m4 libtool
automake-1.11.1-4.el6.noarch
autoconf-2.63-5.1.el6.noarch
m4-1.4.13-5.el6.x86_64
libtool-2.2.6-15.5.el6.x86_64
[root@dhcp-66-87-213 xfstests]# rpm -q automake autoconf m4 libtool
automake-1.13.4-3.el7.noarch
autoconf-2.69-11.el7.noarch
m4-1.4.16-10.el7.x86_64
libtool-2.4.2-21.el7_2.x86_64
> Does autoreconf -fi help?
No, autoreconf -fi has the same issue.
>
> Thanks for your help,
> Gwendal.
Thank you!
Eryu
next prev parent reply other threads:[~2017-04-10 9:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMHSBOXjP4QOGmM2HxygY0r+ML93XyEmLEfwGz6KvS0S0sjuCA@mail.gmail.com>
2017-03-24 23:48 ` [PATCH v2] Code to allow cros-compilation on chromeOS Gwendal Grignou
2017-03-27 11:35 ` Eryu Guan
2017-04-04 17:37 ` [PATCH v3] " Gwendal Grignou
2017-04-06 11:18 ` Eryu Guan
2017-04-06 23:26 ` Gwendal Grignou
2017-04-07 4:12 ` Eryu Guan
2017-04-07 21:41 ` Gwendal Grignou
2017-04-10 9:25 ` Eryu Guan [this message]
2017-04-19 21:59 ` Gwendal Grignou
2017-04-19 23:33 ` [PATCH v4] " Gwendal Grignou
2017-04-25 13:09 ` Eryu Guan
2017-05-08 10:19 ` Xiao Yang
2017-05-08 10:50 ` Eryu Guan
2017-05-08 11:19 ` Xiao Yang
2017-05-08 21:22 ` Gwendal Grignou
2017-05-09 1:37 ` Xiao Yang
2017-05-09 7:12 ` Xiao Yang
2017-05-12 6:04 ` Xiao Yang
2017-05-12 8:12 ` Eryu Guan
2017-04-28 16:27 ` [PATCH v5] " Gwendal Grignou
2017-04-28 16:58 ` Gwendal Grignou
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=20170410092528.GE22845@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=gwendal@chromium.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 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.