gcc 3

[damonbrinkley]

I just don't don't get on with Linux, too much of a sloth for my likes (and yes, I know its fast, but it seems to struggle too much for me)

Haha, I hear ya man. No, it's a sloth for everybody - some just don't want to admit it. I'm not a n00b, I've used Linux before. Windows isn't open source, and Microsoft's biz strategies aren't all that good either, but Linux just isn't ready for desktop users. Period.

Guess I didn't get that memo and need to take Linux off of my desktop here at work and at home and install Winders back on them. I'll let my fellow Linux users know that it's not ready for the desktop and they need to put WIndows back on their machines also. Thanks for letting me know it was a 'sloth' and I just didn't know it........

[Perica]

..

[jrfritz]

Thats because there are bugs in KDE3....log out of kde 3 and login under IceWM and see the speed!

[Perica]

..

[Pype.Clicker]

Hey,

By telling the linker to "--oformat binary", you asking it to produce a flat binary file (no headers, no symbols, no relocation. Just bits of .text and .data gathered together and located to a specific address you give it).
All you can do with such a file is load it at the right address (and it's up to the linker to guess what that address could be) and jump at the start of it to run it ...

You're more than likely asking also to perform another operation on this binary file (linking against something else, relocating, whatever) which requires it to be a "normal" file (a Protected Executable, as \/\/ind0\/\/$ used to use -- which is just Common Object File Format (COFF) with a MS-DOS .EXE compliant header).


off-topic: your hate towards linux seems unjustified for me. You seem to ignore what linux is and expect it to run "out of a box" ... what naive this is ... You cannot have a fast GUI under linux until you tell it what your graphical card is and provided the right kernel modules to handle it ... And you cannot expect it to boot quickly while it is performing a safety-check on your hard disk ... Faster (journalized) file system that *never* need a safety-check exist for linux (reiserFS) and it is open source too (so if you take the time for it you can understand and master it ).
Linux isn't ready for hard-core g4merz and unscientific people. That's some kind of elite-only product which expect YOU to know how to do things. That's what Unix is all about: "by experts for experts".

I'm sorry to say this but you're obviously not yet an expert, and you probably won't successfully install any Linux distribution until you manage to read a Howto, or find a Guru that will do the dirty job for you

[DarylD]

I like Linux, although I am not using it at the moment for OS development because I like the ability to use KaZaA while I code to build up my collection of MP3's (I know, its naughty, so shoot me!).

But it is the best OS there is for programming as far as I am concerned, if only because of the wealth of programming possibilities. All the source is available and even if the API's aren't documented brilliantly there is enough information to find things out and the developers are easy enough to get hold of. Try doing that on Windows!! Linux is home to all the development languages you could wan't as well and historically unix is the home of the most widely used (C/C++).

I have a soft spot for it because coding for KDE/QT is a dream, its such a well thought out design.

Perica, I agree with Pype, you are just not trying hard enough or not expert enough. Or is it the usual can't be bothered to learn problem?

Daryl.

[Perica]

..

[Whatever5k]

Why bother when there are things 10 times better than it (Windows)

Uh? What are these things (except the game factor)? Pype is right, you really are naive and you are starting to get on my nerves with your "Windows is great, Linux is ****" slogan - you don't even know what Linux is!

[Pype.Clicker]

i cannot tell without knowing what you're doing with that file ... it probably comes from an incompatible combination of command line arguments or something alike ... Check out what the arguments you supplied meant and try to figure out which one should be removed.

What i suggest is that you first produce one single .o file without any -oformat and THEN give that file to the linker and produce the binary out of it.

[Perica]

..

[Pype.Clicker]

elf files under windows ??

well, i understand better why you have that much troubles. Maybe if you can provide the whole building process i could help you better...

i mean what kind of object files are kernel32.o and kernelloader.o ? did you made them with GCC, does it come from earlier linking ...

maybe you gave those informations already (in which case i do apologize) but i've been lost a bit with that linux-vs-wind0w$ stuff... can you summarize your case ?

[Perica]

..

[Pype.Clicker]

i might be confused, but what's that "Output" that comes as the target of every "copy" command ? is this a file (are you trying to collect and concatenate the results of the miscellaneous binary file there ?) or is it just a directory ?

[Perica]

..

[Pype.Clicker]

hmmm ... If iirc, the g++ compiler you use will output PE (COFF) files, not ELF (unless you're the proud owner of a cross-compiler). Thus attempting to link ELF and PE files together will fail. You should (imho) ask nasm to output -fcoff instead of -felf ...