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

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 <antonius.r...@gmail.com 
<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"
<carlos.bejar-colo...@philips.com
<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 <antonius.r...@gmail.com
<mailto:antonius.r...@gmail.com>>
*Cc:* N: <yocto@yoctoproject.org <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 <antonius.r...@gmail.com
<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"
<ross.bur...@intel.com <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
<antonius.r...@gmail.com
<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
<antonius.r...@gmail.com
<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 27

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 > 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 <antonius.r...@gmail.com> 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 <antonius.r...@gmail.com>
> *Cc:* N: <yocto@yoctoproject.org>
> *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 <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" <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... 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 <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 (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 <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

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 <antonius.r...@gmail.com>
*Cc:* N: <yocto@yoctoproject.org>
*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 <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" <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... 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 <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 (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 <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









--
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 

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 <antonius.r...@gmail.com>
Cc: N: <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 
<antonius.r...@gmail.com<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" 
<ross.bur...@intel.com<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 
<antonius.r...@gmail.com<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 
<antonius.r...@gmail.com<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






T

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

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 

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 

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
> >> 

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

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

[Burton, Ross]

On 25 July 2014 13:42, Anoop Babu babu.an...@gmail.com 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

[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 ross.bur...@intel.com wrote:

 On 24 July 2014 14:29, Anoop babu.an...@gmail.com 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] 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 babu.an...@gmail.com 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
 patching file src/addr2line.c
 patching file src/ChangeLog
 patching file src/findtextrel.c
 patching file src/ld.h
 

Re: [yocto] Bitbake error for elfutils-native

[Burton, Ross]

On 24 July 2014 08:05, Anoop babu.an...@gmail.com 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

[Anoop]

Burton, Ross ross.burton@... writes:

 
 On 24 July 2014 08:05, Anoop babu.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 10:25, Anoop babu.an...@gmail.com 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]

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 rpm-native -- do compile failed

[Burton, Ross]

On 24 July 2014 14:29, Anoop babu.an...@gmail.com 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