its ok. No i don't have internet connection at all on my redhat which is why everything has been difficult for me.

Well again, i didnt contradict myself, there are 3 types of subscriptions: self support(used only for updates), premium and standard support that have telephone support and both are expensive. As a starter i think it is only trivial to start with the cheap($49/yr) self support.

2 members found this post helpful.

http://rpm.pbone.net/index.php3?stat...el6.x86_64.rpm
http://rpm.pbone.net/index.php3?stat...el6.x86_64.rpm
http://rpm.pbone.net/index.php3?stat...el6.x86_64.rpm

I would keep going, but I need some sleep for work.

Just search around between that site and others for the needed dependencies, which I think you remember me saying quite a few posts back....

1)
call red hat on the phone -- yes the phone
and use a credit card to BUY rhel6

then come back

also be advised that
1) red hat is DESIGNED for the "headless server" FIRST AND FOREMOST!
2) red hat is DESIGNED for the business office second
3) red hat is DESIGNED for the Laboratory to run the lab and the equipment
4 - a very large #
and DEAD LAST
on a laptop

rhel was NEVER designed or meant to be used on a laptop
most laptops will run it "mostly" well aad with minor issues
HOWEVER
rhel 6 will NEVER even install on some laptops


if you are NOT goint to buy a license for rhel6 then DO NOT USE RHEL !!!!!!!!!!!!!!!!!

by the way gcc and the devel tools are on the install dvd that you have so there is no need for a network connection
use the install dvd.

@OP

You can use your installation media (dvd or iso) as a repository for yum.
Take a look here for details.
Just note that the baseurl is the path the mount point of the installation media.

After that just run:
to install gcc with its dependencies and the other tools needed to compile software in linux

Regards

To the OP - Any luck yet?

And sorry for being arrogant yesterday, I was having a bad day with my depression. All good now!

No problem, and good to hear that all is now good. Well i was able to download the gcc from the site u gave me the other day but unfortunately when i ran each of the gcc, result indicated the need for more dependencies, and its becoming an infinite problem (z needs y needs x needs w needs v needs u).

So now i'm trying what the other contributor advised...running yum from dvd and see if it'll work.

And now you see why we are trying to steer you away from that Good old "dependency hell." I ran into that problem years ago when all I had access to at my old house was dial up..... Yes, I'm old, I know..... :/ LOL

And good luck trying to get it to work. Let us know how it goes.

Hello there,

I followed the guide from the link you provided me with but i got the following result:

root@localhost yum.repos.d]# yum groupinstall Development Tools
Loaded plugins: refresh-packagekit, rhnplugin
This system is not registered with RHN.
RHN support will be disabled.
Setting up Group Process
Warning: Group Development does not exist.
Warning: Group Tools does not exist.
No packages in any requested group available to install or update
[root@localhost yum.repos.d]#

[root@localhost yum.repos.d]# ls
yum.repos.d
[root@localhost yum.repos.d]# cat yum.repos.d
[rhel-dvd]
name=Red Hat Enterprise Linux Client version 6
baseurl=file:///media/RHEL/Client/
enabled=1
gpgcheck=0
[root@localhost yum.repos.d]#

my problem is going in to an infinite loop.

You forgot your quotation marks

same result with the quotation marks

root@localhost yum.repos.d]# yum groupinstall 'Development Tools'
Loaded plugins: refresh-packagekit, rhnplugin
This system is not registered with RHN.
RHN support will be disabled.
Setting up Group Process
Warning: Group Development does not exist.
Warning: Group Tools does not exist.
No packages in any requested group available to install or update
[root@localhost yum.repos.d]#

Hmm... Works on my machine. Try using double quotes.

To add to that - I actually came across a bug, maybe it is affecting you. Here is the bug report: http://bugs.contribs.org/show_bug.cg...ltiple&id=1894

same result.

hmm ..it seems i'm the only one that redhat is giving hard time, from one problem to another. Anyway hope is not lost

Did you look at the bug report? The information provided should be able to help you.