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 12:04:38 +0100 [thread overview]
Message-ID: <20180205110438.k7osf6ofwf3w6tpr@pengutronix.de> (raw)
In-Reply-To: <CABDcavZ990+KQRL2xBykP8vnpBDP4t8HZwjrSmCH86omef2BWA@mail.gmail.com>
On Mon, Feb 05, 2018 at 11:49:38AM +0100, Guillermo Rodriguez Garcia wrote:
> 2018-02-05 11:25 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > > 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.
> >
>
> OK. configure does not exist in this case.
>
>
> > 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.
> >
>
> Interesting. In my case the ptxversion does not work because intltoolize
> needs to be run as well. But it is good to know this.
ok.
> For packages where the ptxdist version works, shall I just copy the generic
> autogen.sh over to patches/<package>-<version>
Exactly.
> Bonus question. If there are no other patches, ptxdist complains in the
> extract stage saying that the series file was not found (although this does
> not prevent it from continuing to the extract.post stage). Is this ok?
Yes, that's ok. I think we fixed this in later version. I don't see this
warning with ptxdist master.
> 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
> > -------
> >
>
> OK, this is good to know as well. This way I don't need to mess with stage
> rules.
That's the reason why we implemented this. :-)
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
prev parent reply other threads:[~2018-02-05 11:04 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
2018-02-05 10:49 ` Guillermo Rodriguez Garcia
2018-02-05 11:04 ` Michael Olbrich [this message]
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=20180205110438.k7osf6ofwf3w6tpr@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