Error in build.sh

[dosadi]

Hi,

When I run:

$ ./setup.sh Pulling code from GitHub... Creating disk image... Building src/Pure64... Building src/BareMetal... Building src/BareMetal-Monitor... Building src/BMFS... Building OS image... Done!

$ ./build.sh Building src/Pure64... Building src/BareMetal... Building src/BareMetal-Monitor... Building src/BMFS... mkdir: cannot create directory ‘bin’: File exists

[... add a new b_output() call to BareMetal-OS/src/BareMetal-Demo/src/helloc.c before the 'Hello, world!' b_output() call for testing purposes ...]

$ ./install-demos.sh Error: File already exists. Error: File already exists. Error: File already exists. Error: File already exists. Error: File already exists.

$ ./run.sh

load Enter file number: 4 exec Hello, world!

This is what I see - the b_output() call which should have come before the 'Hello, world!' print isn't there. I can't tell if helloc.c is being rebuilt or not, but it also(?) looks like install-demos.sh isn't overwriting the old demo files on the BMFS image or rebuilding the whole disk image from scratch, depending on what is necessary.

[ghost]

What platform are you on? Are you on a Mac? There have been issues before with the shell scripts when running them on a Mac.

[dosadi]

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;} I wish :-).  I just run Linux on an ultra-cheap Dell laptop.  Why?Jon Sent via BlackBerry Hub+ Inbox for Android From: [email protected]: August 7, 2020 11:04 PMTo: [email protected]: [email protected]: [email protected]; [email protected]: Re: [ReturnInfinity/BareMetal-OS] Error in build.sh (#45)
What platform are you on? Are you on a Mac?

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

[ghost]

Alrighty. I sent a PR for the mkdir error. Looks like the function (in BMFS, src/bmfs.c:64),

void create(char* filename, unsigned long long int maxsize)

could use a -f or --force flag, which ignores the error if the file already exists.

I'm not quite sure what the last part of your problem is. Can you explain that a bit more?

[dosadi]

Wow, responding by email resulted in really mangled response text. Gotta remember to not do that...

Anyway, what I was trying to do is to modify the helloc.c demo to get a better understanding of how the build system works, and I was having trouble getting the test change to build and install on the bmfs disk image. I have an older BM source tree, and I am trying to learn how the new tree differs from the one I have been using.

[ghost]

Okay, I'll take a look at it at some point tomorrow if Ian doesn't beat me to it.

[IanSeyler]

Merged! Thanks for adding that.

[IanSeyler]

@dosadi You'll want to use the latest source tree. That way we can test it on our end.

[dosadi]

I actually have both the old one and the new one I can use for testing, that's what I should have said. I am trying to port the old code from being directly jumped to at 0x200000 over to being run as one of the applications from the monitor, same as the 'helloc' application. That's why I noticed the issue, is that I was starting to play with adding my own code to 'helloc'....