| View previous topic :: View next topic |
| Author |
Message |
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
 Posted: Tue Apr 22, 2014 4:13 pm Post subject: |
 |
|
| Right before the collect2 line it seems to suggest there is a syntax error; as to why there is a syntax error, you might need to inspect the file. |
|
| Back to top |
|
 |
kaiulrich
n00b
Joined: 10 Sep 2005
Posts: 59
|
| Posted: Tue Apr 22, 2014 7:02 pm Post subject: |
|
|
One of the yocto guys sad wie need 3.82 or newer. My current make is GNU Make 3.81
remember i did.
| Code: |
bitbake -c fetchall core-image-minimal
WARNING: Host distribution "Gentoo" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
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:
Your version of make 3.82 is broken. Please revert to 3.81 or install a patched version.
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
ERROR: Command execution failed: Exited with 1
Summary: There was 1 WARNING message shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
|
and
| Code: | | >=sys-devel/make-3.82 |
|
|
| Back to top |
|
|
kaiulrich
n00b
Joined: 10 Sep 2005
Posts: 59
|
| Posted: Tue Apr 22, 2014 8:06 pm Post subject: |
|
|
hm line 150 of shlib.lds | Code: |
[...]
__libc_subfreE(__st { *(__libc_subfreeres) }
[...] |
| Code: | /* Script for --shared -z combreloc: shared library, combine & sort relocs */
OUTPUT_FORMAT("elf32-littlearm", "elf32-bigarm",
"elf32-littlearm")
OUTPUT_ARCH(arm)
ENTRY(_start)
SEARCH_DIR("=/usr/local/lib"); SEARCH_DIR("=/lib"); SEARCH_DIR("=/usr/lib");
SECTIONS
{
/* Read-only sections, merged into text segment: */
. = SEGMENT_START("text-segment", 0) + SIZEOF_HEADERS;
.note.gnu.build-id : { *(.note.gnu.build-id) }
.note.ABI-tag : { *(.note.ABI-tag) } .gnu.hash : { *(.gnu.hash) }
.dynsym : { *(.dynsym) }
.dynstr : { *(.dynstr) }
.gnu.version : { *(.gnu.version) }
.gnu.version_d : { *(.gnu.version_d) }
.gnu.version_r : { *(.gnu.version_r) }
.rel.dyn :
{
*(.rel.init)
*(.rel.text .rel.text.* .rel.gnu.linkonce.t.*)
*(.rel.fini)
*(.rel.rodata .rel.rodata.* .rel.gnu.linkonce.r.*)
*(.rel.data.rel.ro .rel.data.rel.ro.* .rel.gnu.linkonce.d.rel.ro.*)
*(.rel.data .rel.data.* .rel.gnu.linkonce.d.*)
*(.rel.tdata .rel.tdata.* .rel.gnu.linkonce.td.*)
*(.rel.tbss .rel.tbss.* .rel.gnu.linkonce.tb.*)
*(.rel.ctors)
*(.rel.dtors)
*(.rel.got)
*(.rel.bss .rel.bss.* .rel.gnu.linkonce.b.*)
*(.rel.iplt)
}
.rela.dyn :
{
*(.rela.init)
*(.rela.text .rela.text.* .rela.gnu.linkonce.t.*)
*(.rela.fini)
*(.rela.rodata .rela.rodata.* .rela.gnu.linkonce.r.*)
*(.rela.data .rela.data.* .rela.gnu.linkonce.d.*)
*(.rela.tdata .rela.tdata.* .rela.gnu.linkonce.td.*)
*(.rela.tbss .rela.tbss.* .rela.gnu.linkonce.tb.*)
*(.rela.ctors)
*(.rela.dtors)
*(.rela.got)
*(.rela.bss .rela.bss.* .rela.gnu.linkonce.b.*)
*(.rela.iplt)
}
.rel.plt :
{
*(.rel.plt)
}
.rela.plt :
{
*(.rela.plt)
}
.init :
{
KEEP (*(SORT_NONE(.init)))
}
.plt : { *(.plt) }
.iplt : { *(.iplt) }
.text :
{
*(.text.unlikely .text.*_unlikely)
*(.text.exit .text.exit.*)
*(.text.startup .text.startup.*)
*(.text.hot .text.hot.*)
*(.text .stub .text.* .gnu.linkonce.t.*)
/* .gnu.warning sections are handled specially by elf32.em. */
*(.gnu.warning)
*(.glue_7t) *(.glue_7) *(.vfp11_veneer) *(.v4_bx)
}
.fini :
{
KEEP (*(SORT_NONE(.fini)))
}
PROVIDE (__etext = .);
PROVIDE (_etext = .);
PROVIDE (etext = .);
.rodata : { *(.rodata .rodata.* .gnu.linkonce.r.*) }
.rodata1 : { *(.rodata1) }
.ARM.extab : { *(.ARM.extab* .gnu.linkonce.armextab.*) }
PROVIDE_HIDDEN (__exidx_start = .);
.ARM.exidx : { *(.ARM.exidx* .gnu.linkonce.armexidx.*) }
PROVIDE_HIDDEN (__exidx_end = .);
.eh_frame_hdr : { *(.eh_frame_hdr) }
.eh_frame : ONLY_IF_RO { KEEP (*(.eh_frame)) }
.gcc_except_table : ONLY_IF_RO { *(.gcc_except_table
.gcc_except_table.*) }
/* These sections are generated by the Sun/Oracle C++ compiler. */
.exception_ranges : ONLY_IF_RO { *(.exception_ranges
.exception_ranges*) }
/* Adjust the address for the data segment. We want to adjust up to
the same address within the page on the next page up. */
.hash : { *(.hash) }
. = ALIGN (CONSTANT (MAXPAGESIZE)) - ((CONSTANT (MAXPAGESIZE) - .) & (CONSTANT (MAXPAGESIZE) - 1)); . = DATA_SEGMENT_ALIGN (CONSTANT (MAXPAGESIZE), CONSTANT (COMMONPAGESIZE));
/* Exception handling */
.eh_frame : ONLY_IF_RW { KEEP (*(.eh_frame)) }
.gcc_except_table : ONLY_IF_RW { *(.gcc_except_table .gcc_except_table.*) }
.exception_ranges : ONLY_IF_RW { *(.exception_ranges .exception_ranges*) }
/* Thread Local Storage sections */
.tdata : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
.tbss : { *(.tbss .tbss.* .gnu.linkonce.tb.*) *(.tcommon) }
.preinit_array :
{
KEEP (*(.preinit_array))
}
.init_array :
{
KEEP (*(SORT(.init_array.*)))
KEEP (*(.init_array))
}
.fini_array :
{
KEEP (*(SORT(.fini_array.*)))
KEEP (*(.fini_array))
}
.ctors :
{
/* gcc uses crtbegin.o to find the start of
the constructors, so we make sure it is
first. Because this is a wildcard, it
doesn't matter if the user does not
actually link against crtbegin.o; the
linker won't look for a file to match a
wildcard. The wildcard also means that it
doesn't matter which directory crtbegin.o
is in. */
KEEP (*crtbegin.o(.ctors))
KEEP (*crtbegin?.o(.ctors))
/* We don't want to include the .ctor section from
the crtend.o file until after the sorted ctors.
The .ctor section from the crtend file contains the
end of ctors marker and it must be last */
KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .ctors))
KEEP (*(SORT(.ctors.*)))
KEEP (*(.ctors))
}
.dtors :
{
KEEP (*crtbegin.o(.dtors))
KEEP (*crtbegin?.o(.dtors))
KEEP (*(EXCLUDE_FILE (*crtend.o *crtend?.o ) .dtors))
KEEP (*(SORT(.dtors.*)))
KEEP (*(.dtors))
}
.jcr : { KEEP (*(.jcr)) }
PROVIDE(__start___libc_subfreeres = .);
__libc_subfreE(__st { *(__libc_subfreeres) }
PROVIDE(__stop___libc_subfreeres = .);
PROVIDE(__start___libc_atexit = .);
__libc_atexit : { *(__libc_atexit) }
PROVIDE(__stop___libc_atexit = .);
PROVIDE(__start___libc_thread_subfreeres = .);
__libc_thread_subfreeres : { *(__libc_thread_subfreeres) }
PROVIDE(__stop___libc_thread_subfreeres = .);
/DISCARD/ : { *(.gnu.glibc-stub.*) }
.data.rel.ro : { *(.data.rel.ro.local* .gnu.linkonce.d.rel.ro.local.*) *(.data.rel.ro .data.rel.ro.* .gnu.linkonce.d.rel.ro.*) }
.dynamic : { *(.dynamic) }
. = DATA_SEGMENT_RELRO_END (0, .);
.got : { *(.got.plt) *(.igot.plt) *(.got) *(.igot) }
.data :
{
PROVIDE (__data_start = .);
*(.data .data.* .gnu.linkonce.d.*)
SORT(CONSTRUCTORS)
}
.data1 : { *(.data1) }
_edata = .; PROVIDE (edata = .);
. = .;
__bss_start = .;
__bss_start__ = .;
.bss :
{
*(.dynbss)
PROVIDE(__start___libc_freeres_ptrs = .);
*(__libc_freeres_ptrs)
PROVIDE(__stop___libc_freeres_ptrs = .);
*(.bss .bss.* .gnu.linkonce.b.*)
*(COMMON)
/* Align here to ensure that the .bss section occupies space up to
_end. Align after .bss to ensure correct alignment even if the
.bss section disappears because there are no input sections.
FIXME: Why do we need it? When there is no .bss section, we don't
pad the .data section. */
. = ALIGN(. != 0 ? 32 / 8 : 1);
}
_bss_end__ = . ; __bss_end__ = . ;
. = ALIGN(32 / 8);
. = ALIGN(32 / 8);
__end__ = . ;
_end = .; PROVIDE (end = .);
. = DATA_SEGMENT_END (.);
/* Stabs debugging sections. */
.stab 0 : { *(.stab) }
.stabstr 0 : { *(.stabstr) }
.stab.excl 0 : { *(.stab.excl) }
.stab.exclstr 0 : { *(.stab.exclstr) }
.stab.index 0 : { *(.stab.index) }
.stab.indexstr 0 : { *(.stab.indexstr) }
.comment 0 : { *(.comment) }
/* DWARF debug sections.
Symbols in the DWARF debugging sections are relative to the beginning
of the section so we begin them at 0. */
/* DWARF 1 */
.debug 0 : { *(.debug) }
.line 0 : { *(.line) }
/* GNU DWARF 1 extensions */
.debug_srcinfo 0 : { *(.debug_srcinfo) }
.debug_sfnames 0 : { *(.debug_sfnames) }
/* DWARF 1.1 and DWARF 2 */
.debug_aranges 0 : { *(.debug_aranges) }
.debug_pubnames 0 : { *(.debug_pubnames) }
/* DWARF 2 */
.debug_info 0 : { *(.debug_info .gnu.linkonce.wi.*) }
.debug_abbrev 0 : { *(.debug_abbrev) }
.debug_line 0 : { *(.debug_line) }
.debug_frame 0 : { *(.debug_frame) }
.debug_str 0 : { *(.debug_str) }
.debug_loc 0 : { *(.debug_loc) }
.debug_macinfo 0 : { *(.debug_macinfo) }
/* SGI/MIPS DWARF 2 extensions */
.debug_weaknames 0 : { *(.debug_weaknames) }
.debug_funcnames 0 : { *(.debug_funcnames) }
.debug_typenames 0 : { *(.debug_typenames) }
.debug_varnames 0 : { *(.debug_varnames) }
/* DWARF 3 */
.debug_pubtypes 0 : { *(.debug_pubtypes) }
.debug_ranges 0 : { *(.debug_ranges) }
/* DWARF Extension. */
.debug_macro 0 : { *(.debug_macro) }
.gnu.attributes 0 : { KEEP (*(.gnu.attributes)) }
.note.gnu.arm.ident 0 : { KEEP (*(.note.gnu.arm.ident)) }
/DISCARD/ : { *(.note.GNU-stack) *(.gnu_debuglink) *(.gnu.lto_*) }
} |
|
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Tue Apr 22, 2014 8:24 pm Post subject: |
|
|
| I'm not sure about the syntax; but that line you've quoted, it miss a closing parenthese (though it might be on another line). You'll probably want to file a bug about this. |
|
| Back to top |
|
|
kaiulrich
n00b
Joined: 10 Sep 2005
Posts: 59
|
| Posted: Wed Apr 23, 2014 12:47 pm Post subject: |
|
|
The yocto people mentioned it migt be the wrong make or gawk version.
I do have
gcc-Version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5)
make-Version GNU Make 3.82 Built for x86_64-pc-linux-gnu
GNU Awk 4.0.2
Is this ringing a bell? |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Wed Apr 23, 2014 1:05 pm Post subject: |
|
|
For comparison, here:
| Code: | gcc version 4.8.2 (Gentoo 4.8.2 p1.0, pie-0.5.8)
GNU Make 4.0
GNU Awk 4.1.1, API: 1.1 |
|
|
| Back to top |
|
|
kaiulrich
n00b
Joined: 10 Sep 2005
Posts: 59
|
| Posted: Thu Apr 24, 2014 7:53 am Post subject: |
|
|
Hm, interesting.
I would try it with
| Code: | GNU Make 4.0
GNU Awk 4.1.1, |
How can i Install these versions? |
|
| Back to top |
|
|
TomWij
Retired Dev
Joined: 04 Jul 2012
Posts: 1553
|
| Posted: Thu Apr 24, 2014 3:19 pm Post subject: |
|
|
| Add sys-devel/make and sys-apps/gawk to /etc/portage/package.accept_keywords and then run `emerge -1u sys-devel/make sys-apps/gawk`; if needed, update the entire world instead with `emerge -avuDN @world`. |
|
| Back to top |
|
|
kaiulrich
n00b
Joined: 10 Sep 2005
Posts: 59
|
| Posted: Thu Apr 24, 2014 6:16 pm Post subject: |
|
|
Hi,
good news tried it with
- GNU Awk 4.1.1, API: 1.1
- GNU Make 4.0
it worked fine.
Thanx |
|
| Back to top |
|
|
kindanil
n00b
Joined: 06 May 2014
Posts: 2
Location: Iran
|
| Posted: Tue May 06, 2014 6:04 am Post subject: running bitbake on gentoo |
|
|
Hi there
I am trying to run bitbake on gentoo. I installed required Debian packages. after running source oe-intit-build-env the following errors stop the execution. I am totally confused what to do 
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
ERROR: Error parsing configuration files
Traceback (most recent call last):
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 227, in CookerDataBuilder.parseBaseConfiguration():
try:
> self.parseConfigurationFiles(self.prefiles, self.postfiles)
except SyntaxError:
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 289, in CookerDataBuilder.parseConfigurationFiles(prefiles=[], postfiles=[]):
if data.getVar("BB_WORKERCONTEXT", False) is None:
> bb.fetch.fetcher_init(data)
bb.codeparser.parser_cache_init(data)
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/fetch2/__init__.py", line 472, in fetcher_init(d=<bb.data_smart.DataSmart object at 0x25a0450>):
pass
> revs.clear()
else:
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/persist_data.py", line 147, in SQLTable.clear():
def clear(self):
> self._execute("DELETE FROM %s;" % self.table)
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/persist_data.py", line 66, in SQLTable._execute(*query=('DELETE FROM BB_URI_HEADREVS;',)):
try:
> return self.cursor.execute(*query)
except sqlite3.OperationalError as exc:
OperationalError: attempt to write a readonly database
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
ERROR: Error parsing configuration files
Traceback (most recent call last):
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 227, in CookerDataBuilder.parseBaseConfiguration():
try:
> self.parseConfigurationFiles(self.prefiles, self.postfiles)
except SyntaxError:
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/cookerdata.py", line 289, in CookerDataBuilder.parseConfigurationFiles(prefiles=[], postfiles=[]):
if data.getVar("BB_WORKERCONTEXT", False) is None:
> bb.fetch.fetcher_init(data)
bb.codeparser.parser_cache_init(data)
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/fetch2/__init__.py", line 472, in fetcher_init(d=<bb.data_smart.DataSmart object at 0x25a0450>):
pass
> revs.clear()
else:
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/persist_data.py", line 147, in SQLTable.clear():
def clear(self):
> self._execute("DELETE FROM %s;" % self.table)
File "/root/home/Yocto/poky-dora-10.0.1/bitbake/lib/bb/persist_data.py", line 66, in SQLTable._execute(*query=('DELETE FROM BB_URI_HEADREVS;',)):
try:
> return self.cursor.execute(*query)
except sqlite3.OperationalError as exc:
OperationalError: attempt to write a readonly database |
|
| Back to top |
|
|
kindanil
n00b
Joined: 06 May 2014
Posts: 2
Location: Iran
|
| Posted: Tue May 06, 2014 11:47 am Post subject: Solved |
|
|
hi all
I found that the user has not write access to the database sqlite , in which paths are stored, simply ran the following command :
chown -R bitbake_user /root/home/Yocto
and it solved  |
|
| Back to top |
|
|
pgu
l33t
Joined: 30 Jul 2009
Posts: 721
Location: Oslo, Norway
|
| Posted: Wed Nov 12, 2014 8:52 pm Post subject: |
|
|
During my first attempt at Yocto on Gentoo I get:
| Code: | meta-yocto-bsp = "dizzy:df87cb27efeaea1455f20692f9f1397c6fcab254"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Error executing a python function in /home/petter/projects/yocto/poky.git
/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.16.bb:
The stack trace of python calls that resulted in this exception/failure was:
File: 'fixup_perms', lineno: 231, function: <module>
0227: each_file = os.path.join(root, f)
0228: fix_perms(each_file, fs_perms_table[dir].fmode, fs
_perms_table[dir].fuid, fs_perms_table[dir].fgid, dir)
0229:
0230:
*** 0231:fixup_perms(d)
0232:
File: 'fixup_perms', lineno: 173, function: fixup_perms
0169: if len(lsplit) != 8 and not (len(lsplit) == 3 and lspl
it[1].lower() == "link"):
0170: msg = "Fixup perms: %s invalid line: %s" % (conf,
line)
0171: package_qa_handle_error("perm-line", msg, d)
0172: continue
*** 0173: entry = fs_perms_entry(d.expand(line))
0174: if entry and entry.path:
0175: fs_perms_table[entry.path] = entry
0176: f.close()
|
after doing:
| Code: | | bitbake -k core-image-minimal |
I'm running
| Code: | # python --version
Python 2.7.7
|
Anybody else getting this error? |
|
| Back to top |
|
|
ccube
n00b
Joined: 15 Feb 2011
Posts: 70
|
| Posted: Thu Nov 20, 2014 1:16 pm Post subject: |
|
|
Hi Guys,
I got a yocto autobuilder running on an ~amd64 box. Happy to share some information about that if there are specific questions! 
Cheers
Lukas |
|
| Back to top |
|
|
pgu
l33t
Joined: 30 Jul 2009
Posts: 721
Location: Oslo, Norway
|
| Posted: Tue Nov 25, 2014 7:20 pm Post subject: |
|
|
I managed to get core-image-minimal and qemux86 up and running. But whenever I try som cross compilation I end up with some errors.
I tried this:
http://www.cnx-software.com/2013/07/05/12mb-minimal-image-for-raspberry-pi-using-the-yocto-project/
Which resulted in:
| Code: | bitbake rpi-basic-image
..
ERROR: Function failed: Unpack failure for URL: 'http://www.rpm5.org/files/rpm/rpm-5.4/rpm-5.4.9-0.20120508.src.rpm;extract=rpm-5.4.9.tar.gz'. Unpack command PATH="/home/yocto/poky.git/scripts/native-intercept:/home/yocto/poky.git/scripts:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/armv6-vfp-linux:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/sbin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/sbin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux//bin:/home/yocto/poky.git/scripts:/home/yocto/poky.git/bitbake/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.3" rpm2cpio.sh /home/yocto/my-rpi-build/downloads/rpm-5.4.9-0.20120508.src.rpm | cpio -id rpm-5.4.9.tar.gz failed with return value 1
ERROR: Logfile of failure stored in: /home/yocto/my-rpi-build/tmp/work/x86_64-linux/rpm-native/5.4.9-r63/temp/log.do_unpack.28861
Log data follows:
| DEBUG: Executing python function do_unpack
| DEBUG: Executing python function base_do_unpack
| NOTE: Unpacking /home/yocto/my-rpi-build/downloads/rpm-5.4.9-0.20120508.src.rpm to /home/yocto/my-rpi-build/tmp/work/x86_64-linux/rpm-native/5.4.9-r63/
| /home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/unlzma: /lib64/liblzma.so.5: no version information available (required by /home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/unlzma)
| /home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/unlzma: /lib64/liblzma.so.5: no version information available (required by /home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/unlzma)
| /home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/unlzma: (stdin): File format not recognized
| cpio: premature end of archive
| DEBUG: Python function base_do_unpack finished
| DEBUG: Python function do_unpack finished
| ERROR: Function failed: Unpack failure for URL: 'http://www.rpm5.org/files/rpm/rpm-5.4/rpm-5.4.9-0.20120508.src.rpm;extract=rpm-5.4.9.tar.gz'. Unpack command PATH="/home/yocto/poky.git/scripts/native-intercept:/home/yocto/poky.git/scripts:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin/armv6-vfp-linux:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/sbin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/usr/bin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux/sbin:/home/yocto/my-rpi-build/tmp/sysroots/x86_64-linux//bin:/home/yocto/poky.git/scripts:/home/yocto/poky.git/bitbake/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.3" rpm2cpio.sh /home/yocto/my-rpi-build/downloads/rpm-5.4.9-0.20120508.src.rpm | cpio -id rpm-5.4.9.tar.gz failed with return value 1
ERROR: Task 74 (virtual:native:/home/yocto/poky.git/meta/recipes-devtools/rpm/rpm_5.4.9.bb, do_unpack) failed with exit code '1'
NOTE: Tasks Summary: Attempted 529 tasks of which 523 didn't need to be rerun and 1 failed.
Waiting for 0 running tasks to finish:
|
And this
http://mytechpg.blogspot.no/2013/06/raspberrypi-and-yocto.html which resulted in:
| Code: | bitbake rpi-hwup-image
Pseudo is not present but is required, building this first before the main build
WARNING: Host distribution "Unknown" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
ERROR: ParseError at /home/yocto/meta-openembedded.git/meta-multimedia/recipes-multimedia/rtmpdump/rtmpdump_2.4.bb:17: Could not inherit file classes/autotools-brokensep.bbclass
ERROR: Command execution failed: Exited with 1 |
|
|
| Back to top |
|
|
ccube
n00b
Joined: 15 Feb 2011
Posts: 70
|
| Posted: Tue Nov 25, 2014 11:50 pm Post subject: |
|
|
Hi pgu,
for me, this does not look like a gentoo specific problem. Did you try compiling the image on one of the supported host platforms instead of gentoo?
You also should consider building with a more recent yocto branch instead of an outdated one. I really recommend reading the yocto documentation (which is really good) and not just copy and pasting commands from a random 1.5 year old blog post! 
Cheers,
ccube |
|
| Back to top |
|
|
pgu
l33t
Joined: 30 Jul 2009
Posts: 721
Location: Oslo, Norway
|
| Posted: Wed Nov 26, 2014 6:17 am Post subject: |
|
|
| I clearly need to spend more time to study the Yocto documentation. I don't have access to a supported OS ATM. I did not try random commands from random blogs. In the lack of a reference system I was searching for blogs and tutorials where users had successfully cross built Yocto. Some users appears to be using the older branches. However, I'll hopefully manage to free up some space and get VirtualBox up and running with some of the supported OS versions soon. That way I will have a golden reference. |
|
| Back to top |
|
|
ccube
n00b
Joined: 15 Feb 2011
Posts: 70
|
| Posted: Wed Nov 26, 2014 11:40 am Post subject: |
|
|
Yeah, understanding yocto is not a job which can be done in a couple of hours. Though, if you are coming from a gentoo background you might have some advantages, because the openembedded recipes are similar to portage's ebuild files!
Have you tried
instead of the old 1.4 branch?
Cheers |
|
| Back to top |
|
|
pgu
l33t
Joined: 30 Jul 2009
Posts: 721
Location: Oslo, Norway
|
| Posted: Wed Nov 26, 2014 12:23 pm Post subject: |
|
|
| Not after I managed to build dizzy using a local toolchain. I'll give the daisy branch a try. |
|
| Back to top |
|
|
pgu
l33t
Joined: 30 Jul 2009
Posts: 721
Location: Oslo, Norway
|
| Posted: Fri Nov 28, 2014 8:22 pm Post subject: |
|
|
Finally I got a different machine with some more disk space set up to run yocto. Using the daisy branch I got a successful Raspberry Pi build. However, it seems to hang right after I log in, but at least it made it to the login prompt:
| Code: | Poky (Yocto Project Reference Distro) 1.6.2 raspberrypi /dev/ttyAMA0
raspberrypi login:
|
|
|
| Back to top |
|
|
|
Other Things Gentoo
