gcc-5.3.0 available as a pet file
Posted: Tue 05 Apr 2016, 08:16
Hello all.
As the title says: the latest (as of this writing) gcc 5.3.0 is now available as a pet
file, from here: -- https://www.adrive.com/public/ENWcjv/gcc-5.3.0.pet --.
I compiled it on a Dpup Wheezy. I used it successfully on josejp2424's
pupjibaro-jessie-beta to compile one utility.
I think that a couple more tests would be needed to declare this compilation
a full success. TIA.
As I mentioned above, it does work. However, since this is my first try at compiling
such a big and important part of "the tool chain", feedback would be welcome:
a vetting if I did things right or a "constructive mouthful" if I did it wrong -- so I
can set it right. Again, TIA.
May I suggest the following if you intend to use it:
-- First load your present devx, if it's not already. Then install this pet archive.
Because gcc needs other "tool chain" programs provided by / located in the devx.
-- Upon install, it will of course lay on top of / supercede / hide (for lack of a
better verb) the gcc that is currently in your devx. Which is the idea.
Ref.: -- https://gcc.gnu.org --
Enjoy.
As the title says: the latest (as of this writing) gcc 5.3.0 is now available as a pet
file, from here: -- https://www.adrive.com/public/ENWcjv/gcc-5.3.0.pet --.
I compiled it on a Dpup Wheezy. I used it successfully on josejp2424's
pupjibaro-jessie-beta to compile one utility.
I think that a couple more tests would be needed to declare this compilation
a full success. TIA.
As I mentioned above, it does work. However, since this is my first try at compiling
such a big and important part of "the tool chain", feedback would be welcome:
a vetting if I did things right or a "constructive mouthful" if I did it wrong -- so I
can set it right. Again, TIA.
May I suggest the following if you intend to use it:
-- First load your present devx, if it's not already. Then install this pet archive.
Because gcc needs other "tool chain" programs provided by / located in the devx.
-- Upon install, it will of course lay on top of / supercede / hide (for lack of a
better verb) the gcc that is currently in your devx. Which is the idea.
Ref.: -- https://gcc.gnu.org --
Enjoy.