mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] minicoredumper: New package
Date: Wed, 15 Aug 2018 12:03:32 +0200	[thread overview]
Message-ID: <20180815100332.biujtqgdzcr3qyxx@pengutronix.de> (raw)
In-Reply-To: <1534250317.10108.19.camel@diehl.com>

On Tue, Aug 14, 2018 at 12:38:38PM +0000, Denis OSTERLAND wrote:
> Am Dienstag, den 14.08.2018, 13:02 +0200 schrieb Uwe Kleine-König:
> > On Tue, Aug 14, 2018 at 12:14:20PM +0200, Roland Hieber wrote:
> > > On Tue, Aug 14, 2018 at 11:57:44AM +0200, Roland Hieber wrote:
> > > > On Mon, Aug 13, 2018 at 04:57:48PM +0200, Uwe Kleine-König wrote:
> > > > > +$(STATEDIR)/minicoredumper.extract: $(STATEDIR)/autogen-tools
> > > > Interesting, I didn't know this one yet. Apparently it generates a
> > > > configure script when only a configure.ac is present?
> > > Hm. On second read of ptxdist/rules/pre/autogen.make, this should be a
> > > no-op as long as no patches/$(MINICOREDUMPER)/autogen.sh is present,
> > > which is the case here. Does it work for you as intended?
> > Yes, works as intended (i.e. the package builds fine) :-)
> > 
> > I used that not because I consider it sensible but because that's what
> > ptxdist newpackage did for me.
> > 
> > Best regards
> > Uwe
> 
> I would expect a link in patch folder instead of prepare section:
> patches/minicoredumper-2.0.1/autogen.sh -> ../autogen.sh

Yes, that is the usual way to do it, the extract.post stage will find
patches/minicoredumper-2.0.1/autogen.sh and execute it in the package
directory to generate configure from configure.ac.

In this case, configure was already present in the tarball, so nothing
of these solutions were needed.

 - Roland


-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-08-15 10:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 14:57 Uwe Kleine-König
2018-08-14  9:57 ` Roland Hieber
2018-08-14 10:14   ` Roland Hieber
2018-08-14 11:02     ` Uwe Kleine-König
2018-08-14 12:38       ` Denis OSTERLAND
2018-08-15 10:03         ` Roland Hieber [this message]
2018-08-14 16:15 ` [ptxdist] [PATCH v2] " Uwe Kleine-König
2018-08-15  9:59   ` Roland Hieber
2018-08-29  7:31   ` Alexander Dahl
2018-08-31  7:41   ` Michael Olbrich

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=20180815100332.biujtqgdzcr3qyxx@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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