[Buildroot] error when i build buidroot

Esaïe Ledoux NJONGSSI KOUAM kouamdoux at gmail.com
Thu Oct 14 11:35:06 UTC 2021


is it finish ??

Creating filesystem with 61440 1k blocks and 15360 inodes
Filesystem UUID: 721b9a0d-d383-4b06-9469-77944cffb7c6
Superblock backups stored on blocks:
8193, 24577, 40961, 57345

Allocating group tables: done
Writing inode tables: done
Copying files into the device: done
Writing superblocks and filesystem accounting information: done

ln -snf
/home/ledoux/Documents/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot
/home/ledoux/Documents/buildroot/output/staging
>>>   Executing post-image script board/qemu/post-image.sh

:) :)😂😂😂

Le mer. 13 oct. 2021 à 18:26, Peter Seiderer <ps.report at gmx.net> a écrit :

> Hello Esaïe,
>
> On Wed, 13 Oct 2021 12:38:11 +0200, Esaïe Ledoux NJONGSSI KOUAM <
> kouamdoux at gmail.com> wrote:
>
> > so i should modify which mk file ??
> >
> > Le mer. 13 oct. 2021 à 12:34, Esaïe Ledoux NJONGSSI KOUAM <
> > kouamdoux at gmail.com> a écrit :
> >
> > > > Can confirm the error with qemu_x86_64_defconfig, bumping the
> > > > kernel version from 5.10.7 to 5.10.72 (latest 5.10.x) solves
> > > > the problem here...
> > >
> > > i think i should modify some .mk file too even if i bumping this
> version
> > > to the latest kernel version file
>
> Three options:
>
> 1) At your build directory edit the '.config' file, exchange the following
> two
> lines:
>
>         BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.10.7"
>         BR2_LINUX_KERNEL_VERSION="5.10.7"
>
> with:
>
>         BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.10.72"
>         BR2_LINUX_KERNEL_VERSION="5.10.72"
>
> and run 'make'
>
>
> 2) At your build directory run 'make menuconfig', navigate to
>
>         Kernel --> Kernel version
> Now press return and edit the string 5.10.7 to 5.10.72, press return
> to confirm the '<Ok>', navigate to '<Exit>', navigate to '<Exit', confirm
> 'Do you wish to save your new configuration', and run 'make'
>
>
> 3) Edit configs/qemu_x86_64_defconfig, exchange the followig line:
>
>         BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.10.7"
> with
>         BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.10.72"
>
> Now run 'make qemu_x86_64_defconfig', run make
>
> 1) and 2) are equivalent, 3) makes your change permanent but needs
> the 'make qemu_x86_64_defconfig' to apply the change to your current
> build...
>
> Regards,
> Peter
>
>
> > >
> > > Le mar. 12 oct. 2021 à 22:58, Arnout Vandecappelle <arnout at mind.be> a
> > > écrit :
> > >
> > >>
> > >>
> > >> On 12/10/2021 22:52, Peter Seiderer wrote:
> > >> > Hello Esaïe,
> > >> >
> > >> > On Tue, 12 Oct 2021 19:41:11 +0200, Esaïe Ledoux NJONGSSI KOUAM <
> > >> kouamdoux at gmail.com> wrote:
> > >> >
> > >> >> Another problem occur ,
> > >> >> Linux 5-10 building generate compilation errors
> > >> >>
> > >> >> i have a lot of error :(
> > >> >>
> > >> >> arch/x86/entry/thunk_64.o: warning: objtool: missing symbol table
> > >> >> make[3]: *** [scripts/Makefile.build:360 :
> arch/x86/entry/thunk_64.o]
> > >> >> Erreur 1
> > >> >> make[3]: *** Suppression du fichier « arch/x86/entry/thunk_64.o »
> > >> >> make[2]: *** [scripts/Makefile.build:496 : arch/x86/entry] Erreur 2
> > >> >>
> > >> >>    CC      arch/x86/mm/cpu_entry_area.o
> > >> >>    CC      arch/x86/mm/maccess.o
> > >> >>    CC      arch/x86/mm/pkeys.o
> > >> >>    CC      arch/x86/mm/kaslr.o
> > >> >>    CC      arch/x86/mm/pti.o
> > >> >>    AR      arch/x86/mm/built-in.a
> > >> >> make[1]: *** [Makefile:1805 : arch/x86] Erreur 2
> > >> >> make[1]: *** Attente des tâches non terminées....
> > >> >> make[1] : on quitte le répertoire
> > >> >> « /home/ledoux/Documents/buildroot/output/build/linux-5.10.7 »
> > >> >> make: *** [package/pkg-generic.mk:294 :
> > >> >>
> > >>
> /home/ledoux/Documents/buildroot/output/build/linux-5.10.7/.stamp_built]
> > >> >> Erreur 2
> > >> >
> > >> > Can confirm the error with qemu_x86_64_defconfig, bumping the
> > >> > kernel version from 5.10.7 to 5.10.72 (latest 5.10.x) solves
> > >> > the problem here...
> > >>
> > >>   I head just confirmed the same thing :-)
> > >>
> > >>   Regards,
> > >>   Arnout
> > >>
> > >> >
> > >> > Regards,
> > >> > Peter
> > >> >
> > >> >>
> > >> >> definitely, I don't know what to do.
> > >> >> I'm afraid to solve this problem and run into others.
> > >> >>
> > >> >>
> > >> >>
> > >> >> Le mar. 12 oct. 2021 à 15:01, Esaïe Ledoux NJONGSSI KOUAM <
> > >> >> kouamdoux at gmail.com> a écrit :
> > >> >>
> > >> >>> i have seen something , ...
> > >> >>> It is working very well , because the problem was rsync version ,
> so i
> > >> >>> have take the better version
> > >> >>> https://github.com/WayneD/rsync/blob/master/INSTALL.md , ...
> > >> >>> thank you for all
> > >> >>>
> > >> >>> Le mar. 12 oct. 2021 à 14:41, Esaïe Ledoux NJONGSSI KOUAM <
> > >> >>> kouamdoux at gmail.com> a écrit :
> > >> >>>
> > >> >>>>> in the buildroot directory. If that gives an error, there is
> really
> > >> >>>> something
> > >> >>>>> wrong with your OS.
> > >> >>>>
> > >> >>>> i'm trying to reinstall rsync , i hope that something will be
> fine
> > >> until
> > >> >>>> the end
> > >> >>>>
> > >> >>>> Le mar. 12 oct. 2021 à 13:00, Esaïe Ledoux NJONGSSI KOUAM <
> > >> >>>> kouamdoux at gmail.com> a écrit :
> > >> >>>>
> > >> >>>>>    > As Joachim asked, can you provide the output of
> > >> >>>>>
> > >> >>>>>    >    pwd
> > >> >>>>>
> > >> >>>>>> and
> > >> >>>>>
> > >> >>>>>    >    findmnt
> > >> >>>>>
> > >> >>>>> ledoux at kali:~/Documents/buildroot$ pwd
> > >> >>>>> /home/ledoux/Documents/buildroot
> > >> >>>>> ledoux at kali:~/Documents/buildroot$ findmnt
> > >> >>>>> TARGET                         SOURCE      FSTYPE  OPTIONS
> > >> >>>>> /                              /dev/sda10  ext4
> > >> >>>>>   rw,relatime,errors=remount-ro
> > >> >>>>> ├─/sys                         sysfs       sysfs
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/kernel/security       securityfs  securit
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/fs/cgroup             cgroup2     cgroup2
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/fs/pstore             pstore      pstore
> > >> >>>>>   rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/firmware/efi/efivars  efivarfs    efivarf
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/fs/bpf                none        bpf
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/kernel/tracing        tracefs     tracefs
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/kernel/debug          debugfs     debugfs
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/sys/kernel/config         configfs    configf
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ └─/sys/fs/fuse/connections   fusectl     fusectl
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> ├─/proc                        proc        proc
> > >> >>>>>   rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ └─/proc/sys/fs/binfmt_misc   systemd-1   autofs
> > >> >>>>>   rw,relatime,fd=29,pgrp=1,time
> > >> >>>>> │   └─/proc/sys/fs/binfmt_misc binfmt_misc binfmt_
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> ├─/dev                         udev        devtmpf
> > >> >>>>> rw,nosuid,relatime,size=17018
> > >> >>>>> │ ├─/dev/pts                   devpts      devpts
> > >> >>>>>   rw,nosuid,noexec,relatime,gid
> > >> >>>>> │ ├─/dev/shm                   tmpfs       tmpfs
>  rw,nosuid,nodev
> > >> >>>>> │ ├─/dev/hugepages             hugetlbfs   hugetlb
> > >> >>>>> rw,relatime,pagesize=2M
> > >> >>>>> │ └─/dev/mqueue                mqueue      mqueue
> > >> >>>>>   rw,nosuid,nodev,noexec,relati
> > >> >>>>> ├─/run                         tmpfs       tmpfs
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/run/lock                  tmpfs       tmpfs
> > >> >>>>> rw,nosuid,nodev,noexec,relati
> > >> >>>>> │ ├─/run/rpc_pipefs            sunrpc      rpc_pip rw,relatime
> > >> >>>>> │ └─/run/user/1000             tmpfs       tmpfs
> > >> >>>>> rw,nosuid,nodev,relatime,size
> > >> >>>>> │   └─/run/user/1000/doc       portal      fuse.po
> > >> >>>>> rw,nosuid,nodev,relatime,user
> > >> >>>>> ├─/tmp                         /dev/sda9   ext4    rw,relatime
> > >> >>>>> ├─/var                         /dev/sda7   ext4    rw,relatime
> > >> >>>>> ├─/home                        /dev/sda11  ext4    rw,relatime
> > >> >>>>> ├─/boot/efi                    /dev/sda2   vfat
> > >> >>>>>   rw,relatime,fmask=0077,dmask=
> > >> >>>>> └─/media/ledoux/Data           /dev/sda6   fuseblk
> > >> >>>>> rw,nosuid,nodev,relatime,user
> > >> >>>>>
> > >> >>>>>
> > >> >>>>>
> > >> >>>>> Le lun. 11 oct. 2021 à 22:25, Arnout Vandecappelle <
> arnout at mind.be>
> > >> a
> > >> >>>>> écrit :
> > >> >>>>>
> > >> >>>>>>    Hi Esaie,
> > >> >>>>>>
> > >> >>>>>>    Please don't top-post, but reply inline like I do below.
> Note
> > >> that
> > >> >>>>>> this
> > >> >>>>>> requires configuring your mailer to quote replies properly
> (i.e.
> > >> put >
> > >> >>>>>> markers
> > >> >>>>>> in front of each line).
> > >> >>>>>>
> > >> >>>>>>
> > >> >>>>>> On 11/10/2021 12:20, Esaïe Ledoux NJONGSSI KOUAM wrote:
> > >> >>>>>>> i have tried
> > >> >>>>>>> git clone git://git.buildroot.net/buildroot <
> > >> >>>>>> http://git.buildroot.net/buildroot>
> > >> >>>>>>> make qemu_x86_64_defconfig
> > >> >>>>>>> make
> > >> >>>>>>>
> > >> >>>>>>> i have type it on Documents folder that has ext4 file system
> > >> >>>>>>
> > >> >>>>>>    As Joachim asked, can you provide the output of
> > >> >>>>>>
> > >> >>>>>>       pwd
> > >> >>>>>>
> > >> >>>>>> and
> > >> >>>>>>
> > >> >>>>>>       findmnt
> > >> >>>>>>
> > >> >>>>>> so we can see if the filesystem really is ext4, or it has
> some
> > >> weird
> > >> >>>>>> mount
> > >> >>>>>> option, or anything else that could explain the issue?
> > >> >>>>>>
> > >> >>>>>>    You can also try:
> > >> >>>>>>
> > >> >>>>>>       touch foo
> > >> >>>>>>       chmod 666 foo
> > >> >>>>>>
> > >> >>>>>> in the buildroot directory. If that gives an error, there is
> really
> > >> >>>>>> something
> > >> >>>>>> wrong with your OS.
> > >> >>>>>>
> > >> >>>>>>    Regards,
> > >> >>>>>>    Arnout
> > >> >>>>>>
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>> still now i have the same error
> > >> >>>>>>>
> > >> >>>>>>> Le dim. 10 oct. 2021 à 21:57, Joachim Wiberg <
> troglobit at gmail.com
> > >> >>>>>>> <mailto:troglobit at gmail.com>> a écrit :
> > >> >>>>>>>
> > >> >>>>>>>      Hi,
> > >> >>>>>>>
> > >> >>>>>>>      On 10/10/21 6:52 PM, Esaïe Ledoux NJONGSSI KOUAM wrote:
> > >> >>>>>>>       > no filesystem has been configured ...
> > >> >>>>>>>       > I'm just trying the default configuration
> > >> >>>>>>>
> > >> >>>>>>>      This is fine.  I think you've got something really
> wrong
> > >> with your
> > >> >>>>>>>      Kali Linux host system.
> > >> >>>>>>>
> > >> >>>>>>>       > should i configure file system for my buildroot ??
> > >> >>>>>>>
> > >> >>>>>>>      No, we mean the file system you are using for building
> > >> Buildroot
> > >> >>>>>> on,
> > >> >>>>>>>      in your Kali Linux install.  The rsync error looks as
> if
> > >> your disk
> > >> >>>>>>>      partition is a non-native Linux file system, like FAT,
> which
> > >> does
> > >> >>>>>>>      not support the operations rsync tries to perform.
> > >> >>>>>>>
> > >> >>>>>>>      How have you set up your Kali Linux?  Do you have the
> > >> buildroot
> > >> >>>>>> git
> > >> >>>>>>>      sources checked out to your home directory or some
> other
> > >> >>>>>> directory,
> > >> >>>>>>>      perhaps shared with Windows?  If so, I'd definitely
> avoid
> > >> that.
> > >> >>>>>> You
> > >> >>>>>>>      can check the filesystem of your build directory by
> > >> comparing the
> > >> >>>>>>>      output of
> > >> >>>>>>>
> > >> >>>>>>>          pwd
> > >> >>>>>>>
> > >> >>>>>>>      with the output from
> > >> >>>>>>>
> > >> >>>>>>>          findmnt
> > >> >>>>>>>
> > >> >>>>>>>      On my system I have ext4 in the FSTYPE column for my
> home
> > >> >>>>>> directory,
> > >> >>>>>>>      which is in the / TARGET.
> > >> >>>>>>>
> > >> >>>>>>>      I finished my install of Kali in my own VM.  It crashed
> badly
> > >> >>>>>> before
> > >> >>>>>>>      I gave it enough disk (40 GiB) and RAM (4 GiB).  That's
> > >> another
> > >> >>>>>> thing
> > >> >>>>>>>      that might have messed up your build tree.
> > >> >>>>>>>
> > >> >>>>>>>       > the error persists even if i compile it as normal
> user
> > >> >>>>>>>
> > >> >>>>>>>      Well that's good to know, at least it's consistent.
> Just
> > >> beware
> > >> >>>>>>>      that if you reuse the same source tree, having switched
> to
> > >> another
> > >> >>>>>>>      user, a lot of files may still have root as the owner,
> which
> > >> may
> > >> >>>>>>>      give you other problems.  Either `sudo chown -R
> user:user .`
> > >> from
> > >> >>>>>>>      inside the Buildroot source tree, or check out a new
> tree.
> > >> >>>>>>>
> > >> >>>>>>>      Best regards
> > >> >>>>>>>        /Joachim
> > >> >>>>>>>
> > >> >>>>>>>
> > >> >>>>>>> _______________________________________________
> > >> >>>>>>> buildroot mailing list
> > >> >>>>>>> buildroot at buildroot.org
> > >> >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot
> > >> >>>>>>>
> > >> >>>>>>
> > >> >>>>>
> > >> >
> > >>
> > >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20211014/48e41991/attachment-0001.html>


More information about the buildroot mailing list