[yocto] dtb filename mismatch prevents booting
Hello list, if I try to boot from my yocto generated SD-card image my u-boot can't start the kernel because the imx6ul-14x14-evk.dtb is missing. reading boot.scr ** Unable to read file boot.scr ** reading zImage 5072288 bytes read in 328 ms (14.7 MiB/s) Booting from mmc ... reading imx6ul-14x14-evk.dtb ** Unable to read file imx6ul-14x14-evk.dtb ** Kernel image @ 0x8200 [ 0x00 - 0x4d65a0 ] Starting kernel ... In my /boot folder I saw a dtb file, but the filename is a bit different. zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb So I changed these filename manually and my Image is booting. mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb »zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“ What is the right way to define these dtb filename? I saw the IMAGE_BOOT_FILES in local.conf #IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb" IMAGE_BOOT_FILES = "zImage imx6ul-14x14-evk.dtb" but after I changed it my build fails. ERROR: Error: The image creation script '/home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic' returned 1: Error: exec_cmd: install -m 0644 -D /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/imx6ul-14x14-evk.dtb /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/deploy/images/imx6ulevk/fsl-image-imx6ulevk-20160208144228/build/boot/imx6ul-14x14-evk.dtb returned '1' instead of 0 Checking basic build environment... Done. Creating image(s)... WARNING: /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic:1 exit 1 from BUILDDIR=/home/graute/5411_IBIS/yocto/build-imx6ulevk wic create $wks --vars /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/sysroots/imx6ulevk/imgdata/ -e fsl-image -o $out/ ERROR: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/graute/5411_IBIS/yocto/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/log.do_rootfs.17681 ERROR: Task 7 (/home/graute/5411_IBIS/yocto/os-meta-dnt/meta-fsl/recipes-fsl/images/fsl-image.bb, do_rootfs) failed with exit code '1' some ideas whats going wrong here? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] wic adds wrong mount lines to my fstab
On Wed, Feb 10, 2016 at 11:19 AM, Ed Bartosh <ed.bart...@linux.intel.com> wrote: > Hi Oliver, > > On Tue, Feb 09, 2016 at 09:29:16AM +0100, Oliver Graute wrote: >> # It uses SPL and u-boot >> # >> # The disk layout used is: >> # - - - -- - -- >> # | | SPL | u-boot | /boot1 | /boot2 | rootfs1 | rootfs2 |data| >> # - - - -- - -- >> # ^ ^ ^ ^ ^ ^ >> # | | | | | | >> # 0 1kiB 69kiB 4MiB 4MiB + 20MiB4MiB + 8Mib + rootfs1 + rootfs2 + >> data >> # >> part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk >> --no-table --align 1 >> part u-boot --source rawcopy --sourceparams="file=u-boot.img" --ondisk >> mmcblk --no-table --align 69 >> part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label >> boot --active --align 4096 --size 20M --extra-space 0 >> #part /boot2 --source bootimg-partition --ondisk mmcblk --fstype=vfat >> --label boot2 --active --align 4096 --size 8M --extra-space 0 >> part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 >> --size 125 >> part /rescue --source rootfs --ondisk mmcblk --fstype=ext3 --label secondary >> --align 4 --size 125 >> part /data --ondisk mmcblk --fstype=ext3 --label data --align 4 --size 730 >> >> Some sugesstions to fix this? > How exactly wic complains if you use --ondisk mmcblk0 ? > > It worked for me with this .wks: > part /boot --source bootimg-pcbios --ondisk mmcblk0 --label boot --active > --align 1024 > part / --source rootfs --ondisk mmcblk0 --fstype=ext3 --label root --align > 1024 > part /rescue --source rootfs --ondisk mmcblk0 --fstype=ext3 --label secondary > --align 4 --size 125 > part /data --ondisk mmcblk0 --fstype=ext3 --label data --align 4 --size 730 > > bootloader --timeout=0 --append="rootwait rootfstype=ext3 console=tty0" > > and produced these 2 lines in fstab: > /dev/mmcblk0p3 /rescue ext3defaults0 0 > /dev/mmcblk0p5 /data ext3defaults0 0 > > If you provide more info about your setup(layers used?) I can try to > reproduce it and fix the issue. > Creating bug in https://bugzilla.yoctoproject.org would be great too. Hello Ed, it is working now with --ondisk mmcblk0. I'am not sure why it didn't worked before. I can't reproduce it anymore. Thx for your help and sorry for the noise. best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] wic adds wrong mount lines to my fstab
Hello list, I am using wic to generate partitioned yocto images. After I boot such an Image, I see two added entrys in my /etc/fstab wich are not correct. cat /etc/fstab # # /etc/fstab: static file system information # # /dev/root / auto defaults1 1 proc/proc proc defaults0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 usbdevfs/proc/bus/usb usbdevfs noauto 0 0 /dev/mmcblk0p5 /rwfs auto defaults0 0 #/dev/mmcblk0p3 /rescue ext3 defaults0 0 /dev/mmcblk0p5 /data ext3 defaults0 0 tmpfs /run tmpfsmode=0755,nodev,nosuid,strictatime 0 0 tmpfs /var/volatile tmpfsdefaults0 0 tmpfs /var/cachetmpfsdefaults0 0 tmpfs /var/lib tmpfsdefaults0 0 tmpfs /var/spooltmpfsdefaults0 0 tmpfs /var/apache2/logs tmpfsdefaults0 0 /dev/mmcblkp3 /rescue ext3defaults0 0 /dev/mmcblkp5 /data ext3defaults0 0 the last two lines are added by the wic tool. Here is the 0 missing. If I add these 0 to my wks --ondisk mmcblk option wic is complaining. So I`am just using is like in this wks disk layout: # short-description: Create SD card image with a boot partition # long-description: # Create an image that can be written onto a SD card using dd for use # with i.MX SoC family. # It uses SPL and u-boot # # The disk layout used is: # - - - -- - -- # | | SPL | u-boot | /boot1 | /boot2 | rootfs1 | rootfs2 |data| # - - - -- - -- # ^ ^ ^ ^ ^ ^ # | | | | | | # 0 1kiB 69kiB 4MiB 4MiB + 20MiB4MiB + 8Mib + rootfs1 + rootfs2 + data # part SPL --source rawcopy --sourceparams="file=SPL" --ondisk mmcblk --no-table --align 1 part u-boot --source rawcopy --sourceparams="file=u-boot.img" --ondisk mmcblk --no-table --align 69 part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4096 --size 20M --extra-space 0 #part /boot2 --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot2 --active --align 4096 --size 8M --extra-space 0 part / --source rootfs --ondisk mmcblk --fstype=ext3 --label root --align 4 --size 125 part /rescue --source rootfs --ondisk mmcblk --fstype=ext3 --label secondary --align 4 --size 125 part /data --ondisk mmcblk --fstype=ext3 --label data --align 4 --size 730 Some sugesstions to fix this? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] dtb filename mismatch prevents booting
On 10/02/16, Maciej Borzecki wrote: > > > Dnia 10 luty 2016 o 17:16 Oliver Graute <oliver.gra...@gmail.com> > > napisał(a): > > > > > > Hello list, > > > > if I try to boot from my yocto generated SD-card image my u-boot can't > > start the kernel because the imx6ul-14x14-evk.dtb is missing. > > > > > > reading boot.scr > > ** Unable to read file boot.scr ** > > reading zImage > > 5072288 bytes read in 328 ms (14.7 MiB/s) > > Booting from mmc ... > > reading imx6ul-14x14-evk.dtb > > ** Unable to read file imx6ul-14x14-evk.dtb ** > > Kernel image @ 0x8200 [ 0x00 - 0x4d65a0 ] > > > > Starting kernel ... > > > > > > In my /boot folder I saw a dtb file, but the filename is a bit different. > > > > zImage-imx6ul-14x14-evk.dtb instead of imx6ul-14x14-evk.dtb > > > > So I changed these filename manually and my Image is booting. > > > > mv zImage-imx6ul-14x14-evk.dtb imx6ul-14x14-evk.dtb > > »zImage-imx6ul-14x14-evk.dtb“ -> »imx6ul-14x14-evk.dtb“ > > > > What is the right way to define these dtb filename? > > > > some ideas whats going wrong here? > > > > IIRC the usual way was to add kernel-devicetree package and let u-boot > pick the proper dtb during boot. > > As for IMAGE_BOOT_FILES, you can tell wic to automatically rename files > by passing the desired name after a semicolon like this: > > IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;mx6ul-14x14-evk.dtb" ok that worked for me, I changed it like this -IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb" +IMAGE_BOOT_FILES = "zImage zImage-imx6ul-14x14-evk.dtb;imx6ul-14x14-evk.dtb" now the Image is directly booting without manually renaming. thx for your help Best Rgeards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Howto change the default shell in yocto?
On 05/03/16, Burton, Ross wrote: > On 5 March 2016 at 11:48, Oliver Graute <oliver.gra...@gmail.com> wrote: > > > first the default *system* shell (/bin/sh) is this possible? or does this > > affect > > to much of the yoco system itself, if I change /bin/sh to /bin/dash? > > > > bash is only the default shell (ie symlink from /bin/sh) if you install it, > so if you don't want bash to be sh then one option is to not install bash. > > If you do want to keep bash installed but change the sh link, then that is > managed with update-alternatives. > ok thx, if I do update-alternatives --install /bin/sh sh /bin/dash 100 on the target it works. Best Regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Howto change the default shell in yocto?
Hello, how can I change the default shell on the yocto target from bash to another shell like dash? is there a variable for local.conf? or do I need to adapt my passwd for every user? Best Regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Howto change the default shell in yocto?
On 04/03/16, Christopher Larson wrote: > The default *system* shell (/bin/sh) or the default shell for users, or for > root? Folks often conflate them, but they're not the same. first the default *system* shell (/bin/sh) is this possible? or does this affect to much of the yoco system itself, if I change /bin/sh to /bin/dash? the alternative for me is to just change the default shell for normal users and the root user. I assume its done via /etc/passwd. But how I adapt these the yocto way? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Can't replace login.defs with shadow-sysroot bbappend
Hello list,
i'm trying to replace /etc/login.defs on the target with my own one. So
I created a shadow-sysroot_%.bbappend file with this content:
FILESEXTRAPATHS_prepend := "${THISDIR}/${BPN}:"
# As we're overriding login.defs_shadow-sysroot we have to readd the checksum
for it here
# as it's containing the license for this component
LIC_FILES_CHKSUM =
"file://login.defs_shadow-sysroot;md5=286ba0946b3b8a300da3893d7b3af060"
SRC_URI_append = " file://login.defs_shadow-sysroot "
S = "${WORKDIR}"
do_install_append() {
install -d ${D}${sysconfdir}
install -p -m 755 ${S}/login.defs_shadow-sysroot
${D}${sysconfdir}/login.defs
}
FILES_${PN} = "${D}${sysconfdir}/login.defs"
If I run "bitbake shadow-sysroot" everything seems fine. But on the target
there is no package shadow-sysroot after a complete image build. Just these:
opkg list | grep shadow
shadow - 4.2.1-r0
shadow-base - 4.2.1-r0
shadow-securetty - 4.2.1-r3
If I explicit added shadow-sysroot to my fsl-image.bb where I put all my
other packages for the target in I get this error.
bitbake fsl-image
Collected errors:
* opkg_prepare_url_for_install: Couldn't find anything to satisfy
'shadow-sysroot'.
ERROR: Function failed: do_rootfs
Some clue what is wrong here? I'am on jethro yocto branch.
Best regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Can't replace login.defs with shadow-sysroot bbappend
On 28/07/16, Zhenhua Luo wrote:
> Hi Oliver,
>
> The following line in shadow-sysroot.bb disables the final binary packages
> generation. You can try to add bbappend for shadow to do the customization.
>
> # don't create any packages
> # otherwise: dbus-dev depends on shadow-sysroot-dev which depends on
> shadow-sysroot
> # and this has another copy of /etc/login.defs already provided by shadow
> PACKAGES = ""
thx for this usefull note. It works for me with shadow_%.bbappend.
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://login.defs"
do_install_append() {
install -m 644 ${WORKDIR}/login.defs ${D}${sysconfdir}/login.defs
}
FILES_${PN} += "${sysconfdir}/login.defs"
Best regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] bitbake -c menuconfig linux-fslc in a tmux window
Hello list,
if I start the following command in a tmux window it doesn't work.
bitbake -c menuconfig linux-fslc
if I start this command in a extra gnome-terminal a new gnome-terminal
pops-up and I can configure my kernel related stuff.
in the poky /os-poky/meta/lib/oe/terminal.py there is some code that
indicate that it could be possible that a new tmux-pane should open here.
Some clue why bitbake does not open an extra tmux-pane for me?
I'am using yocto jethro 2.0.2.
Best Regards,
Oliver
NOTE: Executing RunQueue Tasks
ERROR: Error executing a python function in
/home/graute/5411_IBIS/yocto/os-meta-fsl-arm/recipes-kernel/linux/linux-fslc_4.4.bb:
The stack trace of python calls that resulted in this exception/failure was:
File: 'do_menuconfig', lineno: 25, function:
0021:bb.note("Configuration changed, recompile will be forced")
0022:bb.build.write_taint('do_compile', d)
0023:
0024:
*** 0025:do_menuconfig(d)
0026:
File: 'do_menuconfig', lineno: 11, function: do_menuconfig
0007:shutil.copy(".config", ".config.orig")
0008:except OSError:
0009:mtime = 0
0010:
*** 0011:oe_terminal("/bin/bash -c \"make menuconfig; if [ \$? -ne 0 ];
then echo 'Command failed.'; printf 'Press any key to continue... '; read r;
fi\"", 'linux-fslc Configuration', d)
0012:
0013:# FIXME this check can be removed when the minimum bitbake
version has been bumped
0014:if hasattr(bb.build, 'write_taint'):
0015:try:
File: 'terminal.bbclass', lineno: 55, function: oe_terminal
0051:except oe.terminal.ExecutionError as exc:
0052:bb.fatal('Unable to spawn terminal %s: %s' % (terminal,
exc))
0053:
0054:try:
*** 0055:oe.terminal.spawn_preferred(command, title, None, d)
0056:except oe.terminal.NoSupportedTerminals:
0057:bb.fatal('No valid terminal found, unable to open devshell')
0058:except oe.terminal.ExecutionError as exc:
0059:bb.fatal('Unable to spawn terminal %s: %s' % (terminal, exc))
File: '/home/graute/5411_IBIS/yocto/os-poky/meta/lib/oe/terminal.py', lineno:
199, function: spawn_preferred
0195:def spawn_preferred(sh_cmd, title=None, env=None, d=None):
0196:"""Spawn the first supported terminal, by priority"""
0197:for terminal in prioritized():
0198:try:
*** 0199:spawn(terminal.name, sh_cmd, title, env, d)
0200:break
0201:except UnsupportedTerminal:
0202:continue
0203:else:
File: '/home/graute/5411_IBIS/yocto/os-poky/meta/lib/oe/terminal.py', lineno:
214, function: spawn
0210:terminal = Registry.registry[name]
0211:except KeyError:
0212:raise UnsupportedTerminal(name)
0213:
*** 0214:pipe = terminal(sh_cmd, title, env, d)
0215:output = pipe.communicate()[0]
0216:if pipe.returncode != 0:
0217:raise ExecutionError(sh_cmd, pipe.returncode, output)
0218:
File: '/home/graute/5411_IBIS/yocto/os-poky/meta/lib/oe/terminal.py', lineno:
133, function: __init__
0129:
0130:if not os.getenv('TMUX'):
0131:raise UnsupportedTerminal('tmux is not running')
0132:
*** 0133:if not check_tmux_pane_size('tmux'):
0134:raise UnsupportedTerminal('tmux pane too small')
0135:
0136:Terminal.__init__(self, sh_cmd, title, env, d)
0137:
File: '/home/graute/5411_IBIS/yocto/os-poky/meta/lib/oe/terminal.py', lineno:
225, function: check_tmux_pane_size
0221:try:
0222:p = sub.Popen('%s list-panes -F
"#{?pane_active,#{pane_height},}"' % tmux,
0223:shell=True,stdout=sub.PIPE,stderr=sub.PIPE)
0224:out, err = p.communicate()
*** 0225:size = int(out.strip())
0226:except OSError as exc:
0227:import errno
0228:if exc.errno == errno.ENOENT:
0229:return None
Exception: ValueError: invalid literal for int() with base 10: ''
ERROR: Function failed: do_menuconfig
ERROR: Logfile of failure stored in:
/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/work/imx6ulevk-poky-linux-gnueabi/linux-fslc/4.4+gitAUTOINC+4fa9845f9b-r0/temp/log.do_menuconfig.22623
ERROR: Task 4
(/home/graute/5411_IBIS/yocto/os-meta-fsl-arm/recipes-kernel/linux/linux-fslc_4.4.bb,
do_menuconfig) failed with exit code '1'
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] build ntp with openssl support
Hello,
how can I build ntp with openssl support?
I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb.
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
PACKAGECONFIG += "openssl"
is this sufficant to enable openssl?
How can I determine if ntp supports sha1?
Best regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build ntp with openssl support
On 16/09/16, Andre McCurdy wrote:
> On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute <oliver.gra...@gmail.com>
> wrote:
> > Hello,
> >
> > how can I build ntp with openssl support?
> >
> > I already created a ntp_%.bbappend file to extend the recipe ntp_4.2.8p4.bb.
> >
> > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> You don't really need this line unless you are adding a file to
> SRC_URI or replacing a file already in SRC_URI with your own version.
>
> > PACKAGECONFIG += "openssl"
>
> This will enable openssl, but it will also disable all the default
> PACKAGECONFIG options (cap, debug and refclocks) which is probably not
> what you want. Try this instead:
>
> PACKAGECONFIG_append = " openssl"
>
> Note the space between " and openssl. It's required.
ok now I see the right configure script options during the configuration
of the ntp build.
--with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
--with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
--with-crypto
But ntp is still build without openssl support. The configure scripts
can't find the relevant openssl stuff.
configure:34762: checking for openssl library directory
configure:34802: result: no
configure:34807: WARNING: libcrypto and libssl not found in any of
/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
configure:34811: checking for openssl include directory
configure:34833: result:
/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
configure:34877: checking if we will use crypto
configure:34879: result: no
configure:35109: checking if we want to use OpenSSL's crypto random (if
available)
configure:35119: result: yes
some clue whats wrong here?
Best regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build ntp with openssl support
On 22/09/16, Khem Raj wrote:
> On Thu, Sep 22, 2016 at 12:16 AM, Oliver Graute <oliver.gra...@gmail.com>
> wrote:
> > On 19/09/16, Oliver Graute wrote:
> >> On 16/09/16, Andre McCurdy wrote:
> >> > On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute <oliver.gra...@gmail.com>
> >> > wrote:
> >> > > Hello,
> >> > >
> >> > > how can I build ntp with openssl support?
> >> > >
> >> > > I already created a ntp_%.bbappend file to extend the recipe
> >> > > ntp_4.2.8p4.bb.
> >> > >
> >> > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> >> >
> >> > You don't really need this line unless you are adding a file to
> >> > SRC_URI or replacing a file already in SRC_URI with your own version.
> >> >
> >> > > PACKAGECONFIG += "openssl"
> >> >
> >> > This will enable openssl, but it will also disable all the default
> >> > PACKAGECONFIG options (cap, debug and refclocks) which is probably not
> >> > what you want. Try this instead:
> >> >
> >> > PACKAGECONFIG_append = " openssl"
> >> >
> >> > Note the space between " and openssl. It's required.
> >>
> >> ok now I see the right configure script options during the configuration
> >> of the ntp build.
> >>
> >> --with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> >> --with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> >> --with-crypto
> >>
> >> But ntp is still build without openssl support. The configure scripts
> >> can't find the relevant openssl stuff.
> >>
> >> configure:34762: checking for openssl library directory
> >> configure:34802: result: no
> >> configure:34807: WARNING: libcrypto and libssl not found in any of
> >> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> >> configure:34811: checking for openssl include directory
> >> configure:34833: result:
> >> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> >> configure:34877: checking if we will use crypto
> >> configure:34879: result: no
> >> configure:35109: checking if we want to use OpenSSL's crypto random (if
> >> available)
> >> configure:35119: result: yes
> >>
> >> some clue whats wrong here?
> >
> > in my sysroots/imx6ulevk/usr/lib I have
> >
> > ls -la libssl*
> >
> > libssl3.so
> > libssl.a
> > libssl.so -> libssl.so.1.0.0
> > libssl.so.1.0.0
> >
> > ls -la libcrypt*
> >
> > libcrypt.a
> > libcrypt_pic.a
> > libcrypt_pic.map
> > libcrypt.so -> ../../lib/libcrypt.so.1
> >
> >
> > but no libcrypto.so. I guess thats the reason why my ntp configure
> > script is complaining.
> >
> > Some ideas how to get libcrypto.so in my /usr/lib folder in the yocto
> > sysroot?
> >
>
> It seems your openssl is not being compiled correctly. Can you go into
> builddir or openssl
> and see if libcrypto.so.1.0.0 is built ? if not then you have to do
> some digging why its not
> configuring to build libcrypto
libcrypto is build by openssl
openssl/1.0.2d-r0/openssl-1.0.2d$ ls -la libcrypt*
libcrypto.a
libcrypto.pc
libcrypto.so -> libcrypto.so.1.0.0
libcrypto.so.1.0.0
but in my sysroot libcrypto is located in lib NOT in usr/lib
the ntp recipe in
meta-openembedded/meta-networking/recipes-support/ntp/ntp_4.2.8p4.bb
defines:
--with-openssl-libdir=${STAGING_LIBDIR}
I assume I need ${STAGING_BASELIBDIR} here instead. But currently I fail
with overwriting this in my bbappend file.
If I use EXTRA_OECONF to overwrite it in my bbappend I see two
--with-openssl-libdir
statements while configuring. The first with /lib the second one with /usr/lib.
EXTRA_OECONF += "\
--with-openssl \
--with-openssl-libdir=${STAGING_BASELIBDIR} \
--with-openssl-incdir=${STAGING_INCDIR} \
--with-crypto \
"
Best Regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build ntp with openssl support
On 19/09/16, Oliver Graute wrote:
> On 16/09/16, Andre McCurdy wrote:
> > On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute <oliver.gra...@gmail.com>
> > wrote:
> > > Hello,
> > >
> > > how can I build ntp with openssl support?
> > >
> > > I already created a ntp_%.bbappend file to extend the recipe
> > > ntp_4.2.8p4.bb.
> > >
> > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> >
> > You don't really need this line unless you are adding a file to
> > SRC_URI or replacing a file already in SRC_URI with your own version.
> >
> > > PACKAGECONFIG += "openssl"
> >
> > This will enable openssl, but it will also disable all the default
> > PACKAGECONFIG options (cap, debug and refclocks) which is probably not
> > what you want. Try this instead:
> >
> > PACKAGECONFIG_append = " openssl"
> >
> > Note the space between " and openssl. It's required.
>
> ok now I see the right configure script options during the configuration
> of the ntp build.
>
> --with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> --with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> --with-crypto
>
> But ntp is still build without openssl support. The configure scripts
> can't find the relevant openssl stuff.
>
> configure:34762: checking for openssl library directory
> configure:34802: result: no
> configure:34807: WARNING: libcrypto and libssl not found in any of
> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> configure:34811: checking for openssl include directory
> configure:34833: result:
> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> configure:34877: checking if we will use crypto
> configure:34879: result: no
> configure:35109: checking if we want to use OpenSSL's crypto random (if
> available)
> configure:35119: result: yes
>
> some clue whats wrong here?
in my sysroots/imx6ulevk/usr/lib I have
ls -la libssl*
libssl3.so
libssl.a
libssl.so -> libssl.so.1.0.0
libssl.so.1.0.0
ls -la libcrypt*
libcrypt.a
libcrypt_pic.a
libcrypt_pic.map
libcrypt.so -> ../../lib/libcrypt.so.1
but no libcrypto.so. I guess thats the reason why my ntp configure
script is complaining.
Some ideas how to get libcrypto.so in my /usr/lib folder in the yocto
sysroot?
some explenation whats the difference between libcrypt.so and libcrypto.so?
Best Regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build ntp with openssl support
On 23/09/16, Lennart Sorensen wrote:
> On Fri, Sep 23, 2016 at 02:19:20PM +0200, Oliver Graute wrote:
> > On 22/09/16, Khem Raj wrote:
> > > On Thu, Sep 22, 2016 at 12:16 AM, Oliver Graute <oliver.gra...@gmail.com>
> > > wrote:
> > > > On 19/09/16, Oliver Graute wrote:
> > > >> On 16/09/16, Andre McCurdy wrote:
> > > >> > On Fri, Sep 16, 2016 at 1:24 AM, Oliver Graute
> > > >> > <oliver.gra...@gmail.com> wrote:
> > > >> > > Hello,
> > > >> > >
> > > >> > > how can I build ntp with openssl support?
> > > >> > >
> > > >> > > I already created a ntp_%.bbappend file to extend the recipe
> > > >> > > ntp_4.2.8p4.bb.
> > > >> > >
> > > >> > > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> > > >> >
> > > >> > You don't really need this line unless you are adding a file to
> > > >> > SRC_URI or replacing a file already in SRC_URI with your own version.
> > > >> >
> > > >> > > PACKAGECONFIG += "openssl"
> > > >> >
> > > >> > This will enable openssl, but it will also disable all the default
> > > >> > PACKAGECONFIG options (cap, debug and refclocks) which is probably
> > > >> > not
> > > >> > what you want. Try this instead:
> > > >> >
> > > >> > PACKAGECONFIG_append = " openssl"
> > > >> >
> > > >> > Note the space between " and openssl. It's required.
> > > >>
> > > >> ok now I see the right configure script options during the
> > > >> configuration
> > > >> of the ntp build.
> > > >>
> > > >> --with-openssl-libdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> > > >> --with-openssl-incdir=/home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> > > >> --with-crypto
> > > >>
> > > >> But ntp is still build without openssl support. The configure scripts
> > > >> can't find the relevant openssl stuff.
> > > >>
> > > >> configure:34762: checking for openssl library directory
> > > >> configure:34802: result: no
> > > >> configure:34807: WARNING: libcrypto and libssl not found in any of
> > > >> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/lib
> > > >> configure:34811: checking for openssl include directory
> > > >> configure:34833: result:
> > > >> /home/graute/5411_IBIS/yocto/build-imx6ulevk-nand/tmp/sysroots/imx6ulevk/usr/include
> > > >> configure:34877: checking if we will use crypto
> > > >> configure:34879: result: no
> > > >> configure:35109: checking if we want to use OpenSSL's crypto random
> > > >> (if available)
> > > >> configure:35119: result: yes
> > > >>
> > > >> some clue whats wrong here?
> > > >
> > > > in my sysroots/imx6ulevk/usr/lib I have
> > > >
> > > > ls -la libssl*
> > > >
> > > > libssl3.so
> > > > libssl.a
> > > > libssl.so -> libssl.so.1.0.0
> > > > libssl.so.1.0.0
> > > >
> > > > ls -la libcrypt*
> > > >
> > > > libcrypt.a
> > > > libcrypt_pic.a
> > > > libcrypt_pic.map
> > > > libcrypt.so -> ../../lib/libcrypt.so.1
> > > >
> > > >
> > > > but no libcrypto.so. I guess thats the reason why my ntp configure
> > > > script is complaining.
> > > >
> > > > Some ideas how to get libcrypto.so in my /usr/lib folder in the yocto
> > > > sysroot?
> > > >
> > >
> > > It seems your openssl is not being compiled correctly. Can you go into
> > > builddir or openssl
> > > and see if libcrypto.so.1.0.0 is built ? if not then you have to do
> > > some digging why its not
> > > configuring to build libcrypto
> >
> > libcrypto is build by openssl
> >
> > openssl/1.0.2d-r0/openssl-1.0.2d$ ls -la libcrypt*
> > libcrypto.a
> > libcrypto.pc
> > libcrypto.so -> libcrypto.so.1.0.0
> > libcrypto.so.1.0.0
> >
> > but in my sysroot libcrypto is located in lib NO
[yocto] Setting directories permissions
Hello List,
I try to define a directory permission for a folder to 0775 instead of
0755 in my recipe. But somewhere in the install and packaging process
this is overwritten.
in my receipe I do this:
do_install() {
install -m 0775 -d ${D}${sysconfdir}/folder1/folder2/
I expect this on the target:
root@box:/etc/folder1# ls -la
drwxrwxr-x2 root webgrp 512 Jan 1 1970 folder2
but I get only this permissions:
root@box:/etc/folder1# ls -la
drwxr-xr-x2 root webgrp 512 Jan 1 1970 folder2
I also tried to define it in the fs-perms.txt file. But this didn't work
either.
/etc/folder1/folder2 0775rootwebgrp false - - -
some clue how to handle such directory permissions the yocto way?
Best Regards,
Oliver
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 26/04/18, Zoran Stojsavljevic wrote: > > I deleted all the build-imx6ulevk folder and build everything from > > scratch with only one thread, waited a few hours for compilation and now > > its working ;) > > Still, I am struggling to understand why??? What is the requirement > behind this ask? The requirement was just get our older yocto (jethro) build running on a PC of a different developer. Often developers have their own flavor of Ubuntu releases and they update to newer versions while they still develop on yocto releases which is much older. Because that yocto release is currently in the field by our costumer. Our product cycle is not so fast to use the newest yocto releases. We started to develop when jethro was up to date. We compiled single threaded just because his PC is a bit unstable on high load. And it crashed a few times on parallel makes. I know that this is not ideal for yocto development. > > As we see, it is much longer (one thread only) than on 14.04!? its takes much longer then with settings PARALLEL_MAKE = "-j 4" BB_NUMBER_THREADS = "4" > Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you > can't)??? And why, after all??? currently not im using only Ubuntu LTS Releases. Perhaps I will try 18.04 LTS which released yesterday ;) Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 25/04/18, Andre McCurdy wrote: > On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute <oliver.gra...@gmail.com> > wrote: > > Hello list, > > > > I try to compile yocto jethro environment which is working > > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. > > > > The compilations stops on gettext-native. > > > > bitbake -k fsl-image-mfgtool-initramfs > > > > | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a > > valid libtool object > > libgettextsrc_la-message.lo should be a short text file. Could you > find it in your build tree and post a copy? > the file was a zero byte file. All other *.lo files in that directory was zero byte too. I assume because of a system crash I had before. Just a bitbake -c cleansstate and rebuild of gettext-native didn't fixed that. I deleted all the build-imx6ulevk folder and build everything from scratch with only one thread, waited a few hours for compilation and now its working ;) > > Some ideas whats the cause for this error? > > At a guess, something a little unusual with the setup of your Kubuntu > system. Combining Ubuntu 16.04 with OE 2.0 isn't so out of the > ordinary and others would certainly have hit the problem before now if > it was always seen. > > Did you install all the standard host dependencies? > > > https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html#packages > yes but thanks for the link as reference. Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] yocto jethro failed on gettext-native
Hello list, I try to compile yocto jethro environment which is working on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. The compilations stops on gettext-native. bitbake -k fsl-image-mfgtool-initramfs make[5]: Entering directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | ../x86_64-linux-libtool --tag=CC --mode=link gcc -isystem/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -release 0.19.4 ../gnulib-lib/libgettextlib.la -lc -no-undefined -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-O1 -o libgettextsrc.la -rpath /home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib libgettextsrc_la-message.lo libgettextsrc_la-po-error.lo libgettextsrc_la-po-xerror.lo libgettextsrc_la-read-catalog-abstract.lo libgettextsrc_la-po-lex.lo libgettextsrc_la-po-gram-gen.lo libgettextsrc_la-po-charset.lo libgettex tsrc_la-read-po.lo libgettextsrc_la-read-properties.lo libgettextsrc_la-read-stringtable.lo libgettextsrc_la-open-catalog.lo libgettextsrc_la-dir-list.lo libgettextsrc_la-str-list.lo libgettextsrc_la-read-catalog.lo libgettextsrc_la-color.lo libgettextsrc_la-write-catalog.lo libgettextsrc_la-write-properties.lo libgettextsrc_la-write-stringtable.lo libgettextsrc_la-write-po.lo libgettextsrc_la-msgl-ascii.lo libgettextsrc_la-msgl-iconv.lo libgettextsrc_la-msgl-equal.lo libgettextsrc_la-msgl-cat.lo libgettextsrc_la-msgl-header.lo libgettextsrc_la-msgl-english.lo libgettextsrc_la-msgl-check.lo libgettextsrc_la-file-list.lo libgettextsrc_la-msgl-charset.lo libgettextsrc_la-po-time.lo libgettextsrc_la-plural-exp.lo libgettextsrc_la-plural-eval.lo libgettextsrc_la-plural-table.lo libgettextsrc_la-format.lo libgettextsrc_la-format-c.lo libgettextsrc_la-format-sh.lo libgettextsrc_la-format-python.lo libgettextsrc_la-format-python-brace.lo libgettextsrc_la-format-lisp.lo libgettextsr c_la-format-elisp.lo libgettextsrc_la-format-librep.lo libgettextsrc_la-format-scheme.lo libgettextsrc_la-format-java.lo libgettextsrc_la-format-csharp.lo libgettextsrc_la-format-awk.lo libgettextsrc_la-format-pascal.lo libgettextsrc_la-format-ycp.lo libgettextsrc_la-format-tcl.lo libgettextsrc_la-format-perl.lo libgettextsrc_la-format-perl-brace.lo libgettextsrc_la-format-php.lo libgettextsrc_la-format-gcc-internal.lo libgettextsrc_la-format-gfc-internal.lo libgettextsrc_la-format-qt.lo libgettextsrc_la-format-qt-plural.lo libgettextsrc_la-format-kde.lo libgettextsrc_la-format-boost.lo libgettextsrc_la-format-lua.lo libgettextsrc_la-format-javascript.lo libgettextsrc_la-read-desktop.lo | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a valid libtool object | Makefile:2285: recipe for target 'libgettextsrc.la' failed | make[5]: *** [libgettextsrc.la] Error 1 | make[5]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | Makefile:2206: recipe for target 'all' failed | make[4]: *** [all] Error 2 | make[4]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | Makefile:1698: recipe for target 'all-recursive' failed | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' | Makefile:1564: recipe for target 'all' failed | make[2]: *** [all] Error 2 | make[2]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' | Makefile:380: recipe for target 'all-recursive' failed | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build' | Makefile:336: recipe for target 'all' failed | make: *** [all] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/temp/log.do_compile.5336) ERROR: Task 531 (virtual:native:/home/us/build/os-poky/meta/recipes-core/gettext/gettext_0.19.4.bb, do_compile) failed with exit code '1' I already tried to reinstall libtool but without success. Some ideas whats the cause for this error? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 25/04/18, Zoran Stojsavljevic wrote: > > I try to compile yocto jethro environment which is working > > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . > > What would be the benefit for the successful compiling of YOCTO Jethro on > Kubuntu 16.04 over Ubuntu 14.04??? I tried to get my Yocto compiled on a PC of a colleague and his installation was a Kubuntu 16.04. I've made the experience that often only additional packages needs to be installed to step over these compile issues. Sometimes its clear from the debug output but in this case I have no Idea which packages is missing. On my develop PC and our Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I can get similar trouble if I update to a newer ubuntu release there too. Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
