OSDev.org

Hello guys. I have built i586-elf compiler in my last linux distro and it was wroking well. But my distro crashed and I copied all my files (Including cross compiler) from $HOME to another drive and after installing another distro, I copied them back. And now when I want to use my cross compiler (i586-elf-gcc) it gives me an error in linking process. It says: I really don't know what to do. I don't have enough time to rebuild the compiler again cuz it took a lot of time on my old PC.
Please help and tell me what should I do

A quick and dirty guess is that -fno-use-linker-plugin could surpress the error. Better yet, installing liblto_plugin.so is a better idea. My magic crystal ball tells me you have switched distribution, and something ABI-like has changed incompatibly.

I recommend you rebuild the cross-toolchain from scratc again. It'll take a while (takes a couple minutes for me with -j8), but it is worth it. Remember, it takes much less time than building an operating system.

You probably built binutils with gold lto plugin, but it was installed someplace you didn't copy over.

Rebuilding new binutils with gold could help.
Or just grab a premade cross-compiler from wiki.

sortie wrote: installing liblto_plugin.so is a better idea

How can I do that?

sortie wrote: I recommend you rebuild the cross-toolchain from scratc again. It'll take a while (takes a couple minutes for me with -j8)

You may have a super PC. But my little PC built it in more than 80 minutes!!!!!

sortie wrote: Remember, it takes much less time than building an operating system

Are you kidding me?




Would you lend me your liblto_plugin.so file and tell me where should I copy it to get my toolchain working? (If it's possible )
Else I should rebuild it and wait for couple of hours to finish

But my little PC built it in more than 80 minutes!!!!!

That means the problem could've been solved now

Seriously, it's more effective, a better exercise, and spares you from the many attempts of getting another incompatible library.

MadZarx wrote:

sortie wrote: installing liblto_plugin.so is a better idea

How can I do that?
Would you lend me your liblto_plugin.so file and tell me where should I copy it to get my toolchain working? (If it's possible )
Else I should rebuild it and wait for couple of hours to finish

Yes, of course, let me upload a virus called liblto_plugin.so so you can install it. Or rather, you can find out what it is and possibly install it from your distribution.

MadZarx wrote:

sortie wrote: Remember, it takes much less time than building an operating system

Are you kidding me?

What did you expect? I spend years on my OS - a couple hours rebuilding a compiler is nothing.

MadZarx wrote:

sortie wrote: Remember, it takes much less time than building an operating system

Are you kidding me?

Android takes about 5-7 hours first build, and 2-3 hours on subsequent builds.
Or, if you want a full os, I hear you'll have a finished kernel in 2 weeks if you go the linux route. Not sure how long the rest takes.

Linux kernel takes under 5 minutes, about the same time as gcc. Last time I did a full LFS build it took about 12 hours - but that computer was a bit slower than the current one.

iansjack wrote:Linux kernel takes under 5 minutes, about the same time as gcc. Last time I did a full LFS build it took about 12 hours - but that computer was a bit slower than the current one.

Would you please inform us of your supercomputer's specs?

m12 wrote:

iansjack wrote:Linux kernel takes under 5 minutes, about the same time as gcc. Last time I did a full LFS build it took about 12 hours - but that computer was a bit slower than the current one.

Would you please inform us of your supercomputer's specs?

If you configure the kernel to CONFIG_everything=n then it will be reaaaally fast to compile.
And even with more modules, modern i7 compiles it within minutes.

dozniak wrote:

m12 wrote:

iansjack wrote:Linux kernel takes under 5 minutes, about the same time as gcc. Last time I did a full LFS build it took about 12 hours - but that computer was a bit slower than the current one.

Would you please inform us of your supercomputer's specs?

If you configure the kernel to CONFIG_everything=n then it will be reaaaally fast to compile.
And even with more modules, modern i7 compiles it within minutes.

On my computer, GCC takes about 50-65 minutes to compile. I haven't ever built Linux, but if gcc takes 5 minutes on his, then theoretically, Linux would take 5-7 days whole on mine (I'm aware of my loose logic).

m12 wrote:

iansjack wrote:Linux kernel takes under 5 minutes, about the same time as gcc. Last time I did a full LFS build it took about 12 hours - but that computer was a bit slower than the current one.

Would you please inform us of your supercomputer's specs?

Sure. The processor is a bog-standard i7-3770, and I have 8 GB of RAM. Those are the only important specification as far as compile times are concerned. I'm running a carefully optimized Gentoo distribution; I find that most off-the-peg distributions are pretty slow compared to a good optimized setup. I only enable those modules that I need in the kernel - no point in compiling support for RAID cards, Amiga file system, or token ring network cards.

How long does your computer take to compile the kernel (I'll discount the 2 days)?

A good test of how long it takes to compile a full Linux distribution would be to do a complete rebuild of a Gentoo installation; any half-decent computer should be able to do that in much less than a day.

m12 wrote:I haven't ever built Linux

Well, that certainly explains your comments on the subject.

Even on a really underpowered ARM NAS box I find that kernel compilation takes only a couple of hours. gcc takes four hours or so on my Raspberry Pi. With 8 much faster cores and 64 times as much RAM it's not really that surprising that it is marginally faster on my main computer.

Try compiling the kernel some time; you will find that it does not take 150 times as long as gcc.

WOW. What the hell
So I have to buy a new PC for OS devel. So I should rebuild GCC and it seems there is no solution for my problem.

You all guys have something more than a supercomputer that you can build GCC in less than 5 minutes.
But mine is 8 years old with 1GiB RAM and 2.8GHz CPU. So I think if I build Linux, it would take a couple of weeks

Oh the nonsense.

I'd think that anybody that wants to make a somewhat sane OS should have performed and maintained a gentoo (or LFS) install at least once. It teaches you a fair share of tricks for your OS, demonstrates the complete brokenness of autoconf and generally gives you an idea of where the system weight truly lies.

Besides, on my old Athlon64 (less Hz, less RAM), it took less than 24 hours to build the kernel, gnome, kde and firefox from nought.

Compilers and graphical browsers are hideous in complexity compared to the other parts of the system.