[intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Sedat Dilek]

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]

[ 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?

Thanks.

Regards,
- Sedat -

P.S.: autoconf version mumbo-jumbo

$ dpkg -S /usr/bin/autoconf
autoconf: /usr/bin/autoconf

$ dpkg -l | grep autoconf
ii  autoconf                                    2.68-1ubuntu2
                             automatic configure script builder

- EOT -

[-- Attachment #2: build-and-install-log_intelddx-2-99-917-580-gf656f6afa288_tearfree-enabled_llvm-3-8-0.txt.gz --]
[-- Type: application/x-gzip, Size: 13732 bytes --]

[-- Attachment #3: config.log.gz --]
[-- Type: application/x-gzip, Size: 14226 bytes --]

[-- Attachment #4: build_xf86-video-intel-with-llvm.sh --]
[-- Type: application/x-sh, Size: 2276 bytes --]

[-- Attachment #5: Type: text/plain, Size: 160 bytes --]

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

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Chris Wilson]

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

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Sedat Dilek]

On Thu, Mar 24, 2016 at 10:54 AM, Chris Wilson <chris@chris-wilson.co.uk> 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 :|

As usual a fast reply - Thanks.

If you have a fix, I will try it.

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

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Sedat Dilek]

[-- Attachment #1: Type: text/plain, Size: 2293 bytes --]

On Thu, Mar 24, 2016 at 10:54 AM, Chris Wilson <chris@chris-wilson.co.uk> 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 :|

[ TRYOUT ]

$ grep ACLOCAL -nr ./
./Makefile.am:21:ACLOCAL_AMFLAGS = $(ACLOCAL_FLAGS) -I m4

I dropped ACLOCAL_FLAG part in Makefile.am (see attached diff) and get...

--- build-and-install-log_intelddx-2-99-917-580-gf656f6afa288_tearfree-enabled_ACLOCAL_FLAGS-dropped_llvm-3-8-0.txt
    2016-03-24 11:13:06.429252959 +0100
+++ build-and-install-log_intelddx-2-99-917-580-gf656f6afa288_tearfree-enabled_llvm-3-8-0.txt
  2016-03-24 10:25:35.913229371 +0100
@@ -1,6 +1,7 @@
 autoreconf: Entering directory `.'
 autoreconf: configure.ac: not using Gettext
-autoreconf: running: aclocal -I m4
+autoreconf: running: aclocal $(ACLOCAL_FLAGS) -I m4
+sh: 1: ACLOCAL_FLAGS: not found
 autoreconf: configure.ac: tracing
 autoreconf: running: libtoolize --install --copy
 libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
@@ -14,6 +15,7 @@ libtoolize: copying file `m4/ltoptions.m
 libtoolize: copying file `m4/ltsugar.m4'
 libtoolize: copying file `m4/ltversion.m4'
 libtoolize: copying file `m4/lt~obsolete.m4'
+sh: 1: ACLOCAL_FLAGS: not found
 autoreconf: running: /usr/bin/autoconf
 autoreconf: running: /usr/bin/autoheader
 autoreconf: running: automake --add-missing --copy --no-force

BTW, my libtool-version is 2.4.2-1ubuntu1.

configure-log is attached.

( In my config.log file I see an error with Clang v3.8.0 - I will send
a separate email. )

- Sedat -

[-- Attachment #2: ACLOCAL_FLAGS.diff --]
[-- Type: text/plain, Size: 398 bytes --]

diff --git a/Makefile.am b/Makefile.am
index c60e8a729271..396f41fdc4df 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -18,7 +18,7 @@
 #  IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
 #  CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
-ACLOCAL_AMFLAGS = $(ACLOCAL_FLAGS) -I m4
+ACLOCAL_AMFLAGS = -I m4
 
 SUBDIRS = man libobj xvmc src tools
 

[-- Attachment #3: configure-log_intelddx-2-99-917-580-gf656f6afa288_tearfree-enabled_ACLOCAL_FLAGS-dropped_llvm-3-8-0.txt --]
[-- Type: text/plain, Size: 13271 bytes --]

autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --install --copy
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:35: installing `./missing'
benchmarks/Makefile.am: installing `./depcomp'
autoreconf: Leaving directory `.'
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... clang
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether clang accepts -g... yes
checking for clang option to accept ISO C89... none needed
checking dependency style of clang... gcc3
checking for clang option to accept ISO C99... none needed
checking how to run the C preprocessor... clang-cpp
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether __clang__ is declared... yes
checking whether __INTEL_COMPILER is declared... no
checking whether __SUNPRO_C is declared... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking if clang supports -Werror=unknown-warning-option... yes
checking if clang supports -Werror=unused-command-line-argument... yes
checking if clang supports -Wall... yes
checking if clang supports -Wpointer-arith... yes
checking if clang supports -Wmissing-declarations... yes
checking if clang supports -Wformat=2... yes
checking if clang supports -Wstrict-prototypes... yes
checking if clang supports -Wmissing-prototypes... yes
checking if clang supports -Wnested-externs... yes
checking if clang supports -Wbad-function-cast... yes
checking if clang supports -Wold-style-definition... yes
checking if clang supports -Wdeclaration-after-statement... yes
checking if clang supports -Wunused... yes
checking if clang supports -Wuninitialized... yes
checking if clang supports -Wshadow... yes
checking if clang supports -Wcast-qual... yes
checking if clang supports -Wmissing-noreturn... yes
checking if clang supports -Wmissing-format-attribute... yes
checking if clang supports -Wredundant-decls... yes
checking if clang supports -Werror=implicit... yes
checking if clang supports -Werror=nonnull... yes
checking if clang supports -Werror=init-self... yes
checking if clang supports -Werror=main... yes
checking if clang supports -Werror=missing-braces... yes
checking if clang supports -Werror=sequence-point... yes
checking if clang supports -Werror=return-type... yes
checking if clang supports -Werror=trigraphs... yes
checking if clang supports -Werror=array-bounds... yes
checking if clang supports -Werror=write-strings... yes
checking if clang supports -Werror=address... yes
checking if clang supports -Werror=int-to-pointer-cast... yes
checking if clang supports -Werror=pointer-to-int-cast... yes
checking if clang supports -pedantic... yes
checking if clang supports -Werror... yes
checking if clang supports -Werror=attributes... yes
checking whether make supports nested variables... yes
checking if clang supports -Wno-cast-qual... yes
checking if clang supports -Wno-redundant-decls... yes
checking if clang supports -Wno-maybe-uninitialized... no
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by clang... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from clang object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if clang supports -fno-rtti -fno-exceptions... yes
checking for clang option to produce PIC... -fPIC -DPIC
checking if clang PIC flag -fPIC -DPIC works... yes
checking if clang static flag -static works... yes
checking if clang supports -c -o file.o... yes
checking if clang supports -c -o file.o... (cached) yes
checking whether the clang linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for strlcpy... no
checking for strlcat... no
checking for strndup... yes
checking for native atomic primitives... Intel
checking for UDEV... yes
checking for sys/stat.h... (cached) yes
checking for X11... yes
X11_CLFAGS= X11_LIBS=-lX11-xcb -lxcb-dri2 -lxcb -lXcomposite -lXdamage -lXrandr -lXext -lXfixes -lXrender -lcairo -lX11 -lpixman-1 -lpng12  
checking sys/ipc.h usability... yes
checking sys/ipc.h presence... yes
checking for sys/ipc.h... yes
checking for sys/ipc.h... (cached) yes
checking for X11/extensions/XShm.h... yes
checking for X11/extensions/shmproto.h... yes
checking for X11/extensions/shmstr.h... yes
checking whether shmctl IPC_RMID allows subsequent attaches... yes
checking for X11_DRI3... yes
checking for IVO_EXTRA... yes
checking for X11/extensions/Xinerama.h... yes
checking for IVO_EXTRA... yes
checking for IVO... no
checking sys/timerfd.h usability... yes
checking sys/timerfd.h presence... yes
checking for sys/timerfd.h... yes
checking for TOOL_CURSOR... yes
checking whether to build additional tools... no
checking if RANDR is defined... yes
checking if RENDER is defined... yes
checking if DPMSExtension is defined... yes
checking for DRM... yes
checking for PCIACCESS... yes
checking dev/wscons/wsconsio.h usability... no
checking dev/wscons/wsconsio.h presence... no
checking for dev/wscons/wsconsio.h... no
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking whether sys/types.h defines makedev... yes
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking for struct sysinfo.totalram... yes
checking for DRMINTEL... yes
checking for XORG... yes
checking vgaHW.h usability... yes
checking vgaHW.h presence... yes
checking for vgaHW.h... yes
checking xaa.h usability... no
checking xaa.h presence... no
checking for xaa.h... no
checking whether to include XAA support... no
checking for dgaproc.h... yes
checking whether to include DGA support... yes
checking if XF86DRI is defined... yes
checking whether to include DRI1 support... no
checking for DRI2... yes
checking for dri2.h... yes
checking whether to include DRI2 support... auto
checking whether to include DRI3 support... no
checking default DRI support... 
checking X11/extensions/dpmsconst.h usability... yes
checking X11/extensions/dpmsconst.h presence... yes
checking for X11/extensions/dpmsconst.h... yes
checking if PRESENT is defined... no
checking whether to include PRESENT support... no
checking whether to include UXA support... yes
checking whether to include SNA support... auto
checking for XVMCLIB... yes
checking whether to include XvMC support... yes
checking which acceleration method to use by default... sna
checking for library containing clock_gettime... -lrt
checking for VALGRIND... yes
checking whether to include valgrind support... yes (auto)
checking for getline... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating man/Makefile
config.status: creating libobj/Makefile
config.status: creating src/Makefile
config.status: creating src/legacy/Makefile
config.status: creating src/legacy/i810/Makefile
config.status: creating src/legacy/i810/xvmc/Makefile
config.status: creating src/render_program/Makefile
config.status: creating src/sna/Makefile
config.status: creating src/sna/brw/Makefile
config.status: creating src/sna/fb/Makefile
config.status: creating src/uxa/Makefile
config.status: creating xvmc/Makefile
config.status: creating xvmc/shader/Makefile
config.status: creating xvmc/shader/mc/Makefile
config.status: creating xvmc/shader/vld/Makefile
config.status: creating test/Makefile
config.status: creating benchmarks/Makefile
config.status: creating tools/Makefile
config.status: creating tools/org.x.xf86-video-intel.backlight-helper.policy
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands


xf86-video-intel
Open-source X.org graphics driver for Intel graphics
https://01.org/linuxgraphics/

What is xf86-video-intel
------------------------
The xf86-video-intel module is an open-source 2D graphics driver for
the X Window System as implemented by X.org. It supports a variety of
Intel graphics chipsets including:

	i810/i810e/i810-dc100,i815,
	i830M,845G,852GM,855GM,865G,
	915G/GM,945G/GM/GME,946GZ
	G/GM/GME/Q965,
	G/Q33,G/Q35,G41,G/Q43,G/GM/Q45
	PineView-M (Atom N400 series)
	PineView-D (Atom D400/D500 series)
	Intel(R) HD Graphics: 2000-6000,
	Intel(R) Iris(TM) Graphics: 5100/6100, and
	Intel(R) Iris(TM) Pro Graphics: 5200/6200/P6300.

Where to get more information about the driver
----------------------------------------------
The primary source of information about this and other open-source
drivers for Intel graphics is:

	https://01.org/linuxgraphics/

Documentation specific to the xf86-video-intel driver including
possible configuration options for the xorg.conf file can be found in
the intel(4) manual page. After installing the driver this
documentation can be read with the following command:

	man intel

Mailing list for communication with users and developers of
xf86-video-intel:

	intel-gfx@lists.freedesktop.org

	Note: Subscription is required before posting, but anyone is
	free to subscribe. See instructions (and archives) here:

	http://lists.freedesktop.org/mailman/listinfo/intel-gfx

To report bugs encountered with the driver, see:

	https://01.org/linuxgraphics/documentation/how-report-bugs

To see bugs that are targeted to be fixed in the next release:

	https://bugs.freedesktop.org/show_bug.cgi?id=intel-2d-release

xf86-video-intel 2.99.917 will be compiled with:
  Xorg Video ABI version: 15.0 (xorg-server-1.15.1)
  pixman version: pixman-1-0.30.2
  Acceleration backends: none *sna uxa
  Additional debugging support? valgrind
  Support for Kernel Mode Setting? yes
  Support for legacy User Mode Setting (for i810)? yes
  Support for Direct Rendering Infrastructure: *DRI2
  Support for Xv motion compensation (XvMC and libXvMC): yes
  Support for display hotplug notifications (udev): yes
  Build additional tools and utilities? xf86-video-intel-backlight-helper
  Experimental support: TearFree


[-- Attachment #4: Type: text/plain, Size: 160 bytes --]

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

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Dave Gordon]

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

Try prefixing your top-level building command (make, or ./configure, or 
whatever) with the assignment ACLOCAL_FLAGS= thus:

$ ACLOCAL_FLAGS= make

Note the space after the equal-sign; this sets ACLOCAL_FLAGS to the null 
string in the environment of the "make" command (only).

To get more information on what aclocal is doing, consider

$ ACLOCAL_FLAGS='--verbose' make

If those don't help, check where aclocal is being invoked and see 
whether it should read "aclocal ${ACLOCAL_FLAGS}" with *braces* rather 
than parentheses!

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

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Chris Wilson]

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

-- 
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Dave Gordon]

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

Re: [intelddx] v2.99.917-580-gf656f6afa288: sh: 1: ACLOCAL_FLAGS: not found

[Sedat Dilek]

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

On Thu, Mar 31, 2016 at 12:36 PM, Dave Gordon <david.s.gordon@intel.com> wrote:
> 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.
>

How do I do that?
( My build-script is attached. )

- Sedat -

[-- Attachment #2: build_xf86-video-intel-with-llvm.sh --]
[-- Type: application/x-sh, Size: 2277 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

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