Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
~/Desktop> gpg --verify gcc-fortran-4.3.3.tar.gz.sig gcc-fortran-4.3.3.tar.gz
gpg: Signature made Sat 24 Jan 2009 07:03:07 PM IST using RSA key ID FC26A641
gpg: Good signature from "Richard Guenther <richard.guenther@gmail.com>"
gpg: aka "Richard Guenther (Work) <rguenther@suse.de>"
gpg: aka "Richard Guenther <richard.guenther@gmx.net>"
gpg: aka "Richard Guenther (GCC) <rguenth@gcc.gnu.org>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1397 5A70 E63C 361C 73AE 69EF 6EEB 81F8 981C 74C7
Subkey fingerprint: 7F74 F97C 1034 68EE 5D75 0B58 3AB0 0996 FC26 A641
then i extracted the tar ball using tar and got "gcc-4.3.3" folder:
i did as you say above, i downloaded the gcc-gfortran from http://download.opensuse.org/distrib...s/suse/x86_64/.
but i get errors as:
/Desktop> rpm -ivh gcc-fortran-4.3-39.1.x86_64.rpm
error: Failed dependencies:
gcc43-fortran is needed by gcc-fortran-4.3-39.1.x86_64
again i downloaded gcc43-fortran from above site.
~/Desktop> rpm -ivh gcc43-4.3.1_20080507-6.1.x86_64.rpm
error: Failed dependencies:
cpp43 = 4.3.1_20080507-6.1 is needed by gcc43-4.3.1_20080507-6.1.x86_64
libmudflap0 >= 4.3.1_20080507-6.1 is needed by gcc43-4.3.1_20080507-6.1.x86_64
so, i think, due to failed dependencies problems( which may occur in future, when i need other packages ), i should add repo for 64 bit OS. Am i right knudfl?
i know how to add repo. But i don't have the " *.txt " file to add in "repos.d".
Can you provide me *.txt file?
i will add the repo *.txt as suggested by u you for 32 bit.
----------------------------------------------------
P.S. : The repo URL is the same for x86 and x86_64,
meaning that the "openSUSE-11.0-Oss.repo" ,
"openSUSE-11.0-Updates.repo" files can be used again .. http://www.linuxquestions.org/questi...d-11-768079/#7
------------------------------------------------------
With Warm regards,
kilam
Last edited by Kilam orez; 01-20-2010 at 09:23 AM.
Reason: to add
As already said, all text attachments here at LQ must
end with the suffix ' .txt '.
You will know that already, you used the files for your
32 - bit Suse. At least you said so, two months ago. # 10.
Suggest : may be have a look at your other system.
.....
As already said, all text attachments here at LQ must
end with the suffix ' .txt '.
You will know that already, you used the files for your
32 - bit Suse. At least you said so, two months ago. # 10.
Suggest : may be have a look at your other system.
.....
Dear Sir/Madam
I also need gfortran 4.3.3 but I don;t know where to download,
If it is possible, you can share for me or tell me website to download
Thank you
Chinh
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.