mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] mediastreamer2: Bad search path when relinking library
Date: Mon, 5 Feb 2018 11:25:24 +0100	[thread overview]
Message-ID: <20180205102524.ts3vrgfl4c5tqoko@pengutronix.de> (raw)
In-Reply-To: <CABDcavbY7z=KVVT-cyW_MD1pAAip8EjzphumsYuH1QEP5p1N_A@mail.gmail.com>

On Mon, Feb 05, 2018 at 11:05:40AM +0100, Guillermo Rodriguez Garcia wrote:
> Hi,
> 
> 2018-02-02 16:46 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> 
> > Hi,
> >
> > On Fri, Feb 02, 2018 at 11:59:03AM +0100, Guillermo Rodriguez Garcia wrote:
> > > I am trying to create a ptxdist package for mediastreamer2. By default,
> > > releases come without a configure script, and with an autogen.sh that
> > > requires intltoolize.
> > >
> > > So I first tried the following:
> > >
> > > In mediastreamer2.in:
> > >
> > > select HOST_INTLTOOL
> > >
> > > In mediasteamer2.make:
> > >
> > > $(STATEDIR)/mediastreamer2.extract:
> > > @$(call targetinfo)
> > > @$(call clean, $(MEDIASTREAMER2_DIR))
> > > @$(call extract, MEDIASTREAMER2)
> > > cd $(MEDIASTREAMER2_DIR) && [ -f configure ] || sh autogen.sh
> > > @$(call patchin, MEDIASTREAMER2)
> > > @$(call touch)
> > >
> > > However, this does not work because apparently ptxdist resolves
> > > dependencies after the extract stage, so when autogen.sh is run, the
> > > host-intltool package has not been installed yet.
> > >
> > > So I tried to run autogen.sh from the extract.post stage instead:
> > >
> > > $(STATEDIR)/mediastreamer2.extract.post:
> > > @$(call targetinfo)
> > > cd $(MEDIASTREAMER2_DIR) && [ -f configure ] || sh autogen.sh
> >
> > I'm guessing you got that from the latest src-autoconf template. This is
> > still broken. It's missing the actual extract.post command:
> >
> 
> No, I actually made that up myself, based on the documentation. The manual
> mentions [1] that extract.post is a good place to "generate a configure
> script out of an autotoolized configure.ac file for example", so that's
> what I tried. Also the manual does not document any default rule when
> extract.post is omitted (whereas it does so for other stages). So I didn't
> know that I had to call world/patchin/post from my custom extract.post rule.

Ok. That needs to be fixed in the documentation.

> >
> >          @$(call world/patchin/post, @PACKAGE@)
> >
> > > @$(call touch)
> > >
> > > This way, host-intltool is installed before autogen.sh is run, so that
> > part
> > > work. But this creates other problems: The install stage fails when
> > trying
> > > to relink some libraries.
> > >
> > > What is the proper way to do this?
> >
> > The template whre you got this from is for packages where the source is
> > part of your BSP. I don't think this is the case for mediasteamer2. You
> > should use the 'target' new-package template.
> >
> > For most packages the tarball contains the configure script. In that case
> > nothing special need to happen. If the configure script is missing, then
> > you need to create a autogen.sh link.
> > e.g. like the libyaml package in PTXdist does this with
> > patches/libyaml-0.1.7/autogen.sh.
> >
> 
> Actually the mediastreamer2 package comes with its own autogen.sh script.
> That's why I am running
> 
> cd $(MEDIASTREAMER2_DIR) && [ -f configure ] || sh autogen.sh
> 
> Is that correct? I guess that if there's an autogen.sh script in the
> package, that should normally be used in preference to the generic ptxdist
> version. Right?

Not quite.
1. If the configure exists, then don't call any autogen.sh unless configure
   was not generated properly.
2. unless you have the source in local_src/ provide
   patches/<package>-<version>/autogen.sh
3. If the autogen.sh from ptxdist works, then use it. The local autogen.sh
   scipts in the packages often do other random stuff, such as calling
   'configure' and the one in ptxdist does the right thing in most cases.
4. If you need to use the package specific autogen.sh, the
   patches/<package>-<version>/autogen.sh should look like this:
-------
#!/bin/sh
exec ./autogen,sh
-------

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-02-05 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 10:59 Guillermo Rodriguez Garcia
2018-02-02 15:46 ` Michael Olbrich
2018-02-05 10:05   ` Guillermo Rodriguez Garcia
2018-02-05 10:25     ` Michael Olbrich [this message]
2018-02-05 10:49       ` Guillermo Rodriguez Garcia
2018-02-05 11:04         ` 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=20180205102524.ts3vrgfl4c5tqoko@pengutronix.de \
    --to=m.olbrich@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