From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] gstreamer 0.10.x: remove do_configure_prepend
Date: Fri, 30 Mar 2012 14:24:58 +0100 [thread overview]
Message-ID: <1333113898.18082.67.camel@ted> (raw)
In-Reply-To: <4F69E9A1.2080505@windriver.com>
On Wed, 2012-03-21 at 22:45 +0800, Robert Yang wrote:
> Hi Richard,
>
> Please see my comments inline ...
>
> On 03/21/2012 08:36 PM, Richard Purdie wrote:
> > On Wed, 2012-03-21 at 16:38 +0800, Robert Yang wrote:
> >> Remove the do_configure_prepend which is used for removing
> >> ${S}/m4/lib-link.m4 to compile under libtool 2.2.2, but our libtool has
> >> been upgraded to 2.4.2, and:
> >>
> >> for the 3 recipes:
> >> gst-plugins-bad_0.10.22.bb
> >> gst-plugins-base_0.10.35.bb
> >> gst-plugins-good_0.10.30.bb
> >>
> >> They don't have m4/lib-link.m4 any more.
> >>
> >> For the gst-plugins-ugly_0.10.18.bb, though it has m4/lib-link.m4, our
> >> libtool version is now 2.4.2, so we can remove the do_configure_prepend
> >> from all of them.
> >>
> >> [YOCTO #2148]
> >>
> >> Signed-off-by: Robert Yang<liezhi.yang@windriver.com>
> >> ---
> >> .../gstreamer/gst-plugins-bad_0.10.22.bb | 7 +------
> >> .../gstreamer/gst-plugins-base_0.10.35.bb | 7 +------
> >> .../gstreamer/gst-plugins-good_0.10.30.bb | 7 +------
> >> .../gstreamer/gst-plugins-ugly_0.10.18.bb | 7 +------
> >> 4 files changed, 4 insertions(+), 24 deletions(-)
> >
> > Not so easy I'm afraid. We need to ensure our libtool is being used.
> > Even if the version matches, our libtool is patched to ensure the
> > sysroot and rpaths work correctly. I'm therefore a little nervous about
> > removing these at this point.
> >
>
> Yes, I agree with you, though I checked the log.do_configure and log.do_compile,
> it used our libtool. The safe way maybe just remove the
> do_configure_prepend from gst-plugins-bad, gst-plugins-base and
> gst-plugins-good since they don't have the ${S}/m4/lib-link.m4 any more.
>
> For gst-plugins-ugly, we can remove when it would not have ${S}/m4/lib-link.m4.
>
> I noticed this because there was error when build gst-plugins-base/bad/good:
>
> rm: cannot remove `/path/to/m4/lib-link.m4': No such file or directory.
>
> Here is an updated patch and pull request which only removes
> do_configure_prepend for gst-plugins-base/bad/good:
> (I'm not sure whether send a V2 is preferred or not for such case).
>
> git://git.pokylinux.org/poky-contrib robert/gst_v2
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=robert/gst_v2
>
> Subject: [PATCH 1/1] gstreamer 0.10.x: remove do_configure_prepend
>
> Remove the do_configure_prepend which is used for removing
> ${S}/m4/lib-link.m4, but the 3 recipes don't have m4/lib-link.m4 any
> more:
> gst-plugins-bad_0.10.22.bb
> gst-plugins-base_0.10.35.bb
> gst-plugins-good_0.10.30.bb
For what its worth, I just looked at the tarballs for these and the .m4
files are still there in the two I checked. This patch is therefore not
right in its current form.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-30 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 8:38 [PATCH 0/1] gstreamer 0.10.x: remove do_configure_prepend Robert Yang
2012-03-21 8:38 ` [PATCH 1/1] " Robert Yang
2012-03-21 12:36 ` Richard Purdie
2012-03-21 14:45 ` Robert Yang
2012-03-30 13:24 ` Richard Purdie [this message]
2012-03-31 1:21 ` Robert Yang
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=1333113898.18082.67.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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