OSDev.org

I downloaded the meaty skeleton repo from github and compared the files to the tutorials. No differences. So, i studied the code line for line and did my best to understand it. I went to compile it the way it said to on the article. It got held up on iso.sh with the error:
I used a downloaded i686 cross compiler from this link found on the cross compiling article: http://newos.org/toolchains/i686-elf-4. ... _64.tar.xz

Can anybody help me please?

It's better to build cross-compiler on your own. As you can see, this cross-compiler is incompatible with the options that are used in build scripts. Either way, you should learn more about what happenes inside these scripts to fully understand what commands and options are used and why.

Yeah, I really wanted to originally, but it's super confusing to me and I kept getting errors. Do you know of any clear as day video tutorials? I'm really a visual learner.

I'm sorry but I didn't use anything beyond this article: http://wiki.osdev.org/GCC_Cross-Compiler .
Be sure to download latest compiler and binutils versions: a lot of people reported strange error messages just because they've downloaded ancient versions of binutils due to alphabetic sorting of names.

cheapskate01 wrote:Yeah, I really wanted to originally, but it's super confusing to me and I kept getting errors.

It's really important that you make sure you have the right tools for the job and know how to use them. Don't skip that part. If you can't get something to work, learn how you can.

I've followed the steps in that wiki more then a dozen times and it hasn't ever failed for me. Just make sure you use the latest binutils for it. I think that's v2.25.1.

What platform are you working on and which errors did you get?

Nutterts wrote:

cheapskate01 wrote:Yeah, I really wanted to originally, but it's super confusing to me and I kept getting errors.

It's really important that you make sure you have the right tools for the job and know how to use them. Don't skip that part. If you can't get something to work, learn how you can.

I've followed the steps in that wiki more then a dozen times and it hasn't ever failed for me. Just make sure you use the latest binutils for it. I think that's v2.25.1.

What platform are you working on and which errors did you get?

I don't remember, It was last year on my old machine and the hard drive was fried. It was running arch I think.

I'm rebuilding right now under 64bit LinuxMint with binutils version 2.24 so it isn't ancient and has been tested with my gcc version.

I'll let you know how it goes.

Edit: Is it okay If I get a bunch of notes? I don't know if I should watch out for these or not.

cheapskate01 wrote:Edit: Is it okay If I get a bunch of notes? I don't know if I should watch out for these or not.

I haven't built a cross-compiler before but usually when you get "notes" or "warnings" they're intended for the developers to help them improve their code and don't mean that your compiled object files won't work. Short answer, "notes" and "warnings" aren't anything you need to worry about as long as the build process completes without errors.

onlyonemac wrote:

cheapskate01 wrote:Edit: Is it okay If I get a bunch of notes? I don't know if I should watch out for these or not.

I haven't built a cross-compiler before but usually when you get "notes" or "warnings" they're intended for the developers to help them improve their code and don't mean that your compiled object files won't work. Short answer, "notes" and "warnings" aren't anything you need to worry about as long as the build process completes without errors.

Okay, thanks. I was just wondering because multiple sources tell me to treat warnings as errors.

Also, Why do I need to have the source for TeXinfo If i'm not building it?

cheapskate01 wrote:Edit: Is it okay If I get a bunch of notes? I don't know if I should watch out for these or not.

Depends, when compiling my own stuff I treat warnings like errors. On a warning the build will fail.

But that should be something you set as a commandline option thru your makefile. So with other people's code I assume that if having no warnings is important they will have done the same. I do try to read them but it's generally seemingly harmless stuff.

cheapskate01 wrote:Also, Why do I need to have the source for TeXinfo If i'm not building it?

I think that build system asks you for binaries, not for source. You can avoid this dependency by specifying something like --disable-docs while configuring your cross-compiler.

Nable wrote:

cheapskate01 wrote:Also, Why do I need to have the source for TeXinfo If i'm not building it?

I think that build system asks you for binaries, not for source. You can avoid this dependency by specifying something like --disable-docs while configuring your cross-compiler.

Ahh. Thanks. I spent 30 mins downloading and extracting the tar of source bc my internet decided to act up at 8:30 last night.

Also, the cross compiler compiled successfully! Now to try the meaty skeleton...

Good Game. Thanks for the help guys!

Now i guess the next step would be to port the 20 extra functions I wrote on BareBones kernel to these files.

Edit: Done

Nable wrote:I'm sorry but I didn't use anything beyond this article: http://wiki.osdev.org/GCC_Cross-Compiler .
Be sure to download latest compiler and binutils versions: a lot of people reported strange error messages just because they've downloaded ancient versions of binutils due to alphabetic sorting of names.

Yes, i were getting these strange messages until i compile with same gcc and same binutils version...

Before i was compiling a gcc 5.1.0 - binutils 2.5.10 cross compiler with gcc 4.5 and a really old binutils version... And i was getting endless of error messages...

Last month i wanted to try the compiling gcc again. I fully readed the http://wiki.osdev.org/GCC_Cross-Compiler article and build my cross compiler successfully. I build my gcc 5.2.0 - binutils 2.5.10 cross compiler with gcc 5.2.1 (beta) and binutils 2.5.10 successfully...

GCC 4.5 is really old. It makes sense to use at least 4.7.