Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matt Taylor
    @64
    happy to make one
    my mistake for not seeing this earlier, i figured you can set env vars from within build scripts but it seems that you can't
    Joey Gouly
    @jgouly
    @phil-opp what are the plans around FS?
    Philipp Oppermann
    @phil-opp
    @64 My plan was to let bootimage parse a package.metadata.bootimage.bootloader-env table, where the user can define environment variables that should be set when building the kernel. Would this solve your problems? (Letting the bootloader itself parse the Cargo.toml would work too, but it would require adding TOML parsing, which bootimage does already anyway)
    @jgouly You mean a file system post on the Writing an OS in Rust blog? I don't have concrete plans yet as I want to write about other things first (multitasking, userspace, system calls)
    Joey Gouly
    @jgouly
    @phil-opp yeah I did. I started to write an ext2fs reader to try integrate
    Philipp Oppermann
    @phil-opp
    Cool!
    Matt Taylor
    @64
    @phil-opp should work
    Philipp Oppermann
    @phil-opp
    @64 Do you have any idea about rust-osdev/bootloader#49 It seems to affect multiple people, but I don't have the time to look at it at the moment.
    Matt Taylor
    @64
    will investigate
    Philipp Oppermann
    @phil-opp
    Thanks a lot!
    Joey Gouly
    @jgouly
    listing files in the root of an ext2 fs!
    (It's read-only, and actually just include_bytes!(), into the kernel, so not actually 'reading from disk')
    Philipp Oppermann
    @phil-opp
    Cool!
    Matt Taylor
    @64
    can you move the 'gets stuck at "booting first stage..."' into the in progress column? i don't have the perms
    Philipp Oppermann
    @phil-opp
    Done
    I also tried to give you permissions, but I couldn't figure our how
    I just gave you write access to bootloader and bootimage now, I think this should include the project board. I set up the repositories so that each pull request requires an approving review before it can be merged.
    Matt Taylor
    @64
    do you think we can make the font8x8 dependency only be pulled in if the vga_300x200 feature is enabled? would cut down on compile times and binary size a bit more
    seems to work
    Philipp Oppermann
    @phil-opp
    Sure, I think just making it optional and letting the vga_300x200 feature depend on it should suffice
    Matt Taylor
    @64
    what’s the status of rust-osdev/bootloader#69 i think i misunderstood - should i just close it?
    Philipp Oppermann
    @phil-opp
    I don't think that the PR has any effect since the Cargo.lock already specifies version 0.2.4. Normally I'm against updating the Cargo.toml for each new version of a dependency (as long as no new features are used) since it generates unneeded churn. On the other hand, fixedvec isn't really a dependency that is updated often, so I think the update would be fine in this case.
    Matt Taylor
    @64
    :thumbsup:
    i'm working on the build script right now so that it can parse Cargo.toml and grab the values as discussed
    Philipp Oppermann
    @phil-opp
    Great, thanks a lot!
    Joey Gouly
    @jgouly
    @phil-opp is there something I can do to get more debug info from core, when using cargo xbuild?
    Joey Gouly
    @jgouly
    (seems like some of the core functions dont have any nice source, when i use objdump -S)
    Matt Taylor
    @64
    which file are you objdumping?
    target/x86_64-foo/debug/foo is the elf file of your kernel, it should contain debug information
    Joey Gouly
    @jgouly
    my kernel, but it's core::write that doesnt have much info
    Matt Taylor
    @64
    ah right
    seems to work for me
    Joey Gouly
    @jgouly
    weird
    Matt Taylor
    @64
    actually no you're right some of this stuff doesn't have any source
    have you checked to see whether the source is given for std? just in a normal binary @jgouly
    Joey Gouly
    @jgouly
    no, but I think I saw some other core functions had some info
    I was just wondering if there was some extra options or something when using xbuild
    Matt Taylor
    @64
    i have a feeling that the internals of write (and format_args) are some compiler black magic, which is probably why no source is shown for these bits
    but maybe phil has something to say on the matter
    Joey Gouly
    @jgouly
    ah could be
    Philipp Oppermann
    @phil-opp
    Yes, format_args is a compiler builtin, so this could be the reason that no source is shown
    However, core is compiled in release mode by cargo-xbuild. Maybe it's possible to enable more debug info
    Philipp Oppermann
    @phil-opp
    But I'm not sure about this
    Joey Gouly
    @jgouly
    Thanks for the info
    Shreyas Lad
    @PenetratingShot
    Everytime I try to install xbuild or bootloader, I get this error:
    error: linking with `cc` failed: exit code: 1
      |
      = note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" "/home/shreyaslad/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "/tmp/cargo-installN69jE3/release/build/ryu-f793e224f68c02e0/build_script_build-f793e224f68c02e0.build_script_build.e2q2k4vm- 
    
    ... 
    
    
    cgu.0.rcgu.o" "/tmp/cargo-installN69jE3/release/build/ryu-f793e224f68c02e0/build_script_build-f793e224f68c02e0.build_script_build.e2q2k4vm-cgu.1.rcgu.o" "/tmp/cargo-installN69jE3/release/build/ryu-f793e224f68c02e0/build_script_build-f793e224f68c02e0.build_script_build.e2q2k4vm-cgu.10.rcgu.o" "/tmp/cargo-
      = note: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/Scrt1.o: unrecognized relocation (0x2a) in section `.text'
              /usr/bin/ld: final link failed: Bad value
              collect2: error: ld returned 1 exit status
    Yes I have tried cargo clean
    Matt Taylor
    @64
    you mean bootimage?
    Matt Taylor
    @64
    what’s your binutils version