* [Buildroot] error when i build buidroot @ 2021-10-10 7:58 Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 12:00 ` Edgar Bonet 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 7:58 UTC (permalink / raw) To: buildroot [-- Attachment #1.1: Type: text/plain, Size: 4388 bytes --] Hey everybody , It is my first time to use buildroot. I have read the manual and i want to use it for embedded linux projects . So i have : clone the project build for qemu_x86_64 by typing "qemu_x86_64_defconfig" then type "make" After that i have seen some error, i don't know how to solve it : "rsync -a --ignore-times --exclude .svn --exclude .git --exclude .hg --exclude .bzr --exclude CVS --chmod=u=rwX,go=rX --exclude .empty --exclude '*~' system/skeleton/ /root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/" So this command generate a lot of errors : rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/dev": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/profile.d": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/media": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/mnt": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/opt": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/proc": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/root": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/run": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/sys": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/tmp": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/bin": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/lib": Function not implemented (38) rsync: [generator] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/sbin": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.group.nsk97w": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.hosts.yBRyXu": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.passwd.0Uncqt": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.profile.0E8enu": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.protocols.DJb4ew": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.services.AO2ruv": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/.shadow.QE0FTt": Function not implemented (38) rsync: [receiver] failed to set permissions on "/root/buildroot/output/host/x86_64-buildroot-linux-uclibc/sysroot/etc/profile.d/.umask.sh.IN0rhw": Function not implemented (38) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3] make: *** [package/pkg-generic.mk:333 : /root/buildroot/output/build/skeleton-init-common/.stamp_staging_installed] Erreur 23 Please how can i fix that ?? Because i have not seen something talk about how to avoid it [-- Attachment #1.2: Type: text/html, Size: 4997 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 7:58 [Buildroot] error when i build buidroot Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 12:00 ` Edgar Bonet 2021-10-10 15:48 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Edgar Bonet @ 2021-10-10 12:00 UTC (permalink / raw) To: buildroot Hello! Esaïe Ledoux Njongssi Kouam wrote: > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" I guess you mean “make qemu_x86_64_defconfig”. > rsync [...] system/skeleton/ /root/buildroot/[...] You are doing this as root? > rsync: [generator] failed to set permissions on "[...]": > Function not implemented (38) This sounds like you are using a filesystem that doesn't support Unix-type permissions.[1] Is this the case? What kind of FS is this? Could you try on a Unixish filesystem? Regards, Edgar Bonet. [1] https://unix.stackexchange.com/questions/12203 _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 12:00 ` Edgar Bonet @ 2021-10-10 15:48 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 17:27 ` Joachim Wiberg 0 siblings, 2 replies; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 15:48 UTC (permalink / raw) To: Edgar Bonet; +Cc: buildroot [-- Attachment #1.1: Type: text/plain, Size: 963 bytes --] yes , i'm doing this as root So the file system that i'm using is ext4 Le dim. 10 oct. 2021 à 14:01, Edgar Bonet <bonet@grenoble.cnrs.fr> a écrit : > Hello! > > Esaïe Ledoux Njongssi Kouam wrote: > > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" > > I guess you mean “make qemu_x86_64_defconfig”. > > > rsync [...] system/skeleton/ /root/buildroot/[...] > > You are doing this as root? > > > rsync: [generator] failed to set permissions on "[...]": > > Function not implemented (38) > > This sounds like you are using a filesystem that doesn't support > Unix-type permissions.[1] Is this the case? What kind of FS is this? > Could you try on a Unixish filesystem? > > Regards, > > Edgar Bonet. > > [1] https://unix.stackexchange.com/questions/12203 > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot > [-- Attachment #1.2: Type: text/html, Size: 1642 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 15:48 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 17:27 ` Joachim Wiberg 1 sibling, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 15:49 UTC (permalink / raw) To: Edgar Bonet; +Cc: buildroot [-- Attachment #1.1: Type: text/plain, Size: 1225 bytes --] i have taged buildroot on stackoverflow : https://stackoverflow.com/questions/69420545/buildroot-build-system-errors Le dim. 10 oct. 2021 à 17:48, Esaïe Ledoux NJONGSSI KOUAM < kouamdoux@gmail.com> a écrit : > yes , i'm doing this as root > > So the file system that i'm using is ext4 > > Le dim. 10 oct. 2021 à 14:01, Edgar Bonet <bonet@grenoble.cnrs.fr> a > écrit : > >> Hello! >> >> Esaïe Ledoux Njongssi Kouam wrote: >> > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" >> >> I guess you mean “make qemu_x86_64_defconfig”. >> >> > rsync [...] system/skeleton/ /root/buildroot/[...] >> >> You are doing this as root? >> >> > rsync: [generator] failed to set permissions on "[...]": >> > Function not implemented (38) >> >> This sounds like you are using a filesystem that doesn't support >> Unix-type permissions.[1] Is this the case? What kind of FS is this? >> Could you try on a Unixish filesystem? >> >> Regards, >> >> Edgar Bonet. >> >> [1] https://unix.stackexchange.com/questions/12203 >> _______________________________________________ >> buildroot mailing list >> buildroot@buildroot.org >> https://lists.buildroot.org/mailman/listinfo/buildroot >> > [-- Attachment #1.2: Type: text/html, Size: 2241 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 0 replies; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 15:49 UTC (permalink / raw) To: Edgar Bonet; +Cc: buildroot [-- Attachment #1.1: Type: text/plain, Size: 1490 bytes --] i have taged buildroot on stackoverflow : https://stackoverflow.com/questions/69420545/buildroot-build-system-errors Le dim. 10 oct. 2021 à 17:49, Esaïe Ledoux NJONGSSI KOUAM < kouamdoux@gmail.com> a écrit : > i have taged buildroot on stackoverflow : > https://stackoverflow.com/questions/69420545/buildroot-build-system-errors > > Le dim. 10 oct. 2021 à 17:48, Esaïe Ledoux NJONGSSI KOUAM < > kouamdoux@gmail.com> a écrit : > >> yes , i'm doing this as root >> >> So the file system that i'm using is ext4 >> >> Le dim. 10 oct. 2021 à 14:01, Edgar Bonet <bonet@grenoble.cnrs.fr> a >> écrit : >> >>> Hello! >>> >>> Esaïe Ledoux Njongssi Kouam wrote: >>> > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" >>> >>> I guess you mean “make qemu_x86_64_defconfig”. >>> >>> > rsync [...] system/skeleton/ /root/buildroot/[...] >>> >>> You are doing this as root? >>> >>> > rsync: [generator] failed to set permissions on "[...]": >>> > Function not implemented (38) >>> >>> This sounds like you are using a filesystem that doesn't support >>> Unix-type permissions.[1] Is this the case? What kind of FS is this? >>> Could you try on a Unixish filesystem? >>> >>> Regards, >>> >>> Edgar Bonet. >>> >>> [1] https://unix.stackexchange.com/questions/12203 >>> _______________________________________________ >>> buildroot mailing list >>> buildroot@buildroot.org >>> https://lists.buildroot.org/mailman/listinfo/buildroot >>> >> [-- Attachment #1.2: Type: text/html, Size: 2872 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 15:48 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 17:27 ` Joachim Wiberg 2021-10-10 16:52 ` Esaïe Ledoux NJONGSSI KOUAM 1 sibling, 1 reply; 25+ messages in thread From: Joachim Wiberg @ 2021-10-10 17:27 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM, Edgar Bonet; +Cc: buildroot [-- Attachment #1.1.1: Type: text/plain, Size: 1672 bytes --] Hi! Kali Linux is a Debian derivative, so it should work fine as build host. I've not used it myself, but I'm installing it in a VM now to check the build steps to see if I can reproduce your problem. On 10/10/21 5:48 PM, Esaïe Ledoux NJONGSSI KOUAM wrote: > Le dim. 10 oct. 2021 à 14:01, Edgar Bonet <bonet@grenoble.cnrs.fr > <mailto:bonet@grenoble.cnrs.fr>> a écrit : > > Esaïe Ledoux Njongssi Kouam wrote: > > > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" > > I guess you mean “make qemu_x86_64_defconfig”. > > > rsync [...] system/skeleton/ /root/buildroot/[...] > > You are doing this as root? > yes , i'm doing this as root I think you might want to browse through the manual again, in particular Chapter 4, https://buildroot.org/downloads/manual/manual.html: | Important: you can and should build everything as a normal user. There | is no need to be root to configure and use Buildroot. By running all | commands as a regular user, you protect your system against packages | behaving badly during compilation and installation. I'll retry the steps as a regular user in my efforts. > > > rsync: [generator] failed to set permissions on "[...]": > > > Function not implemented (38) > > This sounds like you are using a filesystem that doesn't support > > Unix-type permissions.[1] Is this the case? What kind of FS is this? > So the file system that i'm using is ext4 Just to double-check, because "Function not implemented 38)" is really not expected on a build host with Ext4. Did you mean the file system you configured for your Buildroot image, or your build system? Best regards /Joachim [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 17:27 ` Joachim Wiberg @ 2021-10-10 16:52 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 19:57 ` Joachim Wiberg 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 16:52 UTC (permalink / raw) To: Joachim Wiberg; +Cc: Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 1959 bytes --] no filesystem has been configured ... I'm just trying the default configuration should i configure file system for my buildroot ?? Le dim. 10 oct. 2021 à 19:27, Joachim Wiberg <troglobit@gmail.com> a écrit : > Hi! > > Kali Linux is a Debian derivative, so it should work fine as build host. > I've not used it myself, but I'm installing it in a VM now to check the > build steps to see if I can reproduce your problem. > > On 10/10/21 5:48 PM, Esaïe Ledoux NJONGSSI KOUAM wrote: > > Le dim. 10 oct. 2021 à 14:01, Edgar Bonet <bonet@grenoble.cnrs.fr > > <mailto:bonet@grenoble.cnrs.fr>> a écrit : > > > Esaïe Ledoux Njongssi Kouam wrote: > > > > build for qemu_x86_64 by typing "qemu_x86_64_defconfig" > > > I guess you mean “make qemu_x86_64_defconfig”. > > > > rsync [...] system/skeleton/ /root/buildroot/[...] > > > You are doing this as root? > > yes , i'm doing this as root > > I think you might want to browse through the manual again, in particular > Chapter 4, https://buildroot.org/downloads/manual/manual.html: > > | Important: you can and should build everything as a normal user. There > | is no need to be root to configure and use Buildroot. By running all > | commands as a regular user, you protect your system against packages > | behaving badly during compilation and installation. > > I'll retry the steps as a regular user in my efforts. > > > > > rsync: [generator] failed to set permissions on "[...]": > > > > Function not implemented (38) > > > This sounds like you are using a filesystem that doesn't support > > > Unix-type permissions.[1] Is this the case? What kind of FS is this? > > So the file system that i'm using is ext4 > > Just to double-check, because "Function not implemented 38)" is really > not expected on a build host with Ext4. Did you mean the file system > you configured for your Buildroot image, or your build system? > > Best regards > /Joachim > > [-- Attachment #1.2: Type: text/html, Size: 2729 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 16:52 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-10 19:57 ` Joachim Wiberg 2021-10-11 10:20 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Joachim Wiberg @ 2021-10-10 19:57 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM; +Cc: Edgar Bonet, buildroot [-- Attachment #1.1.1: Type: text/plain, Size: 1600 bytes --] 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 [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-10 19:57 ` Joachim Wiberg @ 2021-10-11 10:20 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-11 20:24 ` Arnout Vandecappelle 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-11 10:20 UTC (permalink / raw) To: Joachim Wiberg; +Cc: Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 1959 bytes --] i have tried git clone git://git.buildroot.net/buildroot make qemu_x86_64_defconfig make i have type it on Documents folder that has ext4 file system still now i have the same error Le dim. 10 oct. 2021 à 21:57, Joachim Wiberg <troglobit@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 > > [-- Attachment #1.2: Type: text/html, Size: 2752 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-11 10:20 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-11 20:24 ` Arnout Vandecappelle 2021-10-12 11:00 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Arnout Vandecappelle @ 2021-10-11 20:24 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM, Joachim Wiberg; +Cc: Edgar Bonet, buildroot 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@gmail.com > <mailto:troglobit@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@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot > _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-11 20:24 ` Arnout Vandecappelle @ 2021-10-12 11:00 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 12:41 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 11:00 UTC (permalink / raw) To: Arnout Vandecappelle; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 6012 bytes --] > As Joachim asked, can you provide the output of > pwd > and > findmnt ledoux@kali:~/Documents/buildroot$ pwd /home/ledoux/Documents/buildroot ledoux@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@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@gmail.com > > <mailto:troglobit@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@buildroot.org > > https://lists.buildroot.org/mailman/listinfo/buildroot > > > [-- Attachment #1.2: Type: text/html, Size: 7806 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 11:00 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 12:41 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 12:56 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 13:01 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 2 replies; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 12:41 UTC (permalink / raw) To: Arnout Vandecappelle; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 6545 bytes --] > 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@gmail.com> a écrit : > > As Joachim asked, can you provide the output of > > > pwd > > > and > > > findmnt > > ledoux@kali:~/Documents/buildroot$ pwd > /home/ledoux/Documents/buildroot > ledoux@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@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@gmail.com >> > <mailto:troglobit@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@buildroot.org >> > https://lists.buildroot.org/mailman/listinfo/buildroot >> > >> > [-- Attachment #1.2: Type: text/html, Size: 8436 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 12:41 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 12:56 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 13:01 ` Esaïe Ledoux NJONGSSI KOUAM 1 sibling, 0 replies; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 12:56 UTC (permalink / raw) To: Arnout Vandecappelle; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 7069 bytes --] 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@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@gmail.com> a écrit : > >> > As Joachim asked, can you provide the output of >> >> > pwd >> >> > and >> >> > findmnt >> >> ledoux@kali:~/Documents/buildroot$ pwd >> /home/ledoux/Documents/buildroot >> ledoux@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@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@gmail.com >>> > <mailto:troglobit@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@buildroot.org >>> > https://lists.buildroot.org/mailman/listinfo/buildroot >>> > >>> >> [-- Attachment #1.2: Type: text/html, Size: 9151 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 12:41 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 12:56 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 13:01 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 17:41 ` Esaïe Ledoux NJONGSSI KOUAM 1 sibling, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 13:01 UTC (permalink / raw) To: Arnout Vandecappelle; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 7067 bytes --] 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@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@gmail.com> a écrit : > >> > As Joachim asked, can you provide the output of >> >> > pwd >> >> > and >> >> > findmnt >> >> ledoux@kali:~/Documents/buildroot$ pwd >> /home/ledoux/Documents/buildroot >> ledoux@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@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@gmail.com >>> > <mailto:troglobit@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@buildroot.org >>> > https://lists.buildroot.org/mailman/listinfo/buildroot >>> > >>> >> [-- Attachment #1.2: Type: text/html, Size: 9152 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 13:01 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 17:41 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 20:52 ` Peter Seiderer 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 17:41 UTC (permalink / raw) To: Arnout Vandecappelle; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 8412 bytes --] 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 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@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@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@gmail.com> a écrit : >> >>> > As Joachim asked, can you provide the output of >>> >>> > pwd >>> >>> > and >>> >>> > findmnt >>> >>> ledoux@kali:~/Documents/buildroot$ pwd >>> /home/ledoux/Documents/buildroot >>> ledoux@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@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@gmail.com >>>> > <mailto:troglobit@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@buildroot.org >>>> > https://lists.buildroot.org/mailman/listinfo/buildroot >>>> > >>>> >>> [-- Attachment #1.2: Type: text/html, Size: 10821 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 17:41 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-12 20:52 ` Peter Seiderer 2021-10-12 20:58 ` Arnout Vandecappelle 0 siblings, 1 reply; 25+ messages in thread From: Peter Seiderer @ 2021-10-12 20:52 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM; +Cc: Joachim Wiberg, Edgar Bonet, buildroot Hello Esaïe, On Tue, 12 Oct 2021 19:41:11 +0200, Esaïe Ledoux NJONGSSI KOUAM <kouamdoux@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... 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@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@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@gmail.com> a écrit : > >> > >>> > As Joachim asked, can you provide the output of > >>> > >>> > pwd > >>> > >>> > and > >>> > >>> > findmnt > >>> > >>> ledoux@kali:~/Documents/buildroot$ pwd > >>> /home/ledoux/Documents/buildroot > >>> ledoux@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@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@gmail.com > >>>> > <mailto:troglobit@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@buildroot.org > >>>> > https://lists.buildroot.org/mailman/listinfo/buildroot > >>>> > > >>>> > >>> _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 20:52 ` Peter Seiderer @ 2021-10-12 20:58 ` Arnout Vandecappelle 2021-10-13 10:34 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Arnout Vandecappelle @ 2021-10-12 20:58 UTC (permalink / raw) To: Peter Seiderer, Esaïe Ledoux NJONGSSI KOUAM Cc: Joachim Wiberg, Edgar Bonet, buildroot 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@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@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@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@gmail.com> a écrit : >>>> >>>>> > As Joachim asked, can you provide the output of >>>>> >>>>> > pwd >>>>> >>>>>> and >>>>> >>>>> > findmnt >>>>> >>>>> ledoux@kali:~/Documents/buildroot$ pwd >>>>> /home/ledoux/Documents/buildroot >>>>> ledoux@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@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@gmail.com >>>>>>> <mailto:troglobit@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@buildroot.org >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot >>>>>>> >>>>>> >>>>> > _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-12 20:58 ` Arnout Vandecappelle @ 2021-10-13 10:34 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-13 10:38 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-13 10:34 UTC (permalink / raw) To: Arnout Vandecappelle Cc: Joachim Wiberg, Peter Seiderer, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 10227 bytes --] > 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 Le mar. 12 oct. 2021 à 22:58, Arnout Vandecappelle <arnout@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@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@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@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@gmail.com> a écrit : > >>>> > >>>>> > As Joachim asked, can you provide the output of > >>>>> > >>>>> > pwd > >>>>> > >>>>>> and > >>>>> > >>>>> > findmnt > >>>>> > >>>>> ledoux@kali:~/Documents/buildroot$ pwd > >>>>> /home/ledoux/Documents/buildroot > >>>>> ledoux@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@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@gmail.com > >>>>>>> <mailto:troglobit@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@buildroot.org > >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot > >>>>>>> > >>>>>> > >>>>> > > > [-- Attachment #1.2: Type: text/html, Size: 16301 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-13 10:34 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-13 10:38 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-13 16:26 ` Peter Seiderer 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-13 10:38 UTC (permalink / raw) To: Arnout Vandecappelle Cc: Joachim Wiberg, Peter Seiderer, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 10665 bytes --] so i should modify which mk file ?? Le mer. 13 oct. 2021 à 12:34, Esaïe Ledoux NJONGSSI KOUAM < kouamdoux@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 > > Le mar. 12 oct. 2021 à 22:58, Arnout Vandecappelle <arnout@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@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@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@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@gmail.com> a écrit : >> >>>> >> >>>>> > As Joachim asked, can you provide the output of >> >>>>> >> >>>>> > pwd >> >>>>> >> >>>>>> and >> >>>>> >> >>>>> > findmnt >> >>>>> >> >>>>> ledoux@kali:~/Documents/buildroot$ pwd >> >>>>> /home/ledoux/Documents/buildroot >> >>>>> ledoux@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@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@gmail.com >> >>>>>>> <mailto:troglobit@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@buildroot.org >> >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot >> >>>>>>> >> >>>>>> >> >>>>> >> > >> > [-- Attachment #1.2: Type: text/html, Size: 16741 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-13 10:38 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-13 16:26 ` Peter Seiderer 2021-10-14 11:35 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Peter Seiderer @ 2021-10-13 16:26 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM; +Cc: Joachim Wiberg, Edgar Bonet, buildroot Hello Esaïe, On Wed, 13 Oct 2021 12:38:11 +0200, Esaïe Ledoux NJONGSSI KOUAM <kouamdoux@gmail.com> wrote: > so i should modify which mk file ?? > > Le mer. 13 oct. 2021 à 12:34, Esaïe Ledoux NJONGSSI KOUAM < > kouamdoux@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@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@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@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@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@gmail.com> a écrit : > >> >>>> > >> >>>>> > As Joachim asked, can you provide the output of > >> >>>>> > >> >>>>> > pwd > >> >>>>> > >> >>>>>> and > >> >>>>> > >> >>>>> > findmnt > >> >>>>> > >> >>>>> ledoux@kali:~/Documents/buildroot$ pwd > >> >>>>> /home/ledoux/Documents/buildroot > >> >>>>> ledoux@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@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@gmail.com > >> >>>>>>> <mailto:troglobit@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@buildroot.org > >> >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot > >> >>>>>>> > >> >>>>>> > >> >>>>> > >> > > >> > > _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-13 16:26 ` Peter Seiderer @ 2021-10-14 11:35 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-14 15:24 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-14 11:35 UTC (permalink / raw) To: Peter Seiderer; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 13837 bytes --] 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@gmx.net> a écrit : > Hello Esaïe, > > On Wed, 13 Oct 2021 12:38:11 +0200, Esaïe Ledoux NJONGSSI KOUAM < > kouamdoux@gmail.com> wrote: > > > so i should modify which mk file ?? > > > > Le mer. 13 oct. 2021 à 12:34, Esaïe Ledoux NJONGSSI KOUAM < > > kouamdoux@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@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@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@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@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@gmail.com> a écrit : > > >> >>>> > > >> >>>>> > As Joachim asked, can you provide the output of > > >> >>>>> > > >> >>>>> > pwd > > >> >>>>> > > >> >>>>>> and > > >> >>>>> > > >> >>>>> > findmnt > > >> >>>>> > > >> >>>>> ledoux@kali:~/Documents/buildroot$ pwd > > >> >>>>> /home/ledoux/Documents/buildroot > > >> >>>>> ledoux@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@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@gmail.com > > >> >>>>>>> <mailto:troglobit@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@buildroot.org > > >> >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot > > >> >>>>>>> > > >> >>>>>> > > >> >>>>> > > >> > > > >> > > > > > [-- Attachment #1.2: Type: text/html, Size: 23327 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-14 11:35 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-14 15:24 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-14 19:30 ` Arnout Vandecappelle 0 siblings, 1 reply; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-14 15:24 UTC (permalink / raw) To: Peter Seiderer; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 14431 bytes --] That's the output in my terminal ... Can i hope that everything is okay!?? Le jeu. 14 oct. 2021 à 12:35, Esaïe Ledoux NJONGSSI KOUAM < kouamdoux@gmail.com> a écrit : > 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@gmx.net> a écrit : > >> Hello Esaïe, >> >> On Wed, 13 Oct 2021 12:38:11 +0200, Esaïe Ledoux NJONGSSI KOUAM < >> kouamdoux@gmail.com> wrote: >> >> > so i should modify which mk file ?? >> > >> > Le mer. 13 oct. 2021 à 12:34, Esaïe Ledoux NJONGSSI KOUAM < >> > kouamdoux@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@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@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@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@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@gmail.com> a écrit : >> > >> >>>> >> > >> >>>>> > As Joachim asked, can you provide the output of >> > >> >>>>> >> > >> >>>>> > pwd >> > >> >>>>> >> > >> >>>>>> and >> > >> >>>>> >> > >> >>>>> > findmnt >> > >> >>>>> >> > >> >>>>> ledoux@kali:~/Documents/buildroot$ pwd >> > >> >>>>> /home/ledoux/Documents/buildroot >> > >> >>>>> ledoux@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@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@gmail.com >> > >> >>>>>>> <mailto:troglobit@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@buildroot.org >> > >> >>>>>>> https://lists.buildroot.org/mailman/listinfo/buildroot >> > >> >>>>>>> >> > >> >>>>>> >> > >> >>>>> >> > >> > >> > >> >> > > >> >> [-- Attachment #1.2: Type: text/html, Size: 24059 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-14 15:24 ` Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-14 19:30 ` Arnout Vandecappelle 2021-10-14 19:48 ` Peter Seiderer 0 siblings, 1 reply; 25+ messages in thread From: Arnout Vandecappelle @ 2021-10-14 19:30 UTC (permalink / raw) To: Esaïe Ledoux NJONGSSI KOUAM, Peter Seiderer Cc: Joachim Wiberg, Edgar Bonet, buildroot On 14/10/2021 17:24, Esaïe Ledoux NJONGSSI KOUAM wrote: > That's the output in my terminal ... > Can i hope that everything is okay!?? > > Le jeu. 14 oct. 2021 à 12:35, Esaïe Ledoux NJONGSSI KOUAM <kouamdoux@gmail.com > <mailto:kouamdoux@gmail.com>> a écrit : > > 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 Yes that looks OK. Regards, Arnout [snip] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-14 19:30 ` Arnout Vandecappelle @ 2021-10-14 19:48 ` Peter Seiderer 2021-10-15 5:47 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 1 reply; 25+ messages in thread From: Peter Seiderer @ 2021-10-14 19:48 UTC (permalink / raw) To: Arnout Vandecappelle Cc: Joachim Wiberg, Esaïe Ledoux NJONGSSI KOUAM, Edgar Bonet, buildroot On Thu, 14 Oct 2021 21:30:40 +0200, Arnout Vandecappelle <arnout@mind.be> wrote: > On 14/10/2021 17:24, Esaïe Ledoux NJONGSSI KOUAM wrote: > > That's the output in my terminal ... > > Can i hope that everything is okay!?? > > > > Le jeu. 14 oct. 2021 à 12:35, Esaïe Ledoux NJONGSSI KOUAM <kouamdoux@gmail.com > > <mailto:kouamdoux@gmail.com>> a écrit : > > > > 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 > > Yes that looks OK. > > Regards, > Arnout And take a look at board/qemu/x86_64/readme.txt on hints how to run the result in qemu... Regards, Peter > > [snip] > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [Buildroot] error when i build buidroot 2021-10-14 19:48 ` Peter Seiderer @ 2021-10-15 5:47 ` Esaïe Ledoux NJONGSSI KOUAM 0 siblings, 0 replies; 25+ messages in thread From: Esaïe Ledoux NJONGSSI KOUAM @ 2021-10-15 5:47 UTC (permalink / raw) To: Peter Seiderer; +Cc: Joachim Wiberg, Edgar Bonet, buildroot [-- Attachment #1.1: Type: text/plain, Size: 1580 bytes --] Done. Le jeu. 14 oct. 2021 à 20:48, Peter Seiderer <ps.report@gmx.net> a écrit : > On Thu, 14 Oct 2021 21:30:40 +0200, Arnout Vandecappelle <arnout@mind.be> > wrote: > > > On 14/10/2021 17:24, Esaïe Ledoux NJONGSSI KOUAM wrote: > > > That's the output in my terminal ... > > > Can i hope that everything is okay!?? > > > > > > Le jeu. 14 oct. 2021 à 12:35, Esaïe Ledoux NJONGSSI KOUAM < > kouamdoux@gmail.com > > > <mailto:kouamdoux@gmail.com>> a écrit : > > > > > > 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 > > > > Yes that looks OK. > > > > Regards, > > Arnout > > And take a look at board/qemu/x86_64/readme.txt on hints how > to run the result in qemu... > > Regards, > Peter > > > > > [snip] > > _______________________________________________ > > buildroot mailing list > > buildroot@buildroot.org > > https://lists.buildroot.org/mailman/listinfo/buildroot > > [-- Attachment #1.2: Type: text/html, Size: 2590 bytes --] [-- Attachment #2: Type: text/plain, Size: 150 bytes --] _______________________________________________ buildroot mailing list buildroot@buildroot.org https://lists.buildroot.org/mailman/listinfo/buildroot ^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2021-10-15 5:48 UTC | newest] Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-10-10 7:58 [Buildroot] error when i build buidroot Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 12:00 ` Edgar Bonet 2021-10-10 15:48 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 15:49 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 17:27 ` Joachim Wiberg 2021-10-10 16:52 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-10 19:57 ` Joachim Wiberg 2021-10-11 10:20 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-11 20:24 ` Arnout Vandecappelle 2021-10-12 11:00 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 12:41 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 12:56 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 13:01 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 17:41 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-12 20:52 ` Peter Seiderer 2021-10-12 20:58 ` Arnout Vandecappelle 2021-10-13 10:34 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-13 10:38 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-13 16:26 ` Peter Seiderer 2021-10-14 11:35 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-14 15:24 ` Esaïe Ledoux NJONGSSI KOUAM 2021-10-14 19:30 ` Arnout Vandecappelle 2021-10-14 19:48 ` Peter Seiderer 2021-10-15 5:47 ` Esaïe Ledoux NJONGSSI KOUAM
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.