Bitbake -g recipe Might emit what you want in some form

#bitbake #yocto

there can be multiple entries in SERIAL_CONSOLES so you might try adding instead of replacing SERIAL_CONSOLES += "115200;ttymxc0" might work

This is a bug and this should be fixed to use full machine name for override since we do not have nezha SoC override No it’s unrelated

Perhaps it’s using locked sstate which might be the reason

Probably, but again if you need a function from a library you include it on linker cmdline if it’s intrinsics then compiler driver doing the needed is best way Preferably without introducing compiler

this would mean that you want to rely on side effects of -pthread which may work with gcc but may not work with clang or other compiler drivers. The issue you have is that some variables are needing a

does backporting https://github.com/curl/curl/commit/50efb0822aa0e0ab165158dd0a26e65a2290e6d2 to curl help ?

in your fortran app recipe you have to add DEPENDS = "libgfortran"

Post log.do_complile perhaps that will have the needed link line

#honister #make #yocto

It’s linker cmdline which is interesting here please post it and that will help to see further

#honister #make #yocto

Yes There already is beagleV machine and it will be derived from that I have plans to add it if Someone is working on it please let me know

its possible to build baremetal toolchains, e.g. look at meta-riscv baremetal machines e.g. https://github.com/riscv/meta-riscv/blob/master/conf/machine/baremetal-riscv32.conf you can do MACHINE=barem

you might have to figure out how the clone should work firstly. then you can either encode it into SRC_URI, but I would say be careful since you might leak password and url info into packages, other o

#yocto

which release branch are you using? <tagliapietra.alessandro@...> wrote:

Ok then next thing you want to check is where the reported stripped file is located and even if it does not work then perhaps look into removing these files if they are not needed

<tagliapietra.alessandro@...> wrote: what package folders do you see under packages-split/ folder in your build area for this recipe ?

The prebuilds are for other architectures. so perhaps you can rm them in a do_install_append() or if they are really needed you perhaps would also need INSANE_SKIP_<name of package> = "arch" eventuall

This will be valiant effort but my advice is don't go alone if you want to undertake this SOC sdks have lot of nitty gritty issues that will pop up along the way and unless you have someone from SOC s

Oh I see. we do support aarch64 as build host, so if you are trying 64bit OS on rpi then it should work although, rpi4 may not have enough muscle to build, perhaps using SSD with rpi4 might help a bit

are you on a x86_64 host? Secondly try to uncomment SDKMACHINE setting in local.conf and see if it helps. Also check if your default shell is bash or dash.