Hi, I have not yet finished the grub2 install scripts.
On 16 Jul 2019, at 09:53, Giang Nguyen <[email protected]> wrote: > Hi guys, sorry for the late response. > I use T2 r48382 > > As Rene suggested, I have read and debugged in mkinitrd.sh, the problem found > and solved already. Detail here: > In function copy_dyn_libs, the for loop returns all shared libraries > including their full path. For example, in my case, it shows > .../lib64/ld-linux-x86-64.so.2... If use full path, the rest of script will > not run correctly. The solution is simple, just use basename of library, I > added lib=${lib##*/} after do statement to get basename. > > Now the compilation finished with no error. I tried to Create ISO and > installed on my Virtualbox Machine. Another problem here when Grub and Grub 2 > cannot install. I'm not quite sure the using of Grub and Grub2 in Stone > script. Why do we use both of them. During the hdd partitioning, I chose GPT > and created 500MB partition for BIOS boot, Grub2 seem to be good now, the > installation finished with some errors. I'm off the office 2 days so I can't > remember those errors exactly (check and send them later). > > > > Vào Th 6, 12 thg 7, 2019 vào lúc 20:10 René Rebe <[email protected]> đã > viết: > Hi, > On 12 Jul 2019, at 13:37, scsijon <[email protected]> wrote: > >> >> I'm not Rene, but to start with, >> >> On 12/07/19 13:46, Giang Nguyen wrote: >>> I started a new build for Generic x86_64 minimal with latest t2 and got >>> some minor errors which has been fixed. The last error was at stage 5-Linux >>> 5.1.15 as below: >> >> what is your build's revision number please, that's always important to >> state to start with? >> >>> ... >>> xfrm6_tunnel.ko xfrm6_mode_tunnel.ko xfrm6_tunnel.ko xfrm6_mode_beet.ko >>> ip6_gre.ko fou6.ko nhc_ghc_ext_frag.ko nhc_ipv6.ko nhc_mobility.ko >>> nhc_ghc_udp.ko nhc_udp.ko nhc_ghc_ext_route.ko nhc_routing.ko >>> nhc_fragment.ko >>> nhc_hop.ko 6lowpan.ko nhc_dest.ko nhc_ghc_icmpv6.ko nhc_ghc_ext_dest.ko >>> nhc_ghc_ext_hop.ko x25.ko dns_resolver.ko >>> Injecting programs and configuration ... >>> Warning: /sbin/udevd is dynamically linked! >>> /sbin/udevd NEEDS /lib64/ld-linux-x86-64.so.2 >>> /lib64/ld-linux-x86-64.so.2 SYMLINKS to ld-2.29.so >>> ln: failed to create symbolic link >> >> ? > > I recently had do some some changes for musl libc support. I guess I should > do an all new fresh build to see if I broke some detail for non musl-libc aka > glibc. > > You can read and debug the code in t2’s mkinitrd.sh to see what is going on > in the initrd creation and shared library collection. > > René > >> Do you have a ld-2.29.so to actually link to or have a >> /lib64/ld-linux-x86-64.so.2 already in place so the symlink is not built? >> >> You have done a STRAIGHT build, not a start and stop and restarted, that >> usually fails. >> >>> '/tmp/tmp.LBconae40L.d/lib64/ld-linux-x86-64.so.2': No such file or >>> directory >> >> created during build point and dissapears afterwards, however if the symlink >> isn't there first, and a .so.2 either, it will fail anyway. >> >> ... >>> Plz help me how to solve this? >>> One more question: Do I need to upgrade udev in T2 DDK? >> >> don't know, which ddk are you using, and how far behind is the package? You >> may need to upgrade a number of packages first before the actual build. >> >>> Thanks & Regards >>> My host is running Ubuntu 18.04.1 >> >> >> >> ----------------------------------------------------------- If you wish to >> unsubscribe from this mailing, send mail to >> [email protected] with a subject of: unsubscribe t2 > > -- > ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com > https://exactscan.com | https://ocrkit.com | https://t2sde.org | > https://rene.rebe.de > -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de -- ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin, https://exactcode.com https://exactscan.com | https://ocrkit.com | https://t2sde.org | https://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
