From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com,
qemu-devel@nongnu.org, aliguori@us.ibm.com
Subject: Re: [Qemu-devel] [PATCH v5 0/3] DTC as submodule
Date: Thu, 18 Apr 2013 13:08:54 +0200 [thread overview]
Message-ID: <20130418110854.GH4915@smtp.vpn> (raw)
In-Reply-To: <516FD2D1.1060403@redhat.com>
On Thu, Apr 18, 2013 at 01:02:41PM +0200, Paolo Bonzini wrote:
> Il 18/04/2013 12:26, Edgar E. Iglesias ha scritto:
> > On Thu, Apr 18, 2013 at 02:45:35PM +1000, peter.crosthwaite@xilinx.com wrote:
> >> From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> >>
> >> These two patches add and use dtc as a submodule as per the RFC:
> >>
> >> http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg05000.html
> >>
> >> There is a remaining action item to mandate libfdt for arm/microblaze and PPC
> >> which is left as follow up work for after review of this series.
> >>
> >> Also fixed the configure to properly build pixman when cross compiling.
> >>
> >> changed since v4:
> >> Use error_exit in configure
> >> changed since v3:
> >> Rebase against recent configure devls.
> >> changed since v2:
> >> Fixed P1 implementation (PMM review)
> >> Fixed CC/AR/LD quoting issue P3 (PMM review)
> >> Addressed PMM review
> >> changed since v1:
> >> Fixed cross compilation of submodules (new P1)
> >> Fixed passing of ARFLAGS to dtc submake
> >
> >
> >
> > Acked-by: Edgar E. Iglesias <edgar.iglesias@gmail.com>
>
> Great, please apply!
>
> > CC: Anthony and Bonzini
> >
> > Shouldn't we in scripts/make_release have a stage that walks the submodules
> > and makes sure to bootstrap autoconf so that we package release-tarballs
> > with pre-generated configure scripts?
> > IIUC, that is standard practice for autoconf tarball releases but I might
> > be wrong.
>
> It depends. Some autoconfiscated packages put autoconf-generated
> scripts in the repository. In this case, there is no need to regenerate
> the files when brewing the release. Others leave out all such files
> (including for example Bison-generated parsers); in this case of course
> you need to include the scripts in the tarball, the user is not supposed
> to run autoconf himself.
OK, thanks.
>
> For submodules that do have autoconf-generated scripts in the repository
> (I think both of them do, in our case), we should trust upstream's
> configure script. That's what everyone has been testing the git
> repository with.
I downloaded the qemu-1.4.1 release and looked at the pixman subdir. It
doesnt come with a generated configure script, but has a autogen.sh script to
run autoconf itself. My understanding was that, like you say, the user
shouldn't need to run autoconf to generate configure, it should have been
provided. Am I missing something?
Best regards,
Edgar
next prev parent reply other threads:[~2013-04-18 11:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 4:45 [Qemu-devel] [PATCH v5 0/3] DTC as submodule peter.crosthwaite
2013-04-18 4:46 ` [Qemu-devel] [PATCH v5 1/3] configure: Put cross compile flags in EXTRA_CFLAGS peter.crosthwaite
2013-04-18 4:46 ` [Qemu-devel] [PATCH v5 2/3] dtc: add submodule peter.crosthwaite
2013-04-18 4:47 ` [Qemu-devel] [PATCH v5 3/3] configure/Make: Build libfdt from submodule DTC peter.crosthwaite
2013-04-20 18:42 ` Blue Swirl
2013-04-21 13:16 ` Paolo Bonzini
2013-04-22 4:45 ` Peter Crosthwaite
2013-04-22 8:58 ` Paolo Bonzini
2013-05-24 14:16 ` Peter Maydell
2013-05-24 14:33 ` Edgar E. Iglesias
2013-05-24 14:34 ` Peter Maydell
2013-04-18 10:26 ` [Qemu-devel] [PATCH v5 0/3] DTC as submodule Edgar E. Iglesias
2013-04-18 11:02 ` Paolo Bonzini
2013-04-18 11:08 ` Edgar E. Iglesias [this message]
2013-04-18 11:10 ` Peter Maydell
2013-04-18 11:58 ` Edgar E. Iglesias
2013-04-18 11:12 ` Paolo Bonzini
2013-04-18 11:56 ` Edgar E. Iglesias
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=20130418110854.GH4915@smtp.vpn \
--to=edgar.iglesias@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).