public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found
Date: Thu, 31 Mar 2016 11:36:40 +0100	[thread overview]
Message-ID: <56FCFDB8.4030203@intel.com> (raw)
In-Reply-To: <20160324124714.GI27742@nuc-i3427.alporthouse.com>

On 24/03/16 12:47, Chris Wilson wrote:
> On Thu, Mar 24, 2016 at 12:29:32PM +0000, Dave Gordon wrote:
>> On 24/03/16 09:54, Chris Wilson wrote:
>>> On Thu, Mar 24, 2016 at 10:34:58AM +0100, Sedat Dilek wrote:
>>>> [ build-script, build and config logs attached ]
>>>>
>>>> Hi Chris,
>>>>
>>>> I am just seeing this (or noticed for the first time, here on
>>>> Ubuntu/precise AMD64)...
>>>>
>>>> $ zgrep -A1 -B1 ACLOCAL_FLAGS:
>>>> build-and-install-log_intelddx-2-99-917-580-gf656f6afa288_tearfree-enabled_llvm-3-8-0.txt.gz
>>>> autoreconf: running: aclocal $(ACLOCAL_FLAGS) -I m4
>>>> sh: 1: ACLOCAL_FLAGS: not found
>>>> autoreconf: configure.ac: tracing
>>>> --
>>>> libtoolize: copying file `m4/lt~obsolete.m4'
>>>> sh: 1: ACLOCAL_FLAGS: not found
>>>> autoreconf: running: /usr/bin/autoconf
>>>>
>>>> What does this mean and it is ignore-able?
>>>
>>> libtool vs automake. Haven't found the right fix yet.
>>>
>>> If you want to locally patch s/$(ACLOCAL_FLAGS)// that'll do the trick.
>>> I think that's what we'll have to do :|
>>> -Chris
>>
>> Is this a confusion between an (undefined) Make-variable vs a shell
>> variable? The syntax above with parentheses $(VAR) would be right
>> for expanding a Make-variable, but it looks like it's being passed
>> as-is to the shell, which interprets it as command-substitution and
>> tries to run the (non-existent) *command* ACLOCAL_FLAGS
>
> Yes. The issue is that recently libtool spits out
> an obtuse error if it sees ${ACLOCAL_FLAGS} in ACLOCAL_AMFLAGS
>
> libtoolize:   error: AC_CONFIG_MACRO_DIRS([m4]) conflicts with ACLOCAL_AMFLAGS=-I /opt/xorg/share/aclocal.
> autoreconf: libtoolize failed with exit status: 1
>
> i.e. it misses that we both include the user aclocal directory as well
> as our own -I m4.
>
> So I tried using it as a make variable instead, but then it is evaluated
> as the shell $() command!
> -Chris

Perhaps try setting AC_CONFIG_MACRO_DIRS to [/opt/xorg/share/aclocal, 
m4] instead, and not use ACLOCAL_AMFLAGS? Or at least not to extend the 
include path.

.Dave.

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-03-31 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  9:34 [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found Sedat Dilek
2016-03-24  9:54 ` Chris Wilson
2016-03-24 10:01   ` Sedat Dilek
2016-03-24 10:20   ` Sedat Dilek
2016-03-24 12:29   ` Dave Gordon
2016-03-24 12:47     ` Chris Wilson
2016-03-31 10:36       ` Dave Gordon [this message]
2016-04-02  5:52         ` Sedat Dilek

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=56FCFDB8.4030203@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sedat.dilek@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox