Re: [yocto] bitbake error

[Dimitris Tassopoulos]

Sometimes, I also got some weird errors like that when copying and pasting
projects (or meta layers) from one machine to other. That's because the
flags and some file stats are not copied.

On Thu, 13 Sep 2018, 18:57 Alexander Kanavin, 
wrote:

> It seems as though the build system is unable to create this directory:
>
>
> /home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8
>
> You probably have a permission problem there, working from /home/b but
> attempting to create /home/yocto.
>
> Alex
>
> 2018-09-13 15:15 GMT+02:00 idealsim :
> > Hi, i'm trying to build an image with Yocto on a new machine (ubuntu
> 16.04
> > LTS)but i have this error that i can't resolve. Can you help ?
> >
> > ERROR: Execution of event handler 'uninative_event_fetchloader' failed
> > Traceback (most recent call last):
> >   File
> "/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass",
> > line 55, in uninative_event_fetchloader(e= at
> > 0x7f2015027790>):
> >  if not os.path.exists(tarballpath):
> > >bb.utils.mkdirhier(tarballdir)
> >  if d.getVar("UNINATIVE_URL", True) == "unset":
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line
> > 716, in
> >
> mkdirhier(directory='/home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8'):
> >  if e.errno != errno.EEXIST:
> > >raise e
> >
> > OSError: [Errno 13] Permission denied:
> '/home/b/yocto-krogoth/../../yocto'
> >
> > ERROR: Command execution failed: Traceback (most recent call last):
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py",
> line
> > 104, in runAsyncCommand
> > commandmethod(self.cmds_async, self, options)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py",
> line
> > 325, in buildTargets
> > command.cooker.buildTargets(pkgs_to_build, task)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/cooker.py",
> line
> > 1423, in buildTargets
> > bb.event.fire(bb.event.BuildStarted(buildname, ntargets), self.data)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> > 178, in fire
> > fire_class_handlers(event, d)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> > 110, in fire_class_handlers
> > execute_handler(name, handler, event, d)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> > 82, in execute_handler
> > ret = handler(event)
> >   File
> "/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass",
> > line 55, in uninative_event_fetchloader
> > bb.utils.mkdirhier(tarballdir)
> >   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line
> > 716, in mkdirhier
> > raise e
> > OSError: [Errno 13] Permission denied:
> '/home/b/yocto-krogoth/../../yocto'
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake error

[Alexander Kanavin]

It seems as though the build system is unable to create this directory:

/home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8

You probably have a permission problem there, working from /home/b but
attempting to create /home/yocto.

Alex

2018-09-13 15:15 GMT+02:00 idealsim :
> Hi, i'm trying to build an image with Yocto on a new machine (ubuntu 16.04
> LTS)but i have this error that i can't resolve. Can you help ?
>
> ERROR: Execution of event handler 'uninative_event_fetchloader' failed
> Traceback (most recent call last):
>   File "/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass",
> line 55, in uninative_event_fetchloader(e= 0x7f2015027790>):
>  if not os.path.exists(tarballpath):
> >bb.utils.mkdirhier(tarballdir)
>  if d.getVar("UNINATIVE_URL", True) == "unset":
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line
> 716, in
> mkdirhier(directory='/home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8'):
>  if e.errno != errno.EEXIST:
> >raise e
>
> OSError: [Errno 13] Permission denied: '/home/b/yocto-krogoth/../../yocto'
>
> ERROR: Command execution failed: Traceback (most recent call last):
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py", line
> 104, in runAsyncCommand
> commandmethod(self.cmds_async, self, options)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py", line
> 325, in buildTargets
> command.cooker.buildTargets(pkgs_to_build, task)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/cooker.py", line
> 1423, in buildTargets
> bb.event.fire(bb.event.BuildStarted(buildname, ntargets), self.data)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> 178, in fire
> fire_class_handlers(event, d)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> 110, in fire_class_handlers
> execute_handler(name, handler, event, d)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line
> 82, in execute_handler
> ret = handler(event)
>   File "/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass",
> line 55, in uninative_event_fetchloader
> bb.utils.mkdirhier(tarballdir)
>   File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line
> 716, in mkdirhier
> raise e
> OSError: [Errno 13] Permission denied: '/home/b/yocto-krogoth/../../yocto'
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] bitbake error

[idealsim]

Hi, i'm trying to build an image with Yocto on a new machine (ubuntu 16.04  
LTS)but i have this error that i can't resolve. Can you help ?


ERROR: Execution of event handler 'uninative_event_fetchloader' failed
Traceback (most recent call last):
  File  
"/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass", line  
55, in uninative_event_fetchloader(e=0x7f2015027790>):

 if not os.path.exists(tarballpath):
>bb.utils.mkdirhier(tarballdir)
 if d.getVar("UNINATIVE_URL", True) == "unset":
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line  
716, in  
mkdirhier(directory='/home/b/yocto-krogoth/../../yocto/downloads//uninative/acf1e44a0ac2e855e81da6426197d36358bf7b4e88e552ef933128498c8910f8'):

 if e.errno != errno.EEXIST:
>raise e

OSError: [Errno 13] Permission denied: '/home/b/yocto-krogoth/../../yocto'

ERROR: Command execution failed: Traceback (most recent call last):
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py",  
line 104, in runAsyncCommand

commandmethod(self.cmds_async, self, options)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/command.py",  
line 325, in buildTargets

command.cooker.buildTargets(pkgs_to_build, task)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/cooker.py", line  
1423, in buildTargets

bb.event.fire(bb.event.BuildStarted(buildname, ntargets), self.data)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line  
178, in fire

fire_class_handlers(event, d)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line  
110, in fire_class_handlers

execute_handler(name, handler, event, d)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/event.py", line  
82, in execute_handler

ret = handler(event)
  File  
"/home/b/yocto-krogoth/sources/poky/meta/classes/uninative.bbclass", line  
55, in uninative_event_fetchloader

bb.utils.mkdirhier(tarballdir)
  File "/home/b/yocto-krogoth/sources/poky/bitbake/lib/bb/utils.py", line  
716, in mkdirhier

raise e
OSError: [Errno 13] Permission denied: '/home/b/yocto-krogoth/../../yocto'
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake error ?

[Riko]

Dear Yocto member,

I fixed it

on /etc/resolv.conf

nameserver 8.8.8.8

Thanks for helping everyone


On 10/08/17 05:13, Burton, Ross wrote:

Maybe.  We don't have your computer, so this is your problem to resolve.

Ross

On 9 August 2017 at 22:06, Riko Ho <mailto:antonius.r...@gmail.com>> wrote:


Can it be related with:
https://askubuntu.com/questions/425484/unable-to-use-wget-command
<https://askubuntu.com/questions/425484/unable-to-use-wget-command>
?


On 09/08/2017 8:43 PM, "Bejar-Colonia, Carlos"
mailto:carlos.bejar-colo...@philips.com>> wrote:

This issue seems to be related to proxy server. Probably your
network is behind a  proxy.

This may help:

https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
<https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy>

-Carlos B

*From:*yocto-boun...@yoctoproject.org
<mailto:yocto-boun...@yoctoproject.org>
[mailto:yocto-boun...@yoctoproject.org
<mailto:yocto-boun...@yoctoproject.org>] *On Behalf Of
*Burton, Ross
*Sent:* Wednesday, August 09, 2017 6:35 AM
*To:* Riko Ho mailto:antonius.r...@gmail.com>>
*Cc:* N: mailto:yocto@yoctoproject.org>>
*Subject:* Re: [yocto] bitbake error ?

I've no idea why you can't connect to example.com
<http://example.com> using wget, you'll have to debug it yourself.

Ross

On 9 August 2017 at 11:27, Riko Ho mailto:antonius.r...@gmail.com>> wrote:

so what s the issue？ my connection is working. is it
related with /etc/hosts?
thanks

On Aug 9, 2017 4:38 PM, "Burton, Ross"
mailto:ross.bur...@intel.com>> wrote:

Yep. That's your problem.

$ wget https://www.example.com/

--2017-08-09 09:37:43-- https://www.example.com/

Resolving www.example.com <http://www.example.com>...
93.184.216.34, 2606:2800:220:1:248:1893:25c8:1946

Connecting to www.example.com
<http://www.example.com>|93.184.216.34|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 1270 (1.2K) [text/html]

Saving to: ‘index.html’

index.html  100%[===>]   1.24K
 --.-KB/s  in 0s

2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved
[1270/1270]

Works for me.  Your network or wget is broken, and
that is unrelated to bitbake/yocto/etc.

Ross

On 9 August 2017 at 09:34, Riko
mailto:antonius.r...@gmail.com>> wrote:

This one ?

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$
wget https://www.example.com/
--2017-08-09 16:33:05-- https://www.example.com/
Resolving www.example.com <http://www.example.com>
(www.example.com <http://www.example.com>)...
failed: Name or service not known.
wget: unable to resolve host address
'www.example.com’ <http://www.example.com%E2%80%99>

On 09/08/17 16:31, Burton, Ross wrote:

For some reason, bitbake can't do "wget
https://www.example.com/";.   Try running that
command outside of bitbake and seeing if it
returns any errors.

Ross

On 9 August 2017 at 09:29, Riko
mailto:antonius.r...@gmail.com>> wrote:

Dear Yocto Member,


I have downloaded fresh install of yocto
but got error, here's the trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$
git clone -b pyro
git://git.yoctoproject.org/poky.git
<http://git.yoctoproject.org/poky.git>
Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100%
(89366/89366), done.
remote: Total 373183 (delta 277418),
reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183),
134.71 MiB | 1.47 MiB/s, done.
Resolving deltas: 100% (277418/277418),

Re: [yocto] bitbake error ?

[Riko]

When I test on browser :

https://www.example.com/

I  got server not found ??


On 09/08/17 16:38, Burton, Ross wrote:

Yep.  That's your problem.

$ wget https://www.example.com/
--2017-08-09 09:37:43-- https://www.example.com/
Resolving www.example.com... 93.184.216.34, 
2606:2800:220:1:248:1893:25c8:1946
Connecting to www.example.com 
|93.184.216.34|:443... connected.

HTTP request sent, awaiting response... 200 OK
Length: 1270 (1.2K) [text/html]
Saving to: ‘index.html’

index.html  100%[===>]   1.24K  --.-KB/sin 0s

2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]

Works for me.  Your network or wget is broken, and that is unrelated 
to bitbake/yocto/etc.


Ross

On 9 August 2017 at 09:34, Riko > wrote:


This one ?

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
https://www.example.com/
--2017-08-09 16:33:05-- https://www.example.com/
Resolving www.example.com 
(www.example.com )... failed: Name or
service not known.
wget: unable to resolve host address 'www.example.com’



On 09/08/17 16:31, Burton, Ross wrote:

For some reason, bitbake can't do "wget
https://www.example.com/";.   Try running that command outside of
bitbake and seeing if it returns any errors.

Ross

On 9 August 2017 at 09:29, Riko mailto:antonius.r...@gmail.com>> wrote:

Dear Yocto Member,


I have downloaded fresh install of yocto but got error,
here's the trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b
pyro git://git.yoctoproject.org/poky.git

Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100% (89366/89366), done.
remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47
MiB/s, done.
Resolving deltas: 100% (277418/277418), done.
Checking connectivity... done.


bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
oe-init-build-env
You had no conf/local.conf file. This configuration file has
therefore been
created for you with some default values. You may wish to
edit it to, for
example, select a different MACHINE (target hardware). See
conf/local.conf
for more information as common configuration options are
commented.

You had no conf/bblayers.conf file. This configuration file
has therefore been
created for you with some default values. To add additional
metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE
including a reference
manual which can be found at:
http://yoctoproject.org/documentation


For more information about OpenEmbedded see their website:
http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like
'runqemu qemux86'
bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$
bitbake core-image-minimal
ERROR:  OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk
disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Fetcher failure for URL: 'https://www.example.com/'. URL
https://www.example.com/ doesn't work.
Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.


Summary: There was 1 ERROR message shown, returning a
non-zero exit code.


Any suggestions ?

I'm using ubuntu 16.04,

Thanks

-- 
___

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








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

Re: [yocto] bitbake error ?

[Burton, Ross]

Maybe.  We don't have your computer, so this is your problem to resolve.

Ross

On 9 August 2017 at 22:06, Riko Ho  wrote:

> Can it be related with:
> https://askubuntu.com/questions/425484/unable-to-use-wget-command
> ?
>
> On 09/08/2017 8:43 PM, "Bejar-Colonia, Carlos" <
> carlos.bejar-colo...@philips.com> wrote:
>
> This issue seems to be related to proxy server. Probably your network is
> behind a  proxy.
>
> This may help:
>
> https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy
>
>
>
> -Carlos B
>
>
>
> *From:* yocto-boun...@yoctoproject.org [mailto:yocto-bounces@yoctopro
> ject.org] *On Behalf Of *Burton, Ross
> *Sent:* Wednesday, August 09, 2017 6:35 AM
> *To:* Riko Ho 
> *Cc:* N: 
> *Subject:* Re: [yocto] bitbake error ?
>
>
>
> I've no idea why you can't connect to example.com using wget, you'll have
> to debug it yourself.
>
>
>
> Ross
>
>
>
> On 9 August 2017 at 11:27, Riko Ho  wrote:
>
> so what s the issue？ my connection is working. is it related with
> /etc/hosts?
> thanks
>
> On Aug 9, 2017 4:38 PM, "Burton, Ross"  wrote:
>
> Yep.  That's your problem.
>
>
>
> $ wget https://www.example.com/
>
> --2017-08-09 09:37:43--  https://www.example.com/
>
> Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:
> 1946
>
> Connecting to www.example.com|93.184.216.34|:443... connected.
>
> HTTP request sent, awaiting response... 200 OK
>
> Length: 1270 (1.2K) [text/html]
>
> Saving to: ‘index.html’
>
>
>
> index.html  100%[===>]   1.24K  --.-KB/sin 0s
>
>
>
> 2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]
>
>
>
> Works for me.  Your network or wget is broken, and that is unrelated to
> bitbake/yocto/etc.
>
>
>
> Ross
>
>
>
> On 9 August 2017 at 09:34, Riko  wrote:
>
> This one ?
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
> https://www.example.com/
> --2017-08-09 16:33:05--  https://www.example.com/
> Resolving www.example.com (www.example.com)... failed: Name or service
> not known.
> wget: unable to resolve host address 'www.example.com’
>
>
>
> On 09/08/17 16:31, Burton, Ross wrote:
>
> For some reason, bitbake can't do "wget https://www.example.com/";.   Try
> running that command outside of bitbake and seeing if it returns any
> errors.
>
>
>
> Ross
>
>
>
> On 9 August 2017 at 09:29, Riko  wrote:
>
> Dear Yocto Member,
>
>
> I have downloaded fresh install of yocto but got error, here's the trace :
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
> git.yoctoproject.org/poky.git
> Cloning into 'poky'...
> remote: Counting objects: 373183, done.
> remote: Compressing objects: 100% (89366/89366), done.
> remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
> Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
> Resolving deltas: 100% (277418/277418), done.
> Checking connectivity... done.
>
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
> oe-init-build-env
> You had no conf/local.conf file. This configuration file has therefore been
> created for you with some default values. You may wish to edit it to, for
> example, select a different MACHINE (target hardware). See conf/local.conf
> for more information as common configuration options are commented.
>
> You had no conf/bblayers.conf file. This configuration file has therefore
> been
> created for you with some default values. To add additional metadata layers
> into your configuration please add entries to conf/bblayers.conf.
>
> The Yocto Project has extensive documentation about OE including a
> reference
> manual which can be found at:
> http://yoctoproject.org/documentation
>
> For more information about OpenEmbedded see their website:
> http://www.openembedded.org/
>
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake '
>
> Common targets are:
> core-image-minimal
> core-image-sato
> meta-toolchain
> meta-ide-support
>
> You can also run generated qemu images with a command like 'runqemu
> qemux86'
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
> core-image-minimal
> ERROR:  OE-core's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is th

Re: [yocto] bitbake error ?

[Riko Ho]

Can it be related with:
https://askubuntu.com/questions/425484/unable-to-use-wget-command
?

On 09/08/2017 8:43 PM, "Bejar-Colonia, Carlos" <
carlos.bejar-colo...@philips.com> wrote:

This issue seems to be related to proxy server. Probably your network is
behind a  proxy.

This may help:

https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy



-Carlos B



*From:* yocto-boun...@yoctoproject.org [mailto:yocto-bounces@
yoctoproject.org] *On Behalf Of *Burton, Ross
*Sent:* Wednesday, August 09, 2017 6:35 AM
*To:* Riko Ho 
*Cc:* N: 
*Subject:* Re: [yocto] bitbake error ?



I've no idea why you can't connect to example.com using wget, you'll have
to debug it yourself.



Ross



On 9 August 2017 at 11:27, Riko Ho  wrote:

so what s the issue？ my connection is working. is it related with
/etc/hosts?
thanks

On Aug 9, 2017 4:38 PM, "Burton, Ross"  wrote:

Yep.  That's your problem.



$ wget https://www.example.com/

--2017-08-09 09:37:43--  https://www.example.com/

Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:
1946

Connecting to www.example.com|93.184.216.34|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 1270 (1.2K) [text/html]

Saving to: ‘index.html’



index.html  100%[===>]   1.24K  --.-KB/sin 0s



2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]



Works for me.  Your network or wget is broken, and that is unrelated to
bitbake/yocto/etc.



Ross



On 9 August 2017 at 09:34, Riko  wrote:

This one ?

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
https://www.example.com/
--2017-08-09 16:33:05--  https://www.example.com/
Resolving www.example.com (www.example.com)... failed: Name or service not
known.
wget: unable to resolve host address 'www.example.com’



On 09/08/17 16:31, Burton, Ross wrote:

For some reason, bitbake can't do "wget https://www.example.com/";.   Try
running that command outside of bitbake and seeing if it returns any
errors.



Ross



On 9 August 2017 at 09:29, Riko  wrote:

Dear Yocto Member,


I have downloaded fresh install of yocto but got error, here's the trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
git.yoctoproject.org/poky.git
Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100% (89366/89366), done.
remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
Resolving deltas: 100% (277418/277418), done.
Checking connectivity... done.


bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore
been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
core-image-minimal
ERROR:  OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:

Fetcher failure for URL: 'https://www.example.com/'. URL
https://www.example.com/ doesn't work.
Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.


Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Any suggestions ?

I'm using ubuntu 16.04,

Thanks

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









--
The information contained in this message may be confidential and legally
protected under applicable law. The message is intended solely for the
addressee(s). If you are not the intended recipient, you are hereby
notified that any use, forwarding, dissemination,

Re: [yocto] bitbake error ?

[Bejar-Colonia, Carlos]

This issue seems to be related to proxy server. Probably your network is behind 
a  proxy.
This may help:
https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy

-Carlos B

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Burton, Ross
Sent: Wednesday, August 09, 2017 6:35 AM
To: Riko Ho 
Cc: N: 
Subject: Re: [yocto] bitbake error ?

I've no idea why you can't connect to example.com<http://example.com> using 
wget, you'll have to debug it yourself.

Ross

On 9 August 2017 at 11:27, Riko Ho 
mailto:antonius.r...@gmail.com>> wrote:

so what s the issue？ my connection is working. is it related with /etc/hosts?
thanks
On Aug 9, 2017 4:38 PM, "Burton, Ross" 
mailto:ross.bur...@intel.com>> wrote:
Yep.  That's your problem.

$ wget https://www.example.com/
--2017-08-09 09:37:43--  https://www.example.com/
Resolving www.example.com<http://www.example.com>... 93.184.216.34, 
2606:2800:220:1:248:1893:25c8:1946
Connecting to www.example.com<http://www.example.com>|93.184.216.34|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 1270 (1.2K) [text/html]
Saving to: ‘index.html’

index.html  100%[===>]   1.24K  --.-KB/sin 0s

2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]

Works for me.  Your network or wget is broken, and that is unrelated to 
bitbake/yocto/etc.

Ross

On 9 August 2017 at 09:34, Riko 
mailto:antonius.r...@gmail.com>> wrote:

This one ?

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget 
https://www.example.com/
--2017-08-09 16:33:05--  https://www.example.com/
Resolving www.example.com<http://www.example.com> 
(www.example.com<http://www.example.com>)... failed: Name or service not known.
wget: unable to resolve host address 'www.example.com’<http://www.example.com’>

On 09/08/17 16:31, Burton, Ross wrote:
For some reason, bitbake can't do "wget https://www.example.com/";.   Try 
running that command outside of bitbake and seeing if it returns any errors.

Ross

On 9 August 2017 at 09:29, Riko 
mailto:antonius.r...@gmail.com>> wrote:
Dear Yocto Member,


I have downloaded fresh install of yocto but got error, here's the trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro 
git://git.yoctoproject.org/poky.git<http://git.yoctoproject.org/poky.git>
Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100% (89366/89366), done.
remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
Resolving deltas: 100% (277418/277418), done.
Checking connectivity... done.


bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake 
core-image-minimal
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker 
(see sanity.conf).
Following is the list of potential problems / advisories:

Fetcher failure for URL: 'https://www.example.com/'. URL 
https://www.example.com/ doesn't work.
Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.


Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Any suggestions ?

I'm using ubuntu 16.04,

Thanks

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






The information contained in this message may be confidential and legally 
protected unde

Re: [yocto] bitbake error ?

[Burton, Ross]

I've no idea why you can't connect to example.com using wget, you'll have
to debug it yourself.

Ross

On 9 August 2017 at 11:27, Riko Ho  wrote:

> so what s the issue？ my connection is working. is it related with
> /etc/hosts?
> thanks
> On Aug 9, 2017 4:38 PM, "Burton, Ross"  wrote:
>
>> Yep.  That's your problem.
>>
>> $ wget https://www.example.com/
>> --2017-08-09 09:37:43--  https://www.example.com/
>> Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:
>> 1946
>> Connecting to www.example.com|93.184.216.34|:443... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 1270 (1.2K) [text/html]
>> Saving to: ‘index.html’
>>
>> index.html  100%[===>]   1.24K  --.-KB/sin 0s
>>
>> 2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]
>>
>> Works for me.  Your network or wget is broken, and that is unrelated to
>> bitbake/yocto/etc.
>>
>> Ross
>>
>> On 9 August 2017 at 09:34, Riko  wrote:
>>
>>> This one ?
>>>
>>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
>>> https://www.example.com/
>>> --2017-08-09 16:33:05--  https://www.example.com/
>>> Resolving www.example.com (www.example.com)... failed: Name or service
>>> not known.
>>> wget: unable to resolve host address 'www.example.com’
>>>
>>>
>>> On 09/08/17 16:31, Burton, Ross wrote:
>>>
>>> For some reason, bitbake can't do "wget https://www.example.com/";.
>>> Try running that command outside of bitbake and seeing if it returns any
>>> errors.
>>>
>>> Ross
>>>
>>> On 9 August 2017 at 09:29, Riko  wrote:
>>>
 Dear Yocto Member,


 I have downloaded fresh install of yocto but got error, here's the
 trace :

 bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
 git.yoctoproject.org/poky.git
 Cloning into 'poky'...
 remote: Counting objects: 373183, done.
 remote: Compressing objects: 100% (89366/89366), done.
 remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
 Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
 Resolving deltas: 100% (277418/277418), done.
 Checking connectivity... done.


 bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
 oe-init-build-env
 You had no conf/local.conf file. This configuration file has therefore
 been
 created for you with some default values. You may wish to edit it to,
 for
 example, select a different MACHINE (target hardware). See
 conf/local.conf
 for more information as common configuration options are commented.

 You had no conf/bblayers.conf file. This configuration file has
 therefore been
 created for you with some default values. To add additional metadata
 layers
 into your configuration please add entries to conf/bblayers.conf.

 The Yocto Project has extensive documentation about OE including a
 reference
 manual which can be found at:
 http://yoctoproject.org/documentation

 For more information about OpenEmbedded see their website:
 http://www.openembedded.org/


 ### Shell environment set up for builds. ###

 You can now run 'bitbake '

 Common targets are:
 core-image-minimal
 core-image-sato
 meta-toolchain
 meta-ide-support

 You can also run generated qemu images with a command like 'runqemu
 qemux86'
 bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
 core-image-minimal
 ERROR:  OE-core's config sanity checker detected a potential
 misconfiguration.
 Either fix the cause of this error or at your own risk disable the
 checker (see sanity.conf).
 Following is the list of potential problems / advisories:

 Fetcher failure for URL: 'https://www.example.com/'. URL
 https://www.example.com/ doesn't work.
 Please ensure your host's network is configured correctly,
 or set BB_NO_NETWORK = "1" to disable network access if
 all required sources are on local disk.


 Summary: There was 1 ERROR message shown, returning a non-zero exit
 code.


 Any suggestions ?

 I'm using ubuntu 16.04,

 Thanks

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

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

Re: [yocto] bitbake error ?

[Riko Ho]

so what s the issue？ my connection is working. is it related with
/etc/hosts?
thanks
On Aug 9, 2017 4:38 PM, "Burton, Ross"  wrote:

> Yep.  That's your problem.
>
> $ wget https://www.example.com/
> --2017-08-09 09:37:43--  https://www.example.com/
> Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:
> 1946
> Connecting to www.example.com|93.184.216.34|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 1270 (1.2K) [text/html]
> Saving to: ‘index.html’
>
> index.html  100%[===>]   1.24K  --.-KB/sin 0s
>
> 2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]
>
> Works for me.  Your network or wget is broken, and that is unrelated to
> bitbake/yocto/etc.
>
> Ross
>
> On 9 August 2017 at 09:34, Riko  wrote:
>
>> This one ?
>>
>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
>> https://www.example.com/
>> --2017-08-09 16:33:05--  https://www.example.com/
>> Resolving www.example.com (www.example.com)... failed: Name or service
>> not known.
>> wget: unable to resolve host address 'www.example.com’
>>
>>
>> On 09/08/17 16:31, Burton, Ross wrote:
>>
>> For some reason, bitbake can't do "wget https://www.example.com/";.   Try
>> running that command outside of bitbake and seeing if it returns any
>> errors.
>>
>> Ross
>>
>> On 9 August 2017 at 09:29, Riko  wrote:
>>
>>> Dear Yocto Member,
>>>
>>>
>>> I have downloaded fresh install of yocto but got error, here's the trace
>>> :
>>>
>>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
>>> git.yoctoproject.org/poky.git
>>> Cloning into 'poky'...
>>> remote: Counting objects: 373183, done.
>>> remote: Compressing objects: 100% (89366/89366), done.
>>> remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
>>> Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
>>> Resolving deltas: 100% (277418/277418), done.
>>> Checking connectivity... done.
>>>
>>>
>>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
>>> oe-init-build-env
>>> You had no conf/local.conf file. This configuration file has therefore
>>> been
>>> created for you with some default values. You may wish to edit it to, for
>>> example, select a different MACHINE (target hardware). See
>>> conf/local.conf
>>> for more information as common configuration options are commented.
>>>
>>> You had no conf/bblayers.conf file. This configuration file has
>>> therefore been
>>> created for you with some default values. To add additional metadata
>>> layers
>>> into your configuration please add entries to conf/bblayers.conf.
>>>
>>> The Yocto Project has extensive documentation about OE including a
>>> reference
>>> manual which can be found at:
>>> http://yoctoproject.org/documentation
>>>
>>> For more information about OpenEmbedded see their website:
>>> http://www.openembedded.org/
>>>
>>>
>>> ### Shell environment set up for builds. ###
>>>
>>> You can now run 'bitbake '
>>>
>>> Common targets are:
>>> core-image-minimal
>>> core-image-sato
>>> meta-toolchain
>>> meta-ide-support
>>>
>>> You can also run generated qemu images with a command like 'runqemu
>>> qemux86'
>>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
>>> core-image-minimal
>>> ERROR:  OE-core's config sanity checker detected a potential
>>> misconfiguration.
>>> Either fix the cause of this error or at your own risk disable the
>>> checker (see sanity.conf).
>>> Following is the list of potential problems / advisories:
>>>
>>> Fetcher failure for URL: 'https://www.example.com/'. URL
>>> https://www.example.com/ doesn't work.
>>> Please ensure your host's network is configured correctly,
>>> or set BB_NO_NETWORK = "1" to disable network access if
>>> all required sources are on local disk.
>>>
>>>
>>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>>
>>>
>>> Any suggestions ?
>>>
>>> I'm using ubuntu 16.04,
>>>
>>> Thanks
>>>
>>> --
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake error ?

[Burton, Ross]

Yep.  That's your problem.

$ wget https://www.example.com/
--2017-08-09 09:37:43--  https://www.example.com/
Resolving www.example.com... 93.184.216.34,
2606:2800:220:1:248:1893:25c8:1946
Connecting to www.example.com|93.184.216.34|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1270 (1.2K) [text/html]
Saving to: ‘index.html’

index.html  100%[===>]   1.24K  --.-KB/sin 0s

2017-08-09 09:37:44 (15.3 MB/s) - ‘index.html’ saved [1270/1270]

Works for me.  Your network or wget is broken, and that is unrelated to
bitbake/yocto/etc.

Ross

On 9 August 2017 at 09:34, Riko  wrote:

> This one ?
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget
> https://www.example.com/
> --2017-08-09 16:33:05--  https://www.example.com/
> Resolving www.example.com (www.example.com)... failed: Name or service
> not known.
> wget: unable to resolve host address 'www.example.com’
>
>
> On 09/08/17 16:31, Burton, Ross wrote:
>
> For some reason, bitbake can't do "wget https://www.example.com/";.   Try
> running that command outside of bitbake and seeing if it returns any
> errors.
>
> Ross
>
> On 9 August 2017 at 09:29, Riko  wrote:
>
>> Dear Yocto Member,
>>
>>
>> I have downloaded fresh install of yocto but got error, here's the trace :
>>
>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
>> git.yoctoproject.org/poky.git
>> Cloning into 'poky'...
>> remote: Counting objects: 373183, done.
>> remote: Compressing objects: 100% (89366/89366), done.
>> remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
>> Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
>> Resolving deltas: 100% (277418/277418), done.
>> Checking connectivity... done.
>>
>>
>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
>> oe-init-build-env
>> You had no conf/local.conf file. This configuration file has therefore
>> been
>> created for you with some default values. You may wish to edit it to, for
>> example, select a different MACHINE (target hardware). See conf/local.conf
>> for more information as common configuration options are commented.
>>
>> You had no conf/bblayers.conf file. This configuration file has therefore
>> been
>> created for you with some default values. To add additional metadata
>> layers
>> into your configuration please add entries to conf/bblayers.conf.
>>
>> The Yocto Project has extensive documentation about OE including a
>> reference
>> manual which can be found at:
>> http://yoctoproject.org/documentation
>>
>> For more information about OpenEmbedded see their website:
>> http://www.openembedded.org/
>>
>>
>> ### Shell environment set up for builds. ###
>>
>> You can now run 'bitbake '
>>
>> Common targets are:
>> core-image-minimal
>> core-image-sato
>> meta-toolchain
>> meta-ide-support
>>
>> You can also run generated qemu images with a command like 'runqemu
>> qemux86'
>> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
>> core-image-minimal
>> ERROR:  OE-core's config sanity checker detected a potential
>> misconfiguration.
>> Either fix the cause of this error or at your own risk disable the
>> checker (see sanity.conf).
>> Following is the list of potential problems / advisories:
>>
>> Fetcher failure for URL: 'https://www.example.com/'. URL
>> https://www.example.com/ doesn't work.
>> Please ensure your host's network is configured correctly,
>> or set BB_NO_NETWORK = "1" to disable network access if
>> all required sources are on local disk.
>>
>>
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>
>>
>> Any suggestions ?
>>
>> I'm using ubuntu 16.04,
>>
>> Thanks
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake error ?

[Riko]

This one ?

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ wget 
https://www.example.com/

--2017-08-09 16:33:05--  https://www.example.com/
Resolving www.example.com (www.example.com)... failed: Name or service 
not known.

wget: unable to resolve host address 'www.example.com’


On 09/08/17 16:31, Burton, Ross wrote:
For some reason, bitbake can't do "wget https://www.example.com/";.   
Try running that command outside of bitbake and seeing if it returns 
any errors.


Ross

On 9 August 2017 at 09:29, Riko > wrote:


Dear Yocto Member,


I have downloaded fresh install of yocto but got error, here's the
trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro
git://git.yoctoproject.org/poky.git

Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100% (89366/89366), done.
remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s,
done.
Resolving deltas: 100% (277418/277418), done.
Checking connectivity... done.


bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
oe-init-build-env
You had no conf/local.conf file. This configuration file has
therefore been
created for you with some default values. You may wish to edit it
to, for
example, select a different MACHINE (target hardware). See
conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has
therefore been
created for you with some default values. To add additional
metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a
reference
manual which can be found at:
http://yoctoproject.org/documentation


For more information about OpenEmbedded see their website:
http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like
'runqemu qemux86'
bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
core-image-minimal
ERROR:  OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable
the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Fetcher failure for URL: 'https://www.example.com/'. URL
https://www.example.com/ doesn't work.
Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.


Summary: There was 1 ERROR message shown, returning a non-zero
exit code.


Any suggestions ?

I'm using ubuntu 16.04,

Thanks

-- 
___

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





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

Re: [yocto] bitbake error ?

[Burton, Ross]

For some reason, bitbake can't do "wget https://www.example.com/";.   Try
running that command outside of bitbake and seeing if it returns any errors.

Ross

On 9 August 2017 at 09:29, Riko  wrote:

> Dear Yocto Member,
>
>
> I have downloaded fresh install of yocto but got error, here's the trace :
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro git://
> git.yoctoproject.org/poky.git
> Cloning into 'poky'...
> remote: Counting objects: 373183, done.
> remote: Compressing objects: 100% (89366/89366), done.
> remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
> Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
> Resolving deltas: 100% (277418/277418), done.
> Checking connectivity... done.
>
>
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source
> oe-init-build-env
> You had no conf/local.conf file. This configuration file has therefore been
> created for you with some default values. You may wish to edit it to, for
> example, select a different MACHINE (target hardware). See conf/local.conf
> for more information as common configuration options are commented.
>
> You had no conf/bblayers.conf file. This configuration file has therefore
> been
> created for you with some default values. To add additional metadata layers
> into your configuration please add entries to conf/bblayers.conf.
>
> The Yocto Project has extensive documentation about OE including a
> reference
> manual which can be found at:
> http://yoctoproject.org/documentation
>
> For more information about OpenEmbedded see their website:
> http://www.openembedded.org/
>
>
> ### Shell environment set up for builds. ###
>
> You can now run 'bitbake '
>
> Common targets are:
> core-image-minimal
> core-image-sato
> meta-toolchain
> meta-ide-support
>
> You can also run generated qemu images with a command like 'runqemu
> qemux86'
> bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake
> core-image-minimal
> ERROR:  OE-core's config sanity checker detected a potential
> misconfiguration.
> Either fix the cause of this error or at your own risk disable the
> checker (see sanity.conf).
> Following is the list of potential problems / advisories:
>
> Fetcher failure for URL: 'https://www.example.com/'. URL
> https://www.example.com/ doesn't work.
> Please ensure your host's network is configured correctly,
> or set BB_NO_NETWORK = "1" to disable network access if
> all required sources are on local disk.
>
>
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
> Any suggestions ?
>
> I'm using ubuntu 16.04,
>
> Thanks
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] bitbake error ?

[Riko]

Dear Yocto Member,


I have downloaded fresh install of yocto but got error, here's the trace :

bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~$ git clone -b pyro 
git://git.yoctoproject.org/poky.git

Cloning into 'poky'...
remote: Counting objects: 373183, done.
remote: Compressing objects: 100% (89366/89366), done.
remote: Total 373183 (delta 277418), reused 373031 (delta 277266)
Receiving objects: 100% (373183/373183), 134.71 MiB | 1.47 MiB/s, done.
Resolving deltas: 100% (277418/277418), done.
Checking connectivity... done.


bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky$ source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has 
therefore been

created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake '

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC:~/poky/build$ bitbake 
core-image-minimal
ERROR:  OE-core's config sanity checker detected a potential 
misconfiguration.
Either fix the cause of this error or at your own risk disable the 
checker (see sanity.conf).

Following is the list of potential problems / advisories:

Fetcher failure for URL: 'https://www.example.com/'. URL 
https://www.example.com/ doesn't work.

Please ensure your host's network is configured correctly,
or set BB_NO_NETWORK = "1" to disable network access if
all required sources are on local disk.


Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Any suggestions ?

I'm using ubuntu 16.04,

Thanks

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

Re: [yocto] bitbake error

[Gary Thomas]

Sorry for the dups - I forgot to CC the list.

On 2015-09-21 08:35, Paul Eggleton wrote:

On Monday 21 September 2015 07:55:35 Gary Thomas wrote:

On 2015-09-21 07:38, Paul Eggleton wrote:

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:

When trying to build using latest Poky/Yocto master
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:

=
=== = Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO= "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
cortexa9" TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb
:

The stack trace of python calls that resulted in this exception/failure
was: File: 'relocatable_binaries_preprocess', lineno: 6, function:
>>
0002:def relocatable_binaries_preprocess(d):
0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
_6

4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
0005:
*** 0006:relocatable_binaries_preprocess(d)

0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function:

relocatable_binaries_preprocess 0001:
0002:def relocatable_binaries_preprocess(d):
*** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
_6

4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
0005:
0006:relocatable_binaries_preprocess(d)

0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace

0003:
0004:for bindir in bindirs:
0005:#bb.note ("Processing directory " + bindir)
0006:directory = path + "/" + bindir

*** 0007:process_dir (path, directory, d)

0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir

0040:perms = None
0041:else:
0042:# Temporarily make the file writeable so we
can

chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)

*** 0044:process_file(cmd, fpath, rootdir, baseprefix,
tmpdir,

d) 0045:
0046:if perms:
0047:os.chmod(fpath, perms)

0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux

0001:def process_file_linux(cmd, fpath, rootdir, baseprefix,
tmpdir,

d): 0002:import subprocess as sub

0003:
*** 0004:p = sub.Popen([cmd, '-l',

fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out =
p.communicate()

0006:# If returned succesfully, process stderr for results
0007:if p.returncode != 0:
0008:return

File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__

0706:cwd, env, universal_newlines,
0707:startupinfo, creationflags,

shell, to_close, 0708:p2cread, p2cwrite,

0709:c2pread, c2pwrite,

*** 0710:errread, errwrite)

0711:except Exception:
0712:# Preserve original exception in case os.close

raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:

_execute_child 1331:except OSError as e:
1332:if e.errno != errno.ECHILD:
1333:raise
1334:child_exception = pickle.loads(data)

*** 1335:raise child_exception

1336:
1337:
1338:def _handle_exitstatus(self, sts,

_WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
_WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in:
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0
.6
4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.b
b,
do_populate_sysroot) failed with exit code '1'
=
==
==

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
Note that this is a build in a older tree, one which 

Re: [yocto] bitbake error

[Paul Eggleton]

On Monday 21 September 2015 07:55:35 Gary Thomas wrote:
> On 2015-09-21 07:38, Paul Eggleton wrote:
> > On Monday 21 September 2015 07:10:00 Gary Thomas wrote:
> >> When trying to build using latest Poky/Yocto master
> >> (7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:
> >> 
> >> =
> >> === = Build Configuration:
> >> BB_VERSION= "1.27.1"
> >> BUILD_SYS = "x86_64-linux"
> >> NATIVELSBSTRING   = "Ubuntu-15.04"
> >> TARGET_SYS= "arm-amltd-linux-gnueabi"
> >> MACHINE   = "teton-p0382"
> >> DISTRO= "amltd"
> >> DISTRO_VERSION= "1.8+snapshot-20150921"
> >> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
> >> cortexa9" TARGET_FPU= "vfp-neon"
> >> meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"
> >> 
> >> ERROR: Error executing a python function in
> >> /local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb
> >> :
> >> 
> >> The stack trace of python calls that resulted in this exception/failure
> >> was: File: 'relocatable_binaries_preprocess', lineno: 6, function:
> >> >> 
> >> 0002:def relocatable_binaries_preprocess(d):
> >>0003:
> >> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
> >> _6
> >> 
> >> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
> >>0005:
> >>*** 0006:relocatable_binaries_preprocess(d)
> >>
> >>0007:
> >> File: 'relocatable_binaries_preprocess', lineno: 3, function:
> >> 
> >> relocatable_binaries_preprocess 0001:
> >>0002:def relocatable_binaries_preprocess(d):
> >>*** 0003:
> >> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
> >> _6
> >> 
> >> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
> >>0005:
> >>0006:relocatable_binaries_preprocess(d)
> >> 
> >>0007:
> >> File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
> >> 
> >>0003:
> >>0004:for bindir in bindirs:
> >>0005:#bb.note ("Processing directory " + bindir)
> >>0006:directory = path + "/" + bindir
> >>
> >>*** 0007:process_dir (path, directory, d)
> >>
> >>0008:
> >> File: 'chrpath.bbclass', lineno: 44, function: process_dir
> >> 
> >>0040:perms = None
> >>0041:else:
> >>0042:# Temporarily make the file writeable so we
> >>can
> >> 
> >> chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
> >> 
> >>*** 0044:process_file(cmd, fpath, rootdir, baseprefix,
> >>tmpdir,
> >> 
> >> d) 0045:
> >>0046:if perms:
> >>0047:os.chmod(fpath, perms)
> >> 
> >>0048:
> >> File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
> >> 
> >>0001:def process_file_linux(cmd, fpath, rootdir, baseprefix,
> >>tmpdir,
> >> 
> >> d): 0002:import subprocess as sub
> >> 
> >>0003:
> >>*** 0004:p = sub.Popen([cmd, '-l',
> >> 
> >> fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out =
> >> p.communicate()
> >> 
> >>0006:# If returned succesfully, process stderr for results
> >>0007:if p.returncode != 0:
> >>0008:return
> >> 
> >> File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
> >> 
> >>0706:cwd, env, universal_newlines,
> >>0707:startupinfo, creationflags,
> >> 
> >> shell, to_close, 0708:p2cread, p2cwrite,
> >> 
> >>0709:c2pread, c2pwrite,
> >>
> >>*** 0710:errread, errwrite)
> >>
> >>0711:except Exception:
> >>0712:# Preserve original exception in case os.close
> >> 
> >> raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
> >> 0714:
> >> File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:
> >> 
> >> _execute_child 1331:except OSError as e:
> >>1332:if e.errno != errno.ECHILD:
> >>1333:raise
> >>1334:child_exception = pickle.loads(data)
> >>
> >>*** 1335:raise child_exception
> >>
> >>1336:
> >>1337:
> >>1338:def _handle_exitstatus(self, sts,
> >> 
> >> _WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
> >> _WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
> >> directory
> >> 
> >> ERROR: Function failed: relocatable_binaries_preprocess
> >> ERROR: Logfile of failure stored in:
> >> /local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0
> >> .6
> >> 4-r0/tem

Re: [yocto] bitbake error

[Gary Thomas]

On 2015-09-21 07:38, Paul Eggleton wrote:

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:

When trying to build using latest Poky/Yocto master
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:


= Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO= "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'relocatable_binaries_preprocess', lineno: 6, function: 
0002:def relocatable_binaries_preprocess(d):
   0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
   0005:
   *** 0006:relocatable_binaries_preprocess(d)
   0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function:
relocatable_binaries_preprocess 0001:
   0002:def relocatable_binaries_preprocess(d):
   *** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
   0005:
   0006:relocatable_binaries_preprocess(d)
   0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
   0003:
   0004:for bindir in bindirs:
   0005:#bb.note ("Processing directory " + bindir)
   0006:directory = path + "/" + bindir
   *** 0007:process_dir (path, directory, d)
   0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir
   0040:perms = None
   0041:else:
   0042:# Temporarily make the file writeable so we can
chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
   *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir,
d) 0045:
   0046:if perms:
   0047:os.chmod(fpath, perms)
   0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
   0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir,
d): 0002:import subprocess as sub
   0003:
   *** 0004:p = sub.Popen([cmd, '-l',
fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out = p.communicate()
   0006:# If returned succesfully, process stderr for results
   0007:if p.returncode != 0:
   0008:return
File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
   0706:cwd, env, universal_newlines,
   0707:startupinfo, creationflags,
shell, to_close, 0708:p2cread, p2cwrite,
   0709:c2pread, c2pwrite,
   *** 0710:errread, errwrite)
   0711:except Exception:
   0712:# Preserve original exception in case os.close
raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:
_execute_child 1331:except OSError as e:
   1332:if e.errno != errno.ECHILD:
   1333:raise
   1334:child_exception = pickle.loads(data)
   *** 1335:raise child_exception
   1336:
   1337:
   1338:def _handle_exitstatus(self, sts,
_WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
_WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in:
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.6
4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb,
do_populate_sysroot) failed with exit code '1'
===
==

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
Note that this is a build in a older tree, one which I've been using
successfully (as you can tell) since late 2014.

Interestingly, I can build using the same meta-data on a different build
box!

I get the same error when using a totally fresh tree, so I'm really
perplexed by this one...


I belie

Re: [yocto] bitbake error

[Paul Eggleton]

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:
> When trying to build using latest Poky/Yocto master
> (7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:
> 
> 
> = Build Configuration:
> BB_VERSION= "1.27.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-15.04"
> TARGET_SYS= "arm-amltd-linux-gnueabi"
> MACHINE   = "teton-p0382"
> DISTRO= "amltd"
> DISTRO_VERSION= "1.8+snapshot-20150921"
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
> TARGET_FPU= "vfp-neon"
> meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"
> 
> ERROR: Error executing a python function in
> /local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:
> 
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'relocatable_binaries_preprocess', lineno: 6, function: 
> 0002:def relocatable_binaries_preprocess(d):
>   0003:   
> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
>   0005:
>   *** 0006:relocatable_binaries_preprocess(d)
>   0007:
> File: 'relocatable_binaries_preprocess', lineno: 3, function:
> relocatable_binaries_preprocess 0001:
>   0002:def relocatable_binaries_preprocess(d):
>   *** 0003:   
> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
>   0005:
>   0006:relocatable_binaries_preprocess(d)
>   0007:
> File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
>   0003:
>   0004:for bindir in bindirs:
>   0005:#bb.note ("Processing directory " + bindir)
>   0006:directory = path + "/" + bindir
>   *** 0007:process_dir (path, directory, d)
>   0008:
> File: 'chrpath.bbclass', lineno: 44, function: process_dir
>   0040:perms = None
>   0041:else:
>   0042:# Temporarily make the file writeable so we can
> chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
>   *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir,
> d) 0045:
>   0046:if perms:
>   0047:os.chmod(fpath, perms)
>   0048:
> File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
>   0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir,
> d): 0002:import subprocess as sub
>   0003:
>   *** 0004:p = sub.Popen([cmd, '-l',
> fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out = p.communicate()
>   0006:# If returned succesfully, process stderr for results
>   0007:if p.returncode != 0:
>   0008:return
> File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
>   0706:cwd, env, universal_newlines,
>   0707:startupinfo, creationflags,
> shell, to_close, 0708:p2cread, p2cwrite,
>   0709:c2pread, c2pwrite,
>   *** 0710:errread, errwrite)
>   0711:except Exception:
>   0712:# Preserve original exception in case os.close
> raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
> 0714:
> File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:
> _execute_child 1331:except OSError as e:
>   1332:if e.errno != errno.ECHILD:
>   1333:raise
>   1334:child_exception = pickle.loads(data)
>   *** 1335:raise child_exception
>   1336:
>   1337:
>   1338:def _handle_exitstatus(self, sts,
> _WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
> _WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
> directory
> 
> ERROR: Function failed: relocatable_binaries_preprocess
> ERROR: Logfile of failure stored in:
> /local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.6
> 4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
> (/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb,
> do_populate_sysroot) failed with exit code '1'
> ===
> ==
> 
> Sadly, I don't see enough info in this error trace to really tell me
> what file/directory is missing (i.e. what the real problem is)
> 
> I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
> Note that this is a build in a older tree, one which I've been using
> successfully (as you can tell) since late 2014.
> 
> Interestingly, I can build using the same meta-data on 

[yocto] bitbake error

[Gary Thomas]

When trying to build using latest Poky/Yocto master 
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e)
I'm getting this error:

=
Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO= "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in 
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'relocatable_binaries_preprocess', lineno: 6, function: 
 0002:def relocatable_binaries_preprocess(d):
 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/sysroot-destdir/'),
 d)
 0004:
 0005:
 *** 0006:relocatable_binaries_preprocess(d)
 0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function: 
relocatable_binaries_preprocess
 0001:
 0002:def relocatable_binaries_preprocess(d):
 *** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/sysroot-destdir/'),
 d)
 0004:
 0005:
 0006:relocatable_binaries_preprocess(d)
 0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
 0003:
 0004:for bindir in bindirs:
 0005:#bb.note ("Processing directory " + bindir)
 0006:directory = path + "/" + bindir
 *** 0007:process_dir (path, directory, d)
 0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir
 0040:perms = None
 0041:else:
 0042:# Temporarily make the file writeable so we can 
chrpath it
 0043:os.chmod(fpath, perms|stat.S_IRWXU)
 *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir, d)
 0045:
 0046:if perms:
 0047:os.chmod(fpath, perms)
 0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
 0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir, d):
 0002:import subprocess as sub
 0003:
 *** 0004:p = sub.Popen([cmd, '-l', fpath],stdout=sub.PIPE,stderr=sub.PIPE)
 0005:err, out = p.communicate()
 0006:# If returned succesfully, process stderr for results
 0007:if p.returncode != 0:
 0008:return
File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
 0706:cwd, env, universal_newlines,
 0707:startupinfo, creationflags, shell, 
to_close,
 0708:p2cread, p2cwrite,
 0709:c2pread, c2pwrite,
 *** 0710:errread, errwrite)
 0711:except Exception:
 0712:# Preserve original exception in case os.close raises.
 0713:exc_type, exc_value, exc_trace = sys.exc_info()
 0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function: _execute_child
 1331:except OSError as e:
 1332:if e.errno != errno.ECHILD:
 1333:raise
 1334:child_exception = pickle.loads(data)
 *** 1335:raise child_exception
 1336:
 1337:
 1338:def _handle_exitstatus(self, sts, _WIFSIGNALED=os.WIFSIGNALED,
 1339:_WTERMSIG=os.WTERMSIG, _WIFEXITED=os.WIFEXITED,
Exception: OSError: [Errno 2] No such file or directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in: 
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_populate_sysroot.12966
ERROR: Task 11 
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb, 
do_populate_sysroot) failed with exit code '1'
=

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
Note that this is a build in a older tree, one which I've been using 
successfully
(as you can tell) since late 2014.

Interestingly, I can build using the same meta-data on a different build
box!

I get the same error when using a totally fresh tree, so I'm really
perplexed by this one...

--

Gary Thomas |  Consulting for t

Re: [yocto] bitbake error during image build for VIA Embedded VAB-820 BSP

[Trevor Woerner]

I tried the build myself, following the instructions to which you 
linked. There were a couple "gotchas" along the way (noted, with 
work-arounds, below [*]), but otherwise the build succeeded. Could you 
try it again, following the steps exactly, and if it fails again, please 
list out exactly everything you typed?


It's great seeing more projects and companies using Yocto, although I 
have to say VIA's use is a little different. I would be nice if they 
integrated with the project in a more "conventional" way.



[*]

1. lttng fails due to some race condition, it tries to run some 
kernel/script program before it has compiled it. If it fails for you, 
simply re-start the build a second time and it should succeed.


2. gtkperf fails to build. Fortunately the gtkperf version in 
meta-openembedded's master is the same as the one from VIA's BSP. Delete 
the one from the BSP (rm -fr 
sources/meta-fsl-bsp-release/imx/meta-fsl-demos/recipes-graphics/gtkperf) and 
replace it with the one from today's master branch of 
meta-openembedded/meta-oe/recipes-graphics/gtkperf

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

[yocto] bitbake error during image build for VIA Embedded VAB-820 BSP

[Vertical Limit]

Hi all,

I am currently trying to compile the Yocto-based BSP (
https://d2phydb95qamfd.cloudfront.net/products/software/vab-820/Linux+HMI+Solution+Pack+BSP/AMOS-820_VAB-820_HMI_SolutionPack_V2.0.1_20150401(Beta_version).zip)
for the VIA Embedded VAB-820 board (
http://www.viaembedded.com/en/boards/pico-itx/vab-820/). Exactly following
the documentation of the VIA webpage (
https://s3-eu-west-1.amazonaws.com/viaembeddeddownloads/products/docs/vab-820/Linux+HMI+Solution+Pack+Development+Guide/AMOS-820_VAB-820_HMI_SolutionPack_V2.0.1_Development+Guide_V1.03_20150401.pdf),
I get a strange error when trying to build an image using "bitbake
via-image-x11" (refer to section 3.3 in the documentation). The output can
be found in the following pastebin:

http://pastebin.com/EU83WMjc


Any ideas for the cause of this issue? Developing environment is Ubuntu
12.04.5 (64 Bit) LTS like proposed by the documentation. Many thanks!

Best regards,
Thomas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Tizen Build Using Yocto - bitbake error mesa_10.1.3.bb,do_configure

[Anoop]

Hi

Yocto Build for minimal image

Summary: 1 task failed:
  /home/sfm/YOCTO/poky/meta/recipes-graphics/mesa/mesa_10.1.3.bb, 
do_configure

*
configure: error: Package requirements (x11-xcb xcb-dri2 >= 1.8 xcb-xfixes) 
were not met:

No package 'x11-xcb' found
No package 'xcb-dri2' found
No package 'xcb-xfixes' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XCB_DRI2_CFLAGS
and XCB_DRI2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

+ '[' 1 '!=' 0 ']'
+ echo 'Configure failed. The contents of all config.log files follows to 
aid debugging'
Configure failed. The contents of all config.log files follows to aid 
debugging
+ find /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/mesa/2_10.1.3-r0/Mesa-10.1.3 -name config.log -print -exec cat '{}' 
';'

+ bbfatal 'oe_runconf failed'
+ echo 'ERROR: oe_runconf failed'
ERROR: oe_runconf failed
+ exit 1
+ bb_exit_handler
+ ret=1
+ case $ret in
+ case $BASH_VERSION in
+ echo 'WARNING: /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-
poky-linux-gnueabi/mesa/2_10.1.3-r0/temp/run.do_configure.12232:1 exit 1 
from
  exit' 1
WARNING: /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/mesa/2_10.1.3-r0/temp/run.do_configure.12232:1 exit 1 from
  exit 1
+ exit 1

CTO/build/tmp/sysroots/i686-linux/usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether arm-poky-linux-gnueabi-gcc  -march=armv7-a -mthumb-
interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --
sysroot=/home/sfm/YOCTO/build/tmp/sysroots/imx6qsabreauto supports -
Werror=missing-prototypes... yes
checking whether arm-poky-linux-gnueabi-gcc  -march=armv7-a -mthumb-
interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --
sysroot=/home/sfm/YOCTO/build/tmp/sysroots/imx6qsabreauto supports -
fvisibility=hidden... yes
checking whether arm-poky-linux-gnueabi-g++  -march=armv7-a -mthumb-
interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --
sysroot=/home/sfm/YOCTO/build/tmp/sysroots/imx6qsabreauto supports -
fvisibility=hidden... yes
checking whether C compiler accepts -msse4.1... no
checking whether to enable assembly... no, platform not supported
checking for dlopen... no
checking for dlopen in -ldl... yes
checking for clock_gettime... yes
checking for posix_memalign... (cached) yes
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... no
configure: WARNING: GLX disabled, disabling Xlib-GLX
checking for LIBDRM... yes
checking for LIBUDEV... yes
checking for EXPAT... yes
checking for mincore... yes
checking for XCB_DRI2... no
configure: error: Package requirements (x11-xcb xcb-dri2 >= 1.8 xcb-xfixes) 
were not met:

No package 'x11-xcb' found
No package 'xcb-dri2' found
No package 'xcb-xfixes' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XCB_DRI2_CFLAGS
and XCB_DRI2_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
+ '[' 1 '!=' 0 ']'
+ echo 'Configure failed. The contents of all config.log files follows to 
aid debugging'
Configure failed. The contents of all config.log files follows to aid 
debugging
+ find /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/mesa/2_10.1.3-r0/Mesa-10.1.3 -name config.log -print -exec cat '{}' 
';'
+ bbfatal 'oe_runconf failed'
+ echo 'ERROR: oe_runconf failed'
ERROR: oe_runconf failed
+ exit 1
+ bb_exit_handler
+ ret=1
+ case $ret in
+ case $BASH_VERSION in
+ echo 'WARNING: /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-
poky-linux-gnueabi/mesa/2_10.1.3-r0/temp/run.do_configure.12232:1 exit 1 
from
  exit' 1
WARNING: /home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/mesa/2_10.1.3-r0/temp/run.do_configure.12232:1 exit 1 from
  exit 1
+ exit 1
ERROR: Function failed: do_configure (log file is located at 
/home/sfm/YOCTO/build/tmp/work/cortexa9hf-vfp-neon-mx6-poky-linux-
gnueabi/mesa/2_10.1.3-r0/temp/log.do_configure.12232)

Please give inputs to resolve the error

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

Re: [yocto] Bitbake error for rpm-native -- do compile failed

[Anoop Babu]

Dear Ross,

My apologies for pushing all issues to yocto forum. Can you please let me
know the meta-tizen  forum.

I had started bitbake procedure after cloning below mentioned repo

git clone ssh://${YOUR_TIZEN_ID}@review.tizen.org:29418/scm/bb/meta-tizen

Today did a fetch from tizen branch. I saw lot of changes being pulled in.
But unfortunately the rpm-native compile issue did not goaway.

Can you confirm this is the same repo to fetch latest revisions as
mentioned by you. Is it to any specific branch?

Thanks once again for the wonderful support.

best regards
Anoop


Best regards
 A.B
P Please think about the environment before printing this e-mail

*7 Switch off as you go | qAlways recycle | P Save a tree...please don't
print this e-mail unless you really need to.*


On Thu, Jul 24, 2014 at 7:06 PM, Burton, Ross  wrote:

> On 24 July 2014 14:29, Anoop  wrote:
> > + export CCFLAGS+= -fPIC
> > /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> > r0/temp/run.do_compile.26826: 120: export: CCFLAGS+: bad variable name
>
> += is a bash extension and those scripts are not running under bash.
>
> This has been fixed in meta-tizen.  *Please* fetch the latest revisions.
>
> Also, this isn't the best list for problems with meta-tizen as
> meta-tizen isn't part of the Yocto project - you'll be better off
> contacting the maintainers directly or filing bugs in their issue
> tracker.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Anoop Babu]

thank you I applied the patch the earlier stated error is not seen . but I
have hit on another error.

Patch redhat-portability.diff does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in:
/home/sfm/yocto_temp/build/tmp/work/i686-linux/elfutils-native/0.158-r0/temp/log.do_patch.3531
ERROR: Task 993
(virtual:native:/home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/
elfutils_0.158.bb, do_patch) failed with exit code '1'

have come across this error?

Best regards
 A.B
P Please think about the environment before printing this e-mail

*7 Switch off as you go | qAlways recycle | P Save a tree...please don't
print this e-mail unless you really need to.*


On Thu, Jul 24, 2014 at 3:14 AM, Burton, Ross  wrote:

> On 23 July 2014 07:51, Anoop  wrote:
> > patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> > directory
>
> I just re-read this mail and remembered that this was a different
> problem with rpm-native, and I fixed it in oe-core/poky.  Their fork
> of poky has been updated to incorporate the fix but if you can't
> upgrade then cherry-pick this commit:
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=442efc3959a65fc9da73f79b3afda95d1cffadf3
>
> Sorry for the wrong reply at first, there are several ways that the
> meta-tizen rpm can fail... :/
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Bitbake error for rpm-native -- do compile failed

[Burton, Ross]

On 25 July 2014 13:42, Anoop Babu  wrote:
> My apologies for pushing all issues to yocto forum. Can you please let me
> know the meta-tizen  forum.

As far as I'm aware you'll have to email the maintainers directly.

> I had started bitbake procedure after cloning below mentioned repo
>
> git clone ssh://${YOUR_TIZEN_ID}@review.tizen.org:29418/scm/bb/meta-tizen
>
> Today did a fetch from tizen branch. I saw lot of changes being pulled in.
> But unfortunately the rpm-native compile issue did not goaway.

I can confirm that they re-introduced this bug, I've reported it to them.

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

Re: [yocto] Bitbake error for rpm-native -- do compile failed

[Burton, Ross]

On 24 July 2014 14:29, Anoop  wrote:
> + export CCFLAGS+= -fPIC
> /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/temp/run.do_compile.26826: 120: export: CCFLAGS+: bad variable name

+= is a bash extension and those scripts are not running under bash.

This has been fixed in meta-tizen.  *Please* fetch the latest revisions.

Also, this isn't the best list for problems with meta-tizen as
meta-tizen isn't part of the Yocto project - you'll be better off
contacting the maintainers directly or filing bugs in their issue
tracker.

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

[yocto] Bitbake error for rpm-native -- do compile failed

[Anoop]

bitbake for imx6qsabreauto

command used 
bitbake -v tizen-common-core-image-minimal-dev

Summary: 1 task failed:
  virtual:native:/home/sfm/yocto_temp/meta-tizen/recipes-
tizen/rpm/rpm_git.bb, do_compile

+ CPPFLAGS=-isystem/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include -I/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include/nss3 
+ export CPPFLAGS
+ export LDFLAGS=-L/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/lib -L/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-O1 -Wl,-
Bsymbolic-functions -ffunction-sections
+ export CCFLAGS+= -fPIC 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/run.do_compile.26826: 120: export: CCFLAGS+: bad variable name
+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2

ERROR: Function failed: do_compile (log file is located at 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/log.do_compile.26826)


*do compile log file*
DEBUG: Executing shell function do_compile
+ 
cd
 /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git


+ 
do_compile


+ 
cd
 /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git


+ 
LANG=C


+ 
export
 LANG


+ 
unset
 DISPLAY


+ 
LD_AS_NEEDED=1


+ 
export
 LD_AS_NEEDED


+ 
pkg-config
 --cflags
 nss


+ CPPFLAGS=-isystem/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include -I/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include/nss3 
+ export CPPFLAGS
+ export LDFLAGS=-L/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/lib -L/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-O1 -Wl,-
Bsymbolic-functions -ffunction-sections
+ export CCFLAGS+= -fPIC 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/run.do_compile.26826: 120: export: CCFLAGS+: bad variable name
+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2

+ cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
+ do_compile
+ cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
+ LANG=C
+ export LANG
+ unset DISPLAY
+ LD_AS_NEEDED=1
+ export LD_AS_NEEDED
+ pkg-config --cflags nss
+ CPPFLAGS=-isystem/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include -I/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/include/nss3 
+ export CPPFLAGS
+ export LDFLAGS=-L/home/sfm/yocto_temp/build/tmp/sysroots/i686-
linux/usr/lib -L/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath-link,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib -Wl,-
rpath,/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/lib -Wl,-O1 -Wl,-
Bsymbolic-functions -ffunction-sections
+ export CCFLAGS+= -fPIC 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/run.do_compile.26826: 120: export: CCFLAGS+: bad variable name
+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2
ERROR: Function failed: do_compile (log file is located at 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/log.do_compile.26826)

Request inputs to resolve this error

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

Re: [yocto] Bitbake error for elfutils-native

[Anoop]

Thank you Ross for the wonderful support.
I cherrypicked the commit. The issue is resolved now.

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

Re: [yocto] Bitbake error for elfutils-native

[Burton, Ross]

On 24 July 2014 10:25, Anoop  wrote:
> Ross
> many thanks for the valuable input.
> I had been building tizen with yocto based on the following link.
>
> https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto
>
> For poky it is mentioned to use
> git clone https://github.com/eurogiciel-oss/poky.git
>
> I think the redhat-portability.diff file in the path
> /home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils-0.158
> as well as
> /home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils
> might not have been updated based on the poky commit
> 52a6d20519870103134166d91e22d21fd736195d.

https://github.com/eurogiciel-oss/poky/commit/52a6d20519870103134166d91e22d21fd736195d

It's there - you need to pull the latest commits.

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

Re: [yocto] Bitbake error for elfutils-native

[Anoop]

Burton, Ross  writes:

> 
> On 24 July 2014 08:05, Anoop  wrote:
> > Patch redhat-portability.diff does not apply (enforce with -f)
> 
> Please update your poky, this has been fixed already and the
> meta-tizen fork of Poky has already integrated this fix.
> 
> (poky commit 52a6d20519870103134166d91e22d21fd736195d)
> 
> Ross

Ross
many thanks for the valuable input.
I had been building tizen with yocto based on the following link.

https://wiki.tizen.org/wiki/Build_Tizen_with_Yocto

For poky it is mentioned to use
git clone https://github.com/eurogiciel-oss/poky.git

I think the redhat-portability.diff file in the path 
/home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils-0.158
as well as
/home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils
might not have been updated based on the poky commit 
52a6d20519870103134166d91e22d21fd736195d.


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

Re: [yocto] Bitbake error for elfutils-native

[Burton, Ross]

On 24 July 2014 08:05, Anoop  wrote:
> Patch redhat-portability.diff does not apply (enforce with -f)

Please update your poky, this has been fixed already and the
meta-tizen fork of Poky has already integrated this fix.

(poky commit 52a6d20519870103134166d91e22d21fd736195d)

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

Re: [yocto] Bitbake error for elfutils-native

[Joseph Andrew de la Peña]

Good day Anoop,

Error is in do_patch task when applying patch for configure. Please check
the hashes in your patch if it's compatible with the HEAD or some upstream
changes for configure.

Thanks,
Joseph


On Thu, Jul 24, 2014 at 3:05 PM, Anoop  wrote:

> bitbake for imx6qsabreauto
>
> command used
> bitbake -v tizen-common-core-image-minimal-dev
>
> I have applied fix to - meta/classes/patch.bbclass
> i.e
> + del os.environ['TMPDIR']
>
> ***Error Log
> ERROR: Command Error: exit status: 1  Output:
> Applying patch redhat-portability.diff
> patching file backends/ChangeLog
> patching file backends/Makefile.am
> patching file backends/Makefile.in
> patching file ChangeLog
> patching file config/ChangeLog
> patching file config/eu.am
> patching file config/Makefile.in
> Hunk #1 succeeded at 147 (offset 1 line).
> Hunk #2 succeeded at 179 (offset 1 line).
> patching file config.h.in
> patching file configure
> Hunk #1 FAILED at 661.
> Hunk #2 FAILED at 678.
> Hunk #3 FAILED at 802.
> Hunk #4 FAILED at 1461.
> Hunk #5 succeeded at 4943 with fuzz 1 (offset 234 lines).
> Hunk #6 FAILED at 4869.
> Hunk #7 succeeded at 5535 (offset 256 lines).
> Hunk #8 FAILED at 6015.
> Hunk #9 succeeded at 7010 with fuzz 1 (offset 257 lines).
> 6 out of 9 hunks FAILED -- rejects in file configure
> patching file configure.ac
> patching file lib/ChangeLog
> patching file lib/eu-config.h
> patching file lib/Makefile.in
> patching file libasm/ChangeLog
> patching file libasm/Makefile.in
> patching file libcpu/ChangeLog
> patching file libcpu/i386_disasm.c
> patching file libcpu/Makefile.in
> patching file libdw/ChangeLog
> patching file libdw/dwarf_begin_elf.c
> patching file libdw/libdw.h
> patching file libdw/Makefile.in
> patching file libdwfl/ChangeLog
> patching file libdwfl/linux-core-attach.c
> patching file libdwfl/linux-pid-attach.c
> patching file libdwfl/Makefile.in
> patching file libebl/ChangeLog
> patching file libebl/Makefile.in
> patching file libelf/ChangeLog
> patching file libelf/common.h
> patching file libelf/gnuhash_xlate.h
> patching file libelf/Makefile.in
> patching file m4/Makefile.in
> patching file Makefile.in
> patching file src/addr2line.c
> patching file src/ChangeLog
> patching file src/findtextrel.c
> patching file src/ld.h
> patching file src/Makefile.am
> patching file src/Makefile.in
> patching file src/readelf.c
> patching file src/strings.c
> patching file src/strip.c
> patching file tests/backtrace.c
> patching file tests/ChangeLog
> patching file tests/line2addr.c
> patching file tests/Makefile.in
> Patch redhat-portability.diff does not apply (enforce with -f)
> ERROR: Function failed: patch_do_patch
> ERROR: Logfile of failure stored in:
> /home/sfm/yocto_temp/build/tmp/work/i686-linux/elfutils-native/0.158-
> r0/temp/log.do_patch.3531
> ERROR: Task 993 (virtual:native:/home/sfm/yocto_temp/poky/meta/recipes-
> devtools/elfutils/elfutils_0.158.bb, do_patch) failed with exit code '1'
>
>
> do patch log file
>
> /home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils/
> /home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/files/
> NOTE: Applying patch 'redhat-portability.diff' (../poky/meta/recipes-
> devtools/elfutils/elfutils-0.158/redhat-portability.diff)
> ERROR: Command Error: exit status: 1  Output:
> Applying patch redhat-portability.diff
> patching file backends/ChangeLog
> patching file backends/Makefile.am
> patching file backends/Makefile.in
> patching file ChangeLog
> patching file config/ChangeLog
> patching file config/eu.am
> patching file config/Makefile.in
> Hunk #1 succeeded at 147 (offset 1 line).
> Hunk #2 succeeded at 179 (offset 1 line).
> patching file config.h.in
> patching file configure
> Hunk #1 FAILED at 661.
> Hunk #2 FAILED at 678.
> Hunk #3 FAILED at 802.
> Hunk #4 FAILED at 1461.
> Hunk #5 succeeded at 4943 with fuzz 1 (offset 234 lines).
> Hunk #6 FAILED at 4869.
> Hunk #7 succeeded at 5535 (offset 256 lines).
> Hunk #8 FAILED at 6015.
> Hunk #9 succeeded at 7010 with fuzz 1 (offset 257 lines).
> 6 out of 9 hunks FAILED -- rejects in file configure
> patching file configure.ac
> patching file lib/ChangeLog
> patching file lib/eu-config.h
> patching file lib/Makefile.in
> patching file libasm/ChangeLog
> patching file libasm/Makefile.in
> patching file libcpu/ChangeLog
> patching file libcpu/i386_disasm.c
> patching file libcpu/Makefile.in
> patching file libdw/ChangeLog
> patching file libdw/dwarf_begin_elf.c
> patching file libdw/libdw.h
> patching file libdw/Makefile.in
> patching file libdwfl/ChangeLog
> patching file libdwfl/linux-core-attach.c
> patching file libdwfl/linux-pid-attach.c
> patching file libdwfl/Makefile.in
> patching file libebl/ChangeLog
> patching file libebl/Makefile.in
> patching file libelf/ChangeLog
> patching file libelf/common.h
> patching file libelf/gnuhash_xlate.h
> patching file libelf/Makefile.in
> patching file m4/Makefile.in
> patching file Makefile.in
> patchi

[yocto] Bitbake error for elfutils-native

[Anoop]

bitbake for imx6qsabreauto

command used 
bitbake -v tizen-common-core-image-minimal-dev

I have applied fix to - meta/classes/patch.bbclass
i.e 
+ del os.environ['TMPDIR']

***Error Log
ERROR: Command Error: exit status: 1  Output:
Applying patch redhat-portability.diff
patching file backends/ChangeLog
patching file backends/Makefile.am
patching file backends/Makefile.in
patching file ChangeLog
patching file config/ChangeLog
patching file config/eu.am
patching file config/Makefile.in
Hunk #1 succeeded at 147 (offset 1 line).
Hunk #2 succeeded at 179 (offset 1 line).
patching file config.h.in
patching file configure
Hunk #1 FAILED at 661.
Hunk #2 FAILED at 678.
Hunk #3 FAILED at 802.
Hunk #4 FAILED at 1461.
Hunk #5 succeeded at 4943 with fuzz 1 (offset 234 lines).
Hunk #6 FAILED at 4869.
Hunk #7 succeeded at 5535 (offset 256 lines).
Hunk #8 FAILED at 6015.
Hunk #9 succeeded at 7010 with fuzz 1 (offset 257 lines).
6 out of 9 hunks FAILED -- rejects in file configure
patching file configure.ac
patching file lib/ChangeLog
patching file lib/eu-config.h
patching file lib/Makefile.in
patching file libasm/ChangeLog
patching file libasm/Makefile.in
patching file libcpu/ChangeLog
patching file libcpu/i386_disasm.c
patching file libcpu/Makefile.in
patching file libdw/ChangeLog
patching file libdw/dwarf_begin_elf.c
patching file libdw/libdw.h
patching file libdw/Makefile.in
patching file libdwfl/ChangeLog
patching file libdwfl/linux-core-attach.c
patching file libdwfl/linux-pid-attach.c
patching file libdwfl/Makefile.in
patching file libebl/ChangeLog
patching file libebl/Makefile.in
patching file libelf/ChangeLog
patching file libelf/common.h
patching file libelf/gnuhash_xlate.h
patching file libelf/Makefile.in
patching file m4/Makefile.in
patching file Makefile.in
patching file src/addr2line.c
patching file src/ChangeLog
patching file src/findtextrel.c
patching file src/ld.h
patching file src/Makefile.am
patching file src/Makefile.in
patching file src/readelf.c
patching file src/strings.c
patching file src/strip.c
patching file tests/backtrace.c
patching file tests/ChangeLog
patching file tests/line2addr.c
patching file tests/Makefile.in
Patch redhat-portability.diff does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/elfutils-native/0.158-
r0/temp/log.do_patch.3531
ERROR: Task 993 (virtual:native:/home/sfm/yocto_temp/poky/meta/recipes-
devtools/elfutils/elfutils_0.158.bb, do_patch) failed with exit code '1'


do patch log file

/home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/elfutils/
/home/sfm/yocto_temp/poky/meta/recipes-devtools/elfutils/files/
NOTE: Applying patch 'redhat-portability.diff' (../poky/meta/recipes-
devtools/elfutils/elfutils-0.158/redhat-portability.diff)
ERROR: Command Error: exit status: 1  Output:
Applying patch redhat-portability.diff
patching file backends/ChangeLog
patching file backends/Makefile.am
patching file backends/Makefile.in
patching file ChangeLog
patching file config/ChangeLog
patching file config/eu.am
patching file config/Makefile.in
Hunk #1 succeeded at 147 (offset 1 line).
Hunk #2 succeeded at 179 (offset 1 line).
patching file config.h.in
patching file configure
Hunk #1 FAILED at 661.
Hunk #2 FAILED at 678.
Hunk #3 FAILED at 802.
Hunk #4 FAILED at 1461.
Hunk #5 succeeded at 4943 with fuzz 1 (offset 234 lines).
Hunk #6 FAILED at 4869.
Hunk #7 succeeded at 5535 (offset 256 lines).
Hunk #8 FAILED at 6015.
Hunk #9 succeeded at 7010 with fuzz 1 (offset 257 lines).
6 out of 9 hunks FAILED -- rejects in file configure
patching file configure.ac
patching file lib/ChangeLog
patching file lib/eu-config.h
patching file lib/Makefile.in
patching file libasm/ChangeLog
patching file libasm/Makefile.in
patching file libcpu/ChangeLog
patching file libcpu/i386_disasm.c
patching file libcpu/Makefile.in
patching file libdw/ChangeLog
patching file libdw/dwarf_begin_elf.c
patching file libdw/libdw.h
patching file libdw/Makefile.in
patching file libdwfl/ChangeLog
patching file libdwfl/linux-core-attach.c
patching file libdwfl/linux-pid-attach.c
patching file libdwfl/Makefile.in
patching file libebl/ChangeLog
patching file libebl/Makefile.in
patching file libelf/ChangeLog
patching file libelf/common.h
patching file libelf/gnuhash_xlate.h
patching file libelf/Makefile.in
patching file m4/Makefile.in
patching file Makefile.in
patching file src/addr2line.c
patching file src/ChangeLog
patching file src/findtextrel.c
patching file src/ld.h
patching file src/Makefile.am
patching file src/Makefile.in
patching file src/readelf.c
patching file src/strings.c
patching file src/strip.c
patching file tests/backtrace.c
patching file tests/ChangeLog
patching file tests/line2addr.c
patching file tests/Makefile.in
Patch redhat-portability.diff does not apply (enforce with -f)
DEBUG: Python function patch_do_patch finished
DEBUG: Python function do_patch

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Anoop]

Burton, Ross  writes:

> 
> On 23 July 2014 07:51, Anoop  wrote:
> > patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> > directory
> 
> I just re-read this mail and remembered that this was a different
> problem with rpm-native, and I fixed it in oe-core/poky.  Their fork
> of poky has been updated to incorporate the fix but if you can't
> upgrade then cherry-pick this commit:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?
id=442efc3959a65fc9da73f79b3afda95d1cffadf3
> 
> Sorry for the wrong reply at first, there are several ways that the
> meta-tizen rpm can fail... :/
> 
> Ross

Once again thank you ross I could resolve the error with the stated changes 
you had mentioned




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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Burton, Ross]

On 23 July 2014 07:51, Anoop  wrote:
> patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> directory

I just re-read this mail and remembered that this was a different
problem with rpm-native, and I fixed it in oe-core/poky.  Their fork
of poky has been updated to incorporate the fix but if you can't
upgrade then cherry-pick this commit:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=442efc3959a65fc9da73f79b3afda95d1cffadf3

Sorry for the wrong reply at first, there are several ways that the
meta-tizen rpm can fail... :/

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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Burton, Ross]

On 23 July 2014 11:00, Anoop  wrote:
> Thank you for the inputs.
> So until I over come this error I need to do bitbake rpm-native -cclean and
> then re-run bitbake tizen-common-core-image-minimal-dev. ?
> I'm asking this since i'm continuously getting task error on meta-tizen rpm
> receipt.

That was how I fixed it when I hit this problem.  I suggest contacting
the maintainers of meta-tizen directly, they're probably not on this
mailing list.

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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Anoop]

Burton, Ross  writes:

> 
> On 23 July 2014 07:51, Anoop  wrote:
> > patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> > directory
> 
> This is a bug in the meta-tizen rpm package.  Until they fix it you'll
> have to do bitbake rpm-native -cclean and then re-run bitbake
> tizen-common-core-image-minimal-dev.
> 
> Ross

Good day Ross

Thank you for the inputs.
So until I over come this error I need to do bitbake rpm-native -cclean and 
then re-run bitbake tizen-common-core-image-minimal-dev. ?
I'm asking this since i'm continuously getting task error on meta-tizen rpm 
receipt.

Best regards
Anoop



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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Anoop]

Good day Joseph Andrew

Thank you for the inputs.

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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Burton, Ross]

On 23 July 2014 07:51, Anoop  wrote:
> patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> directory

This is a bug in the meta-tizen rpm package.  Until they fix it you'll
have to do bitbake rpm-native -cclean and then re-run bitbake
tizen-common-core-image-minimal-dev.

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

Re: [yocto] Yocto Bitbake Error - rmp-native task failure

[Joseph Andrew de la Peña]

Good day Anoop,

Error is from do_patch task for rpm-native unit:
patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
directory

Please verify in your recipe all the SRC_URIs (patches) to be applied.
Could be that your SRCREV and patches are in conflict. The odd thing is why
the patch -p0 is not specifying a patch file.

To sum it up, please check the rpm-native recipe.

Thanks,
Joseph


On Wed, Jul 23, 2014 at 2:51 PM, Anoop  wrote:

>
> I gave bitbake for imx6qsabreauto
>
> command used
> bitbake -v tizen-common-core-image-minimal-dev
>
>
> below is the error section from the log
> + patch -p0
>
> patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> directory
>
> + bb_exit_handler
> + ret=2
> + echo WARNING: exit code 2 from a shell command.
> WARNING: exit code 2 from a shell command.
> + exit 2
>
> ERROR: Function failed: do_prep (log file is located at
> /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/temp/log.do_patch.32228)
> /usr/bin/install -c -m 644 ./Lib/test/test_bool.py
> /home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib/python2.7/test
>
> ERROR: Logfile of failure stored in:
> /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/temp/log.do_patch.32228
> NOTE: recipe rpm-native-git-r0: task do_patch: Failed
> ERROR: Task 85 (virtual:native:/home/sfm/yocto_temp/meta-tizen/recipes-
> tizen/rpm/rpm_git.bb, do_patch) failed with exit code '1'
>
> Error log from patch file
> +
> chmod
>  -Rf
>  a+rX,u+w,g-w,o-w
>  /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
>
>
> + cp /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/git/packaging/rpm.manifest .
>
> + rm -rf sqlite
>
> + tar xjf /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/git/packaging/db-4.8.30.tar.bz2
>
> + ln -s db-4.8.30 db
>
> + chmod -R u+w db/LICENSE db/README db/btree db/build_brew db/build_s60
> db/build_unix db/build_vxworks db/build_wince db/build_windows db/clib
> db/common db/crypto db/csharp db/cxx db/db db/db185 db/db_archive
> db/db_checkpoint db/db_deadlock db/db_dump db/db_dump185 db/db_hotbackup
> db/db_load db/db_printlog db/db_recover db/db_sql db/db_stat db/db_upgrade
> db/db_verify db/dbinc db/dbinc_auto db/dbm db/dbreg db/dist db/docs
> db/docs_src db/env db/examples_c db/examples_csharp db/examples_cxx
> db/examples_java db/examples_stl db/fileops db/hash db/hmac db/hsearch
> db/java db/libdb_csharp db/libdb_java db/lock db/log db/mod_db4 db/mp
> db/mutex db/os db/os_brew db/os_qnx db/os_s60 db/os_vxworks db/os_windows
> db/perl db/php_db4 db/qam db/rep db/repmgr db/sequence db/stl db/tcl
> db/test
> db/test_micro db/test_stl db/txn
>
> + rm -f rpmdb/db.h
>
> + patch -p0
>
> patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> directory
>
> + bb_exit_handler
> + ret=2
> + echo WARNING: exit code 2 from a shell command.
> WARNING: exit code 2 from a shell command.
> + exit 2
>
> + cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
> + do_prep
> + cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
> + chmod -Rf a+rX,u+w,g-w,o-w /home/sfm/yocto_temp/build/tmp/work/i686-
> linux/rpm-native/git-r0/git
> + cp /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/git/packaging/rpm.manifest .
> + rm -rf sqlite
> + tar xjf /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/git/packaging/db-4.8.30.tar.bz2
> + ln -s db-4.8.30 db
> + chmod -R u+w db/LICENSE db/README db/btree db/build_brew db/build_s60
> db/build_unix db/build_vxworks db/build_wince db/build_windows db/clib
> db/common db/crypto db/csharp db/cxx db/db db/db185 db/db_archive
> db/db_checkpoint db/db_deadlock db/db_dump db/db_dump185 db/db_hotbackup
> db/db_load db/db_printlog db/db_recover db/db_sql db/db_stat db/db_upgrade
> db/db_verify db/dbinc db/dbinc_auto db/dbm db/dbreg db/dist db/docs
> db/docs_src db/env db/examples_c db/examples_csharp db/examples_cxx
> db/examples_java db/examples_stl db/fileops db/hash db/hmac db/hsearch
> db/java db/libdb_csharp db/libdb_java db/lock db/log db/mod_db4 db/mp
> db/mutex db/os db/os_brew db/os_qnx db/os_s60 db/os_vxworks db/os_windows
> db/perl db/php_db4 db/qam db/rep db/repmgr db/sequence db/stl db/tcl
> db/test
> db/test_micro db/test_stl db/txn
> + rm -f rpmdb/db.h
> + patch -p0
> patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or
> directory
> + bb_exit_handler
> + ret=2
> + echo WARNING: exit code 2 from a shell command.
> WARNING: exit code 2 from a shell command.
> + exit 2
> DEBUG: Python function do_patch finished
> ERROR: Function failed: do_prep (log file is located at
> /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
> r0/temp/log.do_patch.32228)
>
> can any one help on how to resolve this error
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listi

[yocto] Yocto Bitbake Error - rmp-native task failure

[Anoop]

I gave bitbake for imx6qsabreauto

command used 
bitbake -v tizen-common-core-image-minimal-dev


below is the error section from the log
+ patch -p0

patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or 
directory

+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2

ERROR: Function failed: do_prep (log file is located at 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/log.do_patch.32228)
/usr/bin/install -c -m 644 ./Lib/test/test_bool.py 
/home/sfm/yocto_temp/build/tmp/sysroots/i686-linux/usr/lib/python2.7/test

ERROR: Logfile of failure stored in: 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/log.do_patch.32228
NOTE: recipe rpm-native-git-r0: task do_patch: Failed
ERROR: Task 85 (virtual:native:/home/sfm/yocto_temp/meta-tizen/recipes-
tizen/rpm/rpm_git.bb, do_patch) failed with exit code '1'

Error log from patch file
+ 
chmod
 -Rf
 a+rX,u+w,g-w,o-w
 /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git


+ cp /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/git/packaging/rpm.manifest .

+ rm -rf sqlite

+ tar xjf /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/git/packaging/db-4.8.30.tar.bz2

+ ln -s db-4.8.30 db

+ chmod -R u+w db/LICENSE db/README db/btree db/build_brew db/build_s60 
db/build_unix db/build_vxworks db/build_wince db/build_windows db/clib 
db/common db/crypto db/csharp db/cxx db/db db/db185 db/db_archive 
db/db_checkpoint db/db_deadlock db/db_dump db/db_dump185 db/db_hotbackup 
db/db_load db/db_printlog db/db_recover db/db_sql db/db_stat db/db_upgrade 
db/db_verify db/dbinc db/dbinc_auto db/dbm db/dbreg db/dist db/docs 
db/docs_src db/env db/examples_c db/examples_csharp db/examples_cxx 
db/examples_java db/examples_stl db/fileops db/hash db/hmac db/hsearch 
db/java db/libdb_csharp db/libdb_java db/lock db/log db/mod_db4 db/mp 
db/mutex db/os db/os_brew db/os_qnx db/os_s60 db/os_vxworks db/os_windows 
db/perl db/php_db4 db/qam db/rep db/repmgr db/sequence db/stl db/tcl db/test 
db/test_micro db/test_stl db/txn

+ rm -f rpmdb/db.h

+ patch -p0

patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or 
directory

+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2

+ cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
+ do_prep
+ cd /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-r0/git
+ chmod -Rf a+rX,u+w,g-w,o-w /home/sfm/yocto_temp/build/tmp/work/i686-
linux/rpm-native/git-r0/git
+ cp /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/git/packaging/rpm.manifest .
+ rm -rf sqlite
+ tar xjf /home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/git/packaging/db-4.8.30.tar.bz2
+ ln -s db-4.8.30 db
+ chmod -R u+w db/LICENSE db/README db/btree db/build_brew db/build_s60 
db/build_unix db/build_vxworks db/build_wince db/build_windows db/clib 
db/common db/crypto db/csharp db/cxx db/db db/db185 db/db_archive 
db/db_checkpoint db/db_deadlock db/db_dump db/db_dump185 db/db_hotbackup 
db/db_load db/db_printlog db/db_recover db/db_sql db/db_stat db/db_upgrade 
db/db_verify db/dbinc db/dbinc_auto db/dbm db/dbreg db/dist db/docs 
db/docs_src db/env db/examples_c db/examples_csharp db/examples_cxx 
db/examples_java db/examples_stl db/fileops db/hash db/hmac db/hsearch 
db/java db/libdb_csharp db/libdb_java db/lock db/log db/mod_db4 db/mp 
db/mutex db/os db/os_brew db/os_qnx db/os_s60 db/os_vxworks db/os_windows 
db/perl db/php_db4 db/qam db/rep db/repmgr db/sequence db/stl db/tcl db/test 
db/test_micro db/test_stl db/txn
+ rm -f rpmdb/db.h
+ patch -p0
patch:  Can't create file /tmp/tmpT3pUSD/poMZnbmM : No such file or 
directory
+ bb_exit_handler
+ ret=2
+ echo WARNING: exit code 2 from a shell command.
WARNING: exit code 2 from a shell command.
+ exit 2
DEBUG: Python function do_patch finished
ERROR: Function failed: do_prep (log file is located at 
/home/sfm/yocto_temp/build/tmp/work/i686-linux/rpm-native/git-
r0/temp/log.do_patch.32228)

can any one help on how to resolve this error


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

[yocto] Bitbake: error in cachedpath.py

[Markus Eich]

Dear all,

I am setting up Yocto to compile my kernel for odroid xu. During the 
package phase of building the kernel, I get an error in cachedpath.py




DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing python function do_package
DEBUG: Executing python function package_get_auto_pr
DEBUG: Python function package_get_auto_pr finished
DEBUG: Executing python function perform_packagecopy
DEBUG: Python function perform_packagecopy finished
DEBUG: Executing python function split_and_strip_files
ERROR: Error executing a python function in 
/home/eich/yocto/poky/meta-odroid/recipes-kernel/linux/linux-hardkernel_3.4.bb:


The stack trace of python calls that resulted in this exception/failure 
was:

File: 'split_and_strip_files', lineno: 222, function: 
 0218:# End of strip
 0219:#
 0220:
 0221:
 *** 0222:split_and_strip_files(d)
 0223:
File: 'split_and_strip_files', lineno: 85, function: split_and_strip_files
 0081:if debugdir and debugdir in 
os.path.dirname(file[len(dvar):]):

 0082:continue
 0083:
 0084:try:
 *** 0085:ltarget = cpath.realpath(file, dvar, False)
 0086:s = cpath.lstat(ltarget)
 0087:except OSError as e:
 0088:(err, strerror) = e.args
 0089:if err != errno.ENOENT:
File: '/home/eich/yocto/poky/meta/lib/oe/cachedpath.py', lineno: 229, 
function: realpath
 0225:# be printed a backtrace with 100s of OSError 
exceptions

 0226:# else
 0227:raise OSError(errno.ELOOP,
 0228:  "too much recursions while 
resolving '%s'; loop in '%s'" %

 *** 0229:  (file, e.strerror))
 0230:
 0231:raise
 0232:
 0233:return file
Exception: OSError: [Errno 40] too much recursions while resolving 
'/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4-r0/package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release'; 
loop in 
'/home/eich/odroid/build/tmp/work/odroid_xu-poky-linux-gnueabi/linux-hardkernel/3.4-r0/package/usr/src/kernel/drivers/gpu/arm/mali400/ump/arch/arch-release'


DEBUG: Python function split_and_strip_files finished
DEBUG: Python function do_package finished
ERROR: Function failed: split_and_strip_files



Seems that the path is to deep?

To track the error, I have attached my kernel.bb


==
require recipes-kernel/linux/linux-yocto.inc

KERNEL_IMAGETYPE = "uImage"

COMPATIBLE_MACHINE = "odroid-xu"

LINUX_VERSION = "3.4.91"
LINUX_VERSION_EXTENSION = "-custom"

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-hardkernel-3.4:"

S = "${WORKDIR}/git"

# from where to fetch the kernel
KERNEL_REPO_OWNER ??= "hardkernel"
KERNEL_REPO_URI ??= "git://github.com/${KERNEL_REPO_OWNER}/linux.git"
KBRANCH = "odroidxu-3.4.y"

SRCREV = "${AUTOREV}"

SRC_URI = " \
  ${KERNEL_REPO_URI};nocheckout=1;branch=${KBRANCH} \
file://defconfig \
"


Any ideas ?

Cheers,

Markus

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