From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with autoreconf mesa3d
Date: Fri, 07 Mar 2014 10:11:13 +0000 [thread overview]
Message-ID: <53199B41.5050509@carallon.com> (raw)
Hello,
I am seeing a build error whilst building mesa3d in 2014.02. The error
occurs when autoreconf rebuilds the configure file.
In configure.ac there is the following to determine the version of mes3d:
m4_define([mesa_version],
[m4_esyscmd([${MAKE-make} -s -f bin/version.mk version | tr -d '\n'
| tr -d '\r'])])
The output of this should be "7.10.3"
My problem is that I have a wrapper Makefile that calls buildroot. This
then means that when autoreconf is called make will print out the
directory like "make: Entering directory `/foo/bar/mesa3d'."
So what I get is version being defined as
"make: Entering directory `/foo/bar/mesa3d'.7.10.3make: Leaving
directory `/foo/bar/mesa3d'."
It easy for me to fix because I can use --no-print-directory when
invoking buildroot from my wrapper makefile but it feels like this is an
issue with mesa3d.
This feels like a poorly written configure.ac file. Would people agree?
Is it worth patching it to prevent this? I know people are working on
bumping the version of mesa so perhaps this would just go away with that?
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7471 9224
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2014-03-07 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:11 Will Wagner [this message]
2014-03-08 9:11 ` [Buildroot] Problem with autoreconf mesa3d Bernd Kuhls
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=53199B41.5050509@carallon.com \
--to=will_wagner@carallon.com \
--cc=buildroot@busybox.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.
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.