13188 2019-02-20 01:45:30 +0000 systemd 239 bash file test bug 2019-08-29 14:47:01 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.6.1 All arm RESOLVED WORKSFORME Medium critical 2.8 M4 1 wei.qingjun wei.qingjun jku meta.mr.watcher meta.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 83044 0 wei.qingjun 2019-02-20 01:45:30 +0000 line 231: [ ! -e ${D}/init ] && ln -s ${rootlibexecdir}/systemd/systemd ${D}/init Will trigger symbolic link already exists error. On Ubuntu 18.04 bash. Should it be [ ! -L ${D}/init ] && ln -s ${rootlibexecdir}/systemd/systemd ${D}/init 83048 1 wei.qingjun 2019-02-20 03:01:07 +0000 I tried to modify the code but I still get error: Log below: | Running custom install script 'XXXXXXXXXXX/tmp/hosttools/sh -c touch $DESTDIR/usr' | ln: failed to create symbolic link 'XXXXXXXXXX/tmp/work/cortexa17hf-neon-vfpv4-rk-linux-gnueabi/systemd/1_239-r0/image/sbin/init': File exists No idea why the init file exists. 83049 2 wei.qingjun 2019-02-20 03:33:28 +0000 I can confirm it is a bug. Althought I have not traced to the cause. I had to add a line to remove the sbin/init file. mv ${D}/${base_sbindir}/init Then I had to mount the ext4 rootfs and manully create the link. The current symbolic link is linked to a wrong location. 83065 3 randy.macleod 2019-02-21 15:47:30 +0000 Can you explain in detail how to reproduce the error? Lots of people are building systemd but perhaps this is a silent failure that we've been ignoring or it could be that you have a custom install script and have made an error. We need more info to proceed. 83071 4 wei.qingjun 2019-02-21 16:12:10 +0000 I have a local recipe that installs a systemd service to start my system at startup. The bb file is something like below. Hope it helps. Thanks Qingjun SUMMARY = "XXX" LICENSE = "CLOSED" PV = "1.0" SRC_URI = "... \ " S = "${WORKDIR}" inherit systemd inherit bin_package INSANE_SKIP_${PN} = "ldflags" INHIBIT_PACKAGE_STRIP = "1" INHIBIT_SYSROOT_STRIP = "1" INHIBIT_PACKAGE_DEBUG_SPLIT = "1" do_compile() { } do_install () { install -Dm 0644 ${S}/XXX.service ${D}/${systemd_unitdir}/system/XXX.service } SYSTEMD_SERVICE_${PN} = "XXX.service" INSANE_SKIP_${PN} += "installed-vs-shipped" 83097 5 sjolley.yp.pm 2019-02-23 00:05:43 +0000 Chen, It appears an answer to the question has been given. I have cleared NEEDINFO. Thanks, Stephen 83419 6 jku 2019-04-03 08:32:26 +0000 (In reply to comment #0) > line 231: > [ ! -e ${D}/init ] && ln -s ${rootlibexecdir}/systemd/systemd ${D}/init This is not line 231 in yocto 2.6.1 systemd_239.bb. Do you have local modifications or are you actually running some other yocto version? 83420 7 Qi.Chen 2019-04-03 09:04:20 +0000 wei, Sorry for late reply. I guess the cause is that your ubuntu18.04 does not have /lib/systemd/systemd, causing ${D}/init being a dead link. I think you are right, using '-L' could solve this problem. As an alternative, you can use 'ln -sf' instead 'ln -s'. You can send out patch if you like, as you have already found the solution. You can send patch to openembedded-core@lists.openembedded.org, for both thud and master branches. If not convenient, I'll do it for you. Best Regards, Chen Qi 83958 8 Qi.Chen 2019-05-28 01:09:21 +0000 wei, Do you still have this bug reproduced on your host? 84469 9 Qi.Chen 2019-07-22 02:13:45 +0000 I cannot reproduce this problem, nor can I find out the host environment of the reporter. 84470 10 wei.qingjun 2019-07-22 02:42:29 +0000 Qingjun(In reply to comment #9) > I cannot reproduce this problem, nor can I find out the host environment of > the reporter. Sorry didn't have a chance to try new release of Yocto. Will try to test against latest release in this week. Regards 84474 11 wei.qingjun 2019-07-22 18:15:04 +0000 (In reply to comment #9) > I cannot reproduce this problem, nor can I find out the host environment of > the reporter. Hello Chen, I just tried systemd 2.41 on latest warrior-next branch. The problem still exists Below is the log. BTW I am running on a Ubuntu 18.04 X64. ln: failed to create symbolic link '/home/weiqj/rk-yocto-bsp/libre-hub/tmp/work/cortexa17hf-neon-vfpv4-rk-linux-gnueabi/systemd/1_241+AUTOINC+c1f8ff8d0d-r0/image/sbin/init': $ WARNING: exit code 1 from a shell command. ERROR: Function failed: do_install (log file is located at /home/weiqj/rk-yocto-bsp/libre-hub/tmp/work/cortexa17hf-neon-vfpv4-rk-linux-gnueabi/systemd/1_241+AUTOINC+c1f8ff8d0$ Still, I had to manually modify the script to make it work. 84475 12 Qi.Chen 2019-07-23 01:16:50 +0000 Hi Wei, I'm wondering why other people don't have such problem. I also use ubuntu hosts. Do you have some additional layer which might have systemd bbappend files? What does your run.do_install file under ${WORKDIR}/temp look like? What creates the ${D}/init link before this line? [ ! -e ${D}/init ] && xxx Could you please show your run.do_install file? Also, you mentioned ${D}/init, but your error log is about ${D}/sbin/init. Anyway, I think showing your run.do_install will help. 84731 13 randy.macleod 2019-08-22 15:01:22 +0000 Wei? 84764 14 randy.macleod 2019-08-29 14:47:01 +0000 No reponse so I'm closing the defect. We'd be happy to have the defect re-opened if the needed info is provided.