From: Wayne Tams <wayne.tams@simpleaudio.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: gst-rtsp not building
Date: Thu, 17 Jan 2013 11:48:10 +0000 [thread overview]
Message-ID: <50F7E4FA.705@simpleaudio.com> (raw)
In-Reply-To: <CAJTo0Lay83xOxnhUAUmb8bS+igk=woeMCboXR+S+VeTHYY61Fg@mail.gmail.com>
On 17/01/13 11:15, Burton, Ross wrote:
> On 17 January 2013 10:18, Wayne Tams <wayne.tams@simpleaudio.com> wrote:
>> DESTDIR=/home/wayne/source/y/yoctoProject/raspberryPiBuild/tmp/work/armv6-vfp-poky-linux-gnueabi/gst-rtsp/0.10.8-r0/image
>> install
>> | make: *** No rule to make target `install'. Stop.
>>
>> Could anyone suggest what could be causing this error and what I could do to
>> fix it.
> To be honest that's probably why that recipe is in a branch (my
> branch) and not in meta-oe...
>
> Do the do_configure and do_build logs actually look like they worked?
> Sometimes "install" will fail because configure failed without an
> error, so build does nothing, and then install actually errors out.
>
> Ross
I did have a recipe but it just wasn't quite right, your branch helped
me there.
You know what the configure was failing, fixed that. Which leads me on to,
ERROR: This autoconf log indicates errors, it looked at host include
and/or library paths while determining system capabilities.
Rerun configure task after fixing this. The path was
'/home/wayne/source/y/yoctoProject/raspberryPiBuild/tmp/work/armv6-vfp-poky-linux-gnueabi/gst-rtsp/0.10.8-r0/gst-rtsp'
ERROR: Function failed: do_qa_configure
perhaps linked to gst-common.inc no longer being available?
Wayne
next prev parent reply other threads:[~2013-01-17 11:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 10:18 gst-rtsp not building Wayne Tams
2013-01-17 11:15 ` Burton, Ross
2013-01-17 11:48 ` Wayne Tams [this message]
2013-01-17 13:45 ` Wayne Tams
2013-01-17 14:04 ` Burton, Ross
2013-01-17 14:26 ` Wayne Tams
2013-01-17 14:37 ` Burton, Ross
2013-01-17 15:00 ` Wayne Tams
2013-01-17 15:20 ` Tomas Frydrych
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=50F7E4FA.705@simpleaudio.com \
--to=wayne.tams@simpleaudio.com \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.