[yocto] [PATCH][meta-selinux] systemd: fix dependencies for audit, selinux

2014-12-03 Thread wenzong.fan 
From: Wenzong Fan 

Signed-off-by: Wenzong Fan 
---
 recipes-core/systemd/systemd_%.bbappend |2 ++
 1 file changed, 2 insertions(+)
 create mode 100644 recipes-core/systemd/systemd_%.bbappend

diff --git a/recipes-core/systemd/systemd_%.bbappend 
b/recipes-core/systemd/systemd_%.bbappend
new file mode 100644
index 000..8d9029b
--- /dev/null
+++ b/recipes-core/systemd/systemd_%.bbappend
@@ -0,0 +1,2 @@
+inherit enable-audit
+inherit enable-selinux
-- 
1.7.9.5

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] linux-raspberrypi: Replace not working v3.16.1 by v3.16.5

2014-12-03 Thread Jens Lucius 
From: Jens Lucius 

The recipe for 3.16.1 is not working because of a typo in branch
and the revision not being available any more.

Update to latest (and last) 3.16.5.

No Update to a 3.17.x because these get rebased regularly.

Signed-off-by: Jens Lucius 
---
 recipes-kernel/linux/linux-raspberrypi_3.16.1.bb | 6 --
 recipes-kernel/linux/linux-raspberrypi_3.16.5.bb | 6 ++
 2 files changed, 6 insertions(+), 6 deletions(-)
 delete mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.1.bb
 create mode 100644 recipes-kernel/linux/linux-raspberrypi_3.16.5.bb

diff --git a/recipes-kernel/linux/linux-raspberrypi_3.16.1.bb 
b/recipes-kernel/linux/linux-raspberrypi_3.16.1.bb
deleted file mode 100644
index 60aca96..000
--- a/recipes-kernel/linux/linux-raspberrypi_3.16.1.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-SRCREV = "82692a293288c334f3da11895e63ea7d066db4f6"
-SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.14.y \
-   file://sl030raspberrypii2ckernel.patch \
-  "
-
-require linux-raspberrypi.inc
diff --git a/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb 
b/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
new file mode 100644
index 000..97947c2
--- /dev/null
+++ b/recipes-kernel/linux/linux-raspberrypi_3.16.5.bb
@@ -0,0 +1,6 @@
+SRCREV = "377c82aa1d31b37f1096096b0e4c65beb0bc5c49"
+SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-3.16.y \
+   file://sl030raspberrypii2ckernel.patch \
+  "
+
+require linux-raspberrypi.inc
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Headers missing in generated SDK

2014-12-03 Thread Urs Fässler 
Hi,
I added
  TOOLCHAIN_TARGET_TASK += "my-super-package"
in the image recipe.

When I then populate the SDK against this image, I have my-super-package
in the SDK sysroot.

Regards
Urs

On 02.12.2014 20:45, Syed Moosvi wrote:
> Hi Matt,
> 
>I added the following but still not getting headers in the
> generated SDK.
> 
>  *RDEPENDS_${PN}-dev = ""*# added to openssl bb file
> 
> TOOLCHAIN_TARGET_TASK_append = " openssl-dev"   # added to local.conf file
> 
> Also, I don't get any errors when I don't add RDEPENDS_ but I think
> you were getting some errors.
> Any clues as to what I may be missing?
> 
> Thanks,
> 
> Syed
> 
> 
> On Wed, Nov 26, 2014 at 6:07 PM, Matt Schuckmann > wrote:
> 
>> Syed,
>>
>> Your problem sounds similar to a problem I had getting my own headers and
>> static library included in the SDK.
>> Check out this thread to see if it helps.
>>
>> https://lists.yoctoproject.org/pipermail/yocto/2014-September/021678.html
>>
>> Matt S.
>>
>>
> 
> 
> 


-- 
--
bytes at work
Technoparkstrasse 7
CH-8406 Winterthur
Switzerland

phone: +41 52 213 79 79





signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] u-boot precompiled ?

2014-12-03 Thread Matthias.Heise 
Hi all,

I'm still trying to find out basic things about getting a system up and 
running. This question is about U-Boot, is it right that for example for my 
wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source, 
compile it and re-direct in a recipe to take that new file as bootloader ? Or 
can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Yu, Chan KitX 
Hi all,

I had the following issues with building x264 package in Yocto

ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository 
'/home/autoeye/daisy/poky/mybuilds/downloads/git2/git.videolan.org.x264.git'...
FATAL: Failed to determine SOCKS server.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

DEBUG: Python function base_do_fetch finished
DEBUG: Python function do_fetch finished
ERROR: Function failed: Fetcher failure for URL: 
'git://git.videolan.org/x264.git'. Unable to fetch URL from any source.

Weirdly, git cloning that repository worked marvelously. I'm out of my depth 
here so I'm posting here so more minds can dig this. I have also attached the 
full log files so those interested can read the whole error log. I think I have 
set the SOCKS proxy correctly since git clone works for me but I'm open to 
suggestions.

Cheers,
Chan Kit


run.do_fetch.2415
Description: run.do_fetch.2415
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Rfi] "bitbake altera-gsrd-image -c populate_sdk" fails with "Multiple .bb files ... nativesdk-libiconv ... external-linaro-toolchain.bb ... eglibc_2.16.bb"

2014-12-03 Thread Dalon Westergreen 
If you look here
http://rocketboards.org/foswiki/Documentation/YoctoDoraBuildWithMetaAltera

This is a better guide to using newer yocto versions.  I would suggest
dumping the poky-socfpga stuff.

Dalon
On Dec 3, 2014 3:36 AM, "Spriggs, Jim"  wrote:

> Re-Hi,
>
> Some more investigations...
>
> To shorten the build run times, I used the altera-image-minimal and
> core-image-minimal recipes instead of the (much larger) altera-gsrd-image.
>
> As they stand, both recipes can be built without problems.
>
> WIth "bitbake  -c populate_sdk" both fail as above with "Multiple
> .bb files..."
>
> Since one of the duplicate providers is apparently the
> external-linaro-toolchain, I decided to eliminate it from site.conf, and
> let bitbake build the "internal" toolchain.
>
> This time the "-c populate_sdk" worked like a charm.
>
> So it looks to me as if there's an incompatibility between the *external*
> linaro toolchain and the "populte_sdk" task in the altera version of poky.
>
> I'm more than happy to try and fix the problem, but I don't (yet) have a
> clue where to look next.
>
> Has anyone got a pointer for me, please?
> --
> jim
>
> 
> From: rfi-boun...@lists.rocketboards.org [
> rfi-boun...@lists.rocketboards.org] on behalf of Spriggs, Jim [
> j.spri...@raylase.de]
> Sent: 02 December 2014 10:12
> To: r...@lists.rocketboards.org
> Subject: [Rfi] "bitbake altera-gsrd-image -c populate_sdk" fails with
> "Multiple .bb files ... nativesdk-libiconv ...
> external-linaro-toolchain.bb ... eglibc_2.16.bb"
>
> Hi Guys,
>
> Having followed the instructions at
> http://www.rocketboards.org/foswiki/Documentation/GSRD140CompilingLinuxCopyArrowSoCKitEdition
> to set up for building the GSRD image,
> I tried "bitbake altera-gsrd-image" and it worked just fine, producing the
> image as expected.
>
> Then I tried "bitbake altera-gsrd-image -c populate_sdk", and got the
> error message in the Subject.
>
> As an utter newbie, I'm hoping someone can point out (in simple terms!)
> what I'm doing wrong.
>
> Is populate_sdk not supported by SoCKit GSRD 14.0 ?
> Is my invocation wrong?
>
> Thanks for any clues!
>
> --
> Jim
> PS: sorry about the company sig - I can't switch it off.
>
>
>
> 
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Peter von Jan (CEO)
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> ___
> Rfi mailing list
> r...@lists.rocketboards.org
> http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
>
> 
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Peter von Jan (CEO)
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> ___
> Rfi mailing list
> r...@lists.rocketboards.org
> http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Burton, Ross 
On 3 December 2014 at 05:40, Yu, Chan KitX  wrote:

> Weirdly, git cloning that repository worked marvelously. I’m out of my
> depth here so I’m posting here so more minds can dig this. I have also
> attached the full log files so those interested can read the whole error
> log. I think I have set the SOCKS proxy correctly since git clone works for
> me but I’m open to suggestions.
>
>
bitbake clears the environment when starting so its possible that your
proxy settings are being lost.  I believe setting eg
ALL_PROXY="socks://my.proxy/" in your local.conf should work.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Yu, Chan KitX 
Unfortunately, that doesn’t work. I also added poky/scripts/ into PATH so 
oe-git-proxy is within PATH but no good. So I’m stuck here now getting x264 to 
git clone ☹

I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck.

Chan Kit


From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, December 04, 2014 7:17 AM
To: Yu, Chan KitX
Cc: yocto@yoctoproject.org; yuchan...@gmail.com
Subject: Re: [yocto] Issue with compiling x264 package in Yocto


On 3 December 2014 at 05:40, Yu, Chan KitX 
mailto:chan.kitx...@intel.com>> wrote:
Weirdly, git cloning that repository worked marvelously. I’m out of my depth 
here so I’m posting here so more minds can dig this. I have also attached the 
full log files so those interested can read the whole error log. I think I have 
set the SOCKS proxy correctly since git clone works for me but I’m open to 
suggestions.

bitbake clears the environment when starting so its possible that your proxy 
settings are being lost.  I believe setting eg ALL_PROXY="socks://my.proxy/" in 
your local.conf should work.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/2] Add some recipes

2014-12-03 Thread Bian, Naimeng 
> -Original Message-
> From: Joe MacDonald [mailto:joe_macdon...@mentor.com]
> Sent: Wednesday, December 03, 2014 10:16 AM
> To: Alexandru Vaduva
> Subject: Re: [yocto] [PATCH 0/2] Add some recipes
> 
> [Re: [yocto] [PATCH 0/2] Add some recipes] On 14.12.02 (Tue 20:48) Alexandru
> Vaduva wrote:
> 
> > Guys, lets keep Bian in the loop. though, so he does not loos the
> > thread information.
> > So to conclude:
> > 1.) one of us(or anyone in the community) should find the time to
> > investigate if only one multipath tools recipe is applicable and if
> > that is the case keep one in the meta-oe, eventually update it.
> > Since it it related to meta-cgl could take a step forward on this
> > because there could be some bbappends applicable for meta-cgl there,
> > but it will take 2/3 weeks until I will be able to do this. So anyone
> > else interested is welcomed to do it if they are in a hurry.
> 
> I don't think anyone is in a hurry, but I'll be sure to send out a heads-up
> if I find time to start working on this in the next week or so.
> I think it's yours, though, Alex, unless Bian is going to follow up on it 
> again.
> 
> > 2.) We kind of torn apart Bian`s patches and maybe he will not be so
> > willing to do redo the patch for drdb, Joe will you be able to do the
> > required changes for making sure his patch can be integrated inside
> meta-networking.
> >
> > Thank you for your time and patience.
> 
> All things being equal, I would rather integrate a patch from Bian than do it
> myself both from a practical point of view and because I always prefer to have
> more contributors.  So Bian, this is my saying that if you're willing to do
> another version of drbd updated based on the comments received so far and want
> to submit it to the meta-networking tree, I'd be happy to have it.
> 

The drbd patch had been merged into meta-openembedded/meta-oe/recipes-extended/ 
some days before.
Is't necessary to move it from meta-oe to meta-networking.
It looks like that meta-networking is more suitable than meta-oe, 
so, i will send a new patch for meta-networking, and get rid of the meta-oe one.

Thanks
 Bian

> If not, I understand, and the remainder of us can sort it out, I'm sure, but
> my first instinct is to wait to see if the original submitter is interested
> in pursuing this.
> 
> -J.
> 
> >
> >
> > Alex Vaduva
> >
> >
> >
> > On Tuesday, December 2, 2014 10:33 PM, Bruce Ashfield
> >  wrote:
> >
> >
> > On 14-12-02 03:17 PM, Joe MacDonald wrote:
> > > [Re: [yocto] [PATCH 0/2] Add some recipes] On 14.12.02 (Tue 14:49)
> > > Bruce
> > Ashfield wrote:
> > >
> > >> On 14-12-02 02:37 PM, Joe MacDonald wrote:
> > >>> [Re: [yocto] [PATCH 0/2] Add some recipes] On 14.12.02 (Tue 14:03)
> > Alexandru Vaduva wrote:
> > >>>
> >  Hello Bian,
> > 
> >  Did you know that the multipath tools recipe was also available
> >  inside the meta-oe and meta-virtualization?
> >  I do not have any problems with it being available in meta-cgl.
> >  I just
> > wanted
> >  to hear other opinions because I would like to make sure we do
> >  not get to
> > that
> >  point where we keep various versions of various recipes in a
> >  variety of
> > places.
> >  It will be a nightmare to work with them in the future.
> > >>>
> > >>> I completely agree, and I that's mostly the consensus of the community.
> > >>> Since meta-cgl already has dependencies on both
> > >>> meta-virtualization and meta-oe, I think it makes the most sense
> > >>> to try to keep updates for the multipath recipes in one or both of
> > >>> those layers.  My recommendation would be to update the meta-oe
> > >>> one as it has broader applicability, but of course that's up to
> > >>> the submitter and the layer maintainers to decide.  It may be that
> > >>> it's appropriate to maintain a bbappend for the recipe in
> > >>> meta-cgl, but I think it'd be good to send it for inclusion in meta-oe
> first.
> > >>
> > >> I'm with Joe on this one.
> > >>
> > >> I only did a really quick check on the history of the two copies
> > >> that we have, but I see the meta-virt variant was added in January
> > >> 2013 and what could be the first version in meta-oe in March the same 
> > >> year.
> > >
> > > I actually intended to say "update the meta-oe one as it has broader
> > > applicability and if you're feeling ambitious, send the same update
> > > to meta-virtualization" since I thought meta-virt didn't have
> > > dependencies on meta-oe and I can see an argument in favour of
> > > keeping a separate recipe if you're keeping the layer contained.
> > > But it looks like that's not the case, so consolidation makes sense here.
> >
> > Yep, there are dependencies on meta-oe where it makes sense, or if
> > there's a package in meta-virt that isn't particularly twitchy about
> > versions and update cadence.
> >
> > >
> > >> The layer index may not have been as helpful back then (but
> > >> honestly I can't recall) .. either way we fail

Re: [yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Yu, Chan KitX 
Another thing I noticed was the SOCKS_SERVER command did not seem to be 
exported into bitbake’s environment which could have caused the error. Although 
I did set SOCKS_SERVER environment in my shell, I’m wondering how do I set the 
same thing in bitbake so it **might** work?

Chan Kit

From: Yu, Chan KitX
Sent: Thursday, December 04, 2014 9:46 AM
To: Burton, Ross
Cc: yocto@yoctoproject.org; yuchan...@gmail.com
Subject: RE: [yocto] Issue with compiling x264 package in Yocto

Unfortunately, that doesn’t work. I also added poky/scripts/ into PATH so 
oe-git-proxy is within PATH but no good. So I’m stuck here now getting x264 to 
git clone ☹

I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck.

Chan Kit


From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, December 04, 2014 7:17 AM
To: Yu, Chan KitX
Cc: yocto@yoctoproject.org; 
yuchan...@gmail.com
Subject: Re: [yocto] Issue with compiling x264 package in Yocto


On 3 December 2014 at 05:40, Yu, Chan KitX 
mailto:chan.kitx...@intel.com>> wrote:
Weirdly, git cloning that repository worked marvelously. I’m out of my depth 
here so I’m posting here so more minds can dig this. I have also attached the 
full log files so those interested can read the whole error log. I think I have 
set the SOCKS proxy correctly since git clone works for me but I’m open to 
suggestions.

bitbake clears the environment when starting so its possible that your proxy 
settings are being lost.  I believe setting eg ALL_PROXY="socks://my.proxy/" in 
your local.conf should work.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Ong, Boon Leong 
Hi  Yu,
Let’s me work with you on this since we are at the same 
building. ☺
I know the solution to the proxy issue that you are facing

Thanks
BL

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Yu, Chan KitX
Sent: Thursday, December 4, 2014 1:30 PM
To: Burton, Ross
Cc: 'yocto@yoctoproject.org'; 'yuchan...@gmail.com'
Subject: Re: [yocto] Issue with compiling x264 package in Yocto

Another thing I noticed was the SOCKS_SERVER command did not seem to be 
exported into bitbake’s environment which could have caused the error. Although 
I did set SOCKS_SERVER environment in my shell, I’m wondering how do I set the 
same thing in bitbake so it **might** work?

Chan Kit

From: Yu, Chan KitX
Sent: Thursday, December 04, 2014 9:46 AM
To: Burton, Ross
Cc: yocto@yoctoproject.org; 
yuchan...@gmail.com
Subject: RE: [yocto] Issue with compiling x264 package in Yocto

Unfortunately, that doesn’t work. I also added poky/scripts/ into PATH so 
oe-git-proxy is within PATH but no good. So I’m stuck here now getting x264 to 
git clone ☹

I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck.

Chan Kit


From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, December 04, 2014 7:17 AM
To: Yu, Chan KitX
Cc: yocto@yoctoproject.org; 
yuchan...@gmail.com
Subject: Re: [yocto] Issue with compiling x264 package in Yocto


On 3 December 2014 at 05:40, Yu, Chan KitX 
mailto:chan.kitx...@intel.com>> wrote:
Weirdly, git cloning that repository worked marvelously. I’m out of my depth 
here so I’m posting here so more minds can dig this. I have also attached the 
full log files so those interested can read the whole error log. I think I have 
set the SOCKS proxy correctly since git clone works for me but I’m open to 
suggestions.

bitbake clears the environment when starting so its possible that your proxy 
settings are being lost.  I believe setting eg ALL_PROXY="socks://my.proxy/" in 
your local.conf should work.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Issue with compiling x264 package in Yocto

2014-12-03 Thread Yu, Chan KitX 
I got it to compile thanks to Boon Leong. Consider this issue resolved for now.

Chan Kit

From: Ong, Boon Leong
Sent: Thursday, December 04, 2014 2:49 PM
To: Yu, Chan KitX; Burton, Ross
Cc: 'yocto@yoctoproject.org'; 'yuchan...@gmail.com'
Subject: RE: [yocto] Issue with compiling x264 package in Yocto

Hi  Yu,
Let’s me work with you on this since we are at the same 
building. ☺
I know the solution to the proxy issue that you are facing

Thanks
BL

From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Yu, Chan KitX
Sent: Thursday, December 4, 2014 1:30 PM
To: Burton, Ross
Cc: 'yocto@yoctoproject.org'; 'yuchan...@gmail.com'
Subject: Re: [yocto] Issue with compiling x264 package in Yocto

Another thing I noticed was the SOCKS_SERVER command did not seem to be 
exported into bitbake’s environment which could have caused the error. Although 
I did set SOCKS_SERVER environment in my shell, I’m wondering how do I set the 
same thing in bitbake so it **might** work?

Chan Kit

From: Yu, Chan KitX
Sent: Thursday, December 04, 2014 9:46 AM
To: Burton, Ross
Cc: yocto@yoctoproject.org; 
yuchan...@gmail.com
Subject: RE: [yocto] Issue with compiling x264 package in Yocto

Unfortunately, that doesn’t work. I also added poky/scripts/ into PATH so 
oe-git-proxy is within PATH but no good. So I’m stuck here now getting x264 to 
git clone ☹

I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck.

Chan Kit


From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Thursday, December 04, 2014 7:17 AM
To: Yu, Chan KitX
Cc: yocto@yoctoproject.org; 
yuchan...@gmail.com
Subject: Re: [yocto] Issue with compiling x264 package in Yocto


On 3 December 2014 at 05:40, Yu, Chan KitX 
mailto:chan.kitx...@intel.com>> wrote:
Weirdly, git cloning that repository worked marvelously. I’m out of my depth 
here so I’m posting here so more minds can dig this. I have also attached the 
full log files so those interested can read the whole error log. I think I have 
set the SOCKS proxy correctly since git clone works for me but I’m open to 
suggestions.

bitbake clears the environment when starting so its possible that your proxy 
settings are being lost.  I believe setting eg ALL_PROXY="socks://my.proxy/" in 
your local.conf should work.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] GStreamer1.0 : gstreamer1.0-plugins-* doesn't extract the codec libraries into GStreamer library path

2014-12-03 Thread Mohd Azril Ahmad 
Hi all,

I have successfully built the Yocto with multilib environment by using the
meta-intel BSP (ValleyIsland). Plus, I'm including the GStreamer1.0 base +
VAAPI as my default video player.

During the boot-up time, I've noticed that the GStreamer1.0-plugin
libraries (good, bad, and ugly) are not extracted into the GST library path
(/usr/lib64/gstreamer-1.0/).

**On first, I was looking for "libgstisomp4.so" (to play video with qtdemux
pipeline) but gst-inspect-1.0 returns nothing.

After some investigations, I've observed that the bitbake (.bb) and include
(.inc) recipe for gstreamer1.0-plugins- does not package out
the *.so files and I have no choice but to force a .bbappend to install for
it by adding :

FILES_${PN} += "${libdir}/gstreamer-1.0/*.so"

My question here, why the plugin libraries are not extracted ? is it due to
multilib environment ? or missing packaging steps in default recipe ?

Please advise ..

Thanks.

Regards,
Azril
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto