custom sama5d27 board ,buildroot failes

[yektaayduk]

Dear Community members,
Step-1
I have a custom board .
One week ago I was able to build sdcard.img for sama5d27 and running it.
I was working in tree , not under BR2_EXTERNAL .
The setup was uclibc and linux4sam_6.0 and at91-bootstrap_3.8.11 .
Than I start to try running user code with pthreads and my program crashed with segfault.

Step-2A
I decided to switch to glibc and new Linux release.

Its recommended to make clean ,but it deleted the output folder.
I setup a new virtual machine with glibc and Linux4sam_6.2 and at91-bootstrap_3.9.0 .

I changed sama5d2_xplained_defconfig (USE_GLIBC)
At first everything is build , image folder has sdcard image, bootstrap ,uboot ,rootfs etc. OK.

Step-2B
Than I build my board_defconfig .
Buildroot complained ,it can find uboot-env.bin . image folder was not updated.

Step-2C
I tried sama5d2_xplained_defconfig again .It also failes .?
Buildroot complained ,it can find something else zImage .
Image folder always has only rootfs.tar ,rootfs.ext4 ,rootfs.ext2 , not more? genimage.tmp is empty.

Question: Cant we build multiple projects back to back ?
How to find a solution?

[blue_z]

I have a custom board .
...
Than I start to try running user code with pthreads and my program crashed with segfault.

Instead of trying a different libc, you should have verified the functionality of your "custom board" and investigated the cause of that segfault.

image folder was not updated.
...
I tried sama5d2_xplained_defconfig again .It also failes .?
Buildroot complained ,it can find something else zImage .
Image folder always has only rootfs.tar ,rootfs.ext4 ,rootfs.ext2 , not more? genimage.tmp is empty.

Your cursory descriptions are insufficient.
The steps you are performing and the results you obtain are not clear at all.

Question: Cant we build multiple projects back to back ?

You wrote that you have just one custom board, so I don't understand exactly what you mean by "multiple projects back to back".
I use an external toolchain and an external directory for downloads to facilitate faster builds after a `make clean` or `make mrproper`.

A single install of Buildroot is simply not suited for "multiple projects", e.g. different boards that do not utilize a common kernel.
You would be better off having individual Buildroot directories for each project board.

How to find a solution?

The only advice/help I can offer is:
Before you issue another `make xxx_defconfig`, you are expected to `make mrproper` first.
If you modify the Buildroot configuration using `make menuconfig`, then `make` should automatically rebuild all affected packages.
If you're concerned that `make` could miss a dependency, then use `make clean` to force a full rebuild.


Regards