[oe-users] First Build of OE Failing Repeatedly
Jeff Rush
jeff at taupro.com
Fri Aug 3 14:02:06 UTC 2007
Hi, I'm new to OE, coming to it from the OpenMoko community. However I'm
currently trying to build the plain vanilla OE for some other embedded devices
I have, and to develop the knowledge of how OE works in general.
I've not however been successful in getting my first build to complete. The
system seems to have a strong dependency on the various scattered source
sites, such that if any one of them is unavailable, a build failed. Yesterday
morning it was the domain for the CUPS software, and now for a couple of days
it is the ftp for the "lsof" software. Fortunately it falls bad to mirrors
for the "lsof" software but every one of them fails, with diverse connection
errors. Is this a known problem?
NOTE: Running task 789 of 1248 (ID: 489,
/var/hostings/OE/org.openembedded.dev/packages/lsof/lsof_4.77.bb, do_fetch)
NOTE: package lsof-4.77: started
NOTE: package lsof-4.77-r1: task do_fetch: started
NOTE: fetch ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.77.tar.bz2
--02:28:48-- ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving lsof.itap.purdue.edu... 128.210.7.20
Connecting to lsof.itap.purdue.edu|128.210.7.20|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/tools/unix/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch
ftp://ftp.cerias.purdue.edu/pub/tools/unix/sysutils/lsof/lsof_4.77.tar.bz2
--02:28:49--
ftp://ftp.cerias.purdue.edu/pub/tools/unix/sysutils/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.cerias.purdue.edu... 128.10.252.10
Connecting to ftp.cerias.purdue.edu|128.10.252.10|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/tools/unix/sysutils/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch ftp://ftp.tau.ac.il/pub/unix/admin/lsof_4.77.tar.bz2
--02:28:50-- ftp://ftp.tau.ac.il/pub/unix/admin/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.tau.ac.il... 132.66.16.61
Connecting to ftp.tau.ac.il|132.66.16.61|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/unix/admin ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch ftp://ftp.cert.dfn.de/pub/tools/admin/lsof/lsof_4.77.tar.bz2
--02:28:53-- ftp://ftp.cert.dfn.de/pub/tools/admin/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.cert.dfn.de... 193.174.13.99
Connecting to ftp.cert.dfn.de|193.174.13.99|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/tools/admin/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch ftp://ftp.fu-berlin.de/pub/unix/tools/lsof/lsof_4.77.tar.bz2
--02:28:55-- ftp://ftp.fu-berlin.de/pub/unix/tools/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.fu-berlin.de... 130.133.3.130
Connecting to ftp.fu-berlin.de|130.133.3.130|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/unix/tools/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch ftp://ftp.kaizo.org/pub/lsof/lsof_4.77.tar.bz2
--02:28:58-- ftp://ftp.kaizo.org/pub/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.kaizo.org... 208.113.202.72
Connecting to ftp.kaizo.org|208.113.202.72|:21... connected.
Logging in as anonymous ...
Login incorrect.
NOTE: fetch ftp://ftp.tu-darmstadt.de/pub/sysadmin/lsof/lsof_4.77.tar.bz2
--02:28:58-- ftp://ftp.tu-darmstadt.de/pub/sysadmin/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.tu-darmstadt.de... 130.83.47.89
Connecting to ftp.tu-darmstadt.de|130.83.47.89|:21... connected.
Logging in as anonymous ...
Login incorrect.
NOTE: fetch
ftp://ftp.tux.org/pub/sites/vic.cc.purdue.edu/tools/unix/lsof/lsof_4.77.tar.bz2
--02:28:59--
ftp://ftp.tux.org/pub/sites/vic.cc.purdue.edu/tools/unix/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving ftp.tux.org... 207.172.156.132
Connecting to ftp.tux.org|207.172.156.132|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/sites/vic.cc.purdue.edu/tools/unix/lsof ...
done.
==> PASV ... couldn't connect to 207.172.156.132 port 55649: Connection timed out
Retrying.
--02:32:10--
ftp://ftp.tux.org/pub/sites/vic.cc.purdue.edu/tools/unix/lsof/lsof_4.77.tar.bz2
(try: 2) => `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Connecting to ftp.tux.org|207.172.156.132|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/sites/vic.cc.purdue.edu/tools/unix/lsof ...
done.
==> PASV ... couldn't connect to 207.172.156.132 port 56530: Connection timed out
Retrying.
--02:35:22--
ftp://ftp.tux.org/pub/sites/vic.cc.purdue.edu/tools/unix/lsof/lsof_4.77.tar.bz2
(try: 3) => `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Connecting to ftp.tux.org|207.172.156.132|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/sites/vic.cc.purdue.edu/tools/unix/lsof ...
done.
==> PASV ... couldn't connect to 207.172.156.132 port 56956: No route to host
NOTE: fetch ftp://gd.tuwien.ac.at/utils/admin-tools/lsof/lsof_4.77.tar.bz2
--02:35:23-- ftp://gd.tuwien.ac.at/utils/admin-tools/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving gd.tuwien.ac.at... 192.35.244.50
Connecting to gd.tuwien.ac.at|192.35.244.50|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /utils/admin-tools/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch ftp://sunsite.ualberta.ca/pub/Mirror/lsof/lsof_4.77.tar.bz2
--02:35:38-- ftp://sunsite.ualberta.ca/pub/Mirror/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving sunsite.ualberta.ca... 129.128.5.190
Connecting to sunsite.ualberta.ca|129.128.5.190|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/Mirror/lsof ... done.
==> PASV ... done. ==> RETR lsof_4.77.tar.bz2 ...
No such file `lsof_4.77.tar.bz2'.
NOTE: fetch
ftp://the.wiretapped.net/pub/security/host-security/lsof/lsof_4.77.tar.bz2
--02:35:41--
ftp://the.wiretapped.net/pub/security/host-security/lsof/lsof_4.77.tar.bz2
=> `/var/hostings/OE/sources/lsof_4.77.tar.bz2'
Resolving the.wiretapped.net... 210.9.80.201
Connecting to the.wiretapped.net|210.9.80.201|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/security/host-security/lsof ...
No such directory `pub/security/host-security/lsof'.
NOTE: Task failed: Fetch failed:
ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_4.77.tar.bz2
NOTE: package lsof-4.77-r1: task do_fetch: failed
ERROR: TaskFailed event exception, aborting
NOTE: package lsof-4.77: failed
ERROR: Build of
/var/hostings/OE/org.openembedded.dev/packages/lsof/lsof_4.77.bb do_fetch failed
ERROR: Task 489
(/var/hostings/OE/org.openembedded.dev/packages/lsof/lsof_4.77.bb, do_fetch)
failed
NOTE: Tasks Summary: Attempted 788 tasks of which 788 didn't need to be rerun
and 1 failed.
ERROR: '/var/hostings/OE/org.openembedded.dev/packages/lsof/lsof_4.77.bb' failed
Obviously this is not a bug per se with the OE/Bitbake software itself, but
the infrastructure surrounding it. If there is a better way of handling this,
please let this poor newbie know. I'm still learning the OE community
philosophy and ways of doing things.
-Jeff
More information about the Openembedded-users
mailing list