GithubHelp home page GithubHelp logo

Comments (8)

sbz-12d avatar sbz-12d commented on July 17, 2024 1

@pino-kim

  1. I think ...you'd better make some bash script to change local.conf in build/conf when set environment.

As you suggested, by commenting the line "rm -f $DIR" works. I was able to setup environment without rebuilding.

-> When you encounter your issue.When set up build environment? or while Running bitbake?
Dmesg log point you something wrong? I guess you attach your system by terminal program(protocal ssh). If true, do you use tmux or screen when set up yocto and run bitbake?

Now everything works fine. Thanks a lot

from meta-riscv.

pino-kim avatar pino-kim commented on July 17, 2024

Hi @sbz-12d

can I join your issue?
At first,I have ask some questoion about your issue.

  1. I don't never heard about scratch. So can you give me more information scratch???
    Is a yocto's tool? Or meaniing something? (I understand 'scratch' meanning base. am i right?)

Answer to you question as I known

  1. If remove line 11, in setup.sh, build dir will not removed by script.
    rm -rf $DIR

2, 3. I think you should reference auto.conf. when setup.sh run, It well be generated. you can find it /build/conf. Also add meta directory in your bblayer.conf.

your host build system is look fine to build riscv yocto. I mean enough space.
If you have error log, I recommend you to attach it.

from meta-riscv.

kraj avatar kraj commented on July 17, 2024

Can you tell me where is sstate-cache directory inside build tree.

from meta-riscv.

sbz-12d avatar sbz-12d commented on July 17, 2024

Hi @pino-kim

Thanks for your reply.

  1. I don't never heard about scratch. So can you give me more information scratch???
    Is a yocto's tool? Or meaniing something? (I understand 'scratch' meanning base. am i right?)
  1. "From scratch" in this context means from beginning or from starting. I meant to say that running setup.sh again (already built image) starts the building of the image the from the beginning.
  1. If remove line 11, in setup.sh, build dir will not removed by script.
    rm -rf $DIR
  1. I will remove " rm -rf $DIR " line from setup.sh and will check it. But currently what i'm doing is, once i have built the image i made a copy of local.conf file from build/conf/local.conf and whenever i want to setup environment for bitbake, i'm doing "source openembedded-core/oe-init-build-env " and copying the backup local.conf file to build/conf folder (replacing the file inside it.). I was able to run the bitbake and build the image without any problem.

If you have error log, I recommend you to attach it.

  1. There was no error log generated. since system was abruptly logging out by killing all the processes current user owns. i have checked the dmesg as well.
    3.1 please note that the error is getting generated when i tried to setup bitbake environment to already built image by doing "source openembedded-core/oe-init-build-env " only and running "bitbake core-image-full-cmdline" command.
    3.2 I was also getting the same error when i did . ./setup.sh and did "bitbake core-image-lsb-sdk".

from meta-riscv.

sbz-12d avatar sbz-12d commented on July 17, 2024

Hi @kraj

Thanks for your reply

Can you tell me where is sstate-cache directory inside build tree.

It is in build directory only. build/sstate-cache

from meta-riscv.

pino-kim avatar pino-kim commented on July 17, 2024

@sbz-12d
Thanks to let me understand your full context.

  1. I think ...you'd better make some bash script to change local.conf in build/conf when set environment.
  1. There was no error log generated. since system was abruptly logging out by killing all the processes current user owns. i have checked the dmesg as well.
    3.1 please note that the error is getting generated when i tried to setup bitbake environment to already built image by doing "source openembedded-core/oe-init-build-env " only and running "bitbake core-image-full-cmdline" command.
    3.2 I was also getting the same error when i did . ./setup.sh and did "bitbake core-image-lsb-sdk".

-> When you encounter your issue.When set up build environment? or while Running bitbake?
Dmesg log point you something wrong? I guess you attach your system by terminal program(protocal ssh). If true, do you use tmux or screen when set up yocto and run bitbake?

from meta-riscv.

kraj avatar kraj commented on July 17, 2024

@sbz-12d are there any changes we need to the script to make it better please propose them with a pull request.

from meta-riscv.

kraj avatar kraj commented on July 17, 2024

this should be fixed now

from meta-riscv.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.