In your console output it says: Maybe run: yum groups mark install (see man yum)—did you do this?
Try running the following commands:
yum groups mark install "Development Tools"
yum groups mark convert "Development Tools"
yum groupinstall "Development Tools"
Reference: RedHat Customer Portal discussion
Answer from ThatsWhatSheCoded on Stack ExchangeIn your console output it says: Maybe run: yum groups mark install (see man yum)—did you do this?
Try running the following commands:
yum groups mark install "Development Tools"
yum groups mark convert "Development Tools"
yum groupinstall "Development Tools"
Reference: RedHat Customer Portal discussion
Try:
yum group list
To see if yum can find the Development Tools under Available Groups.
If it fails, try:
yum clean all
yum group list
And see if it can find it. If it still fails, you might not have the correct mirrors enabled to resolve it.
try the clean command again and then:
yum --disablerepo=\* --enablerepo=base,updates group list
If you can find it. Great! Install with:
yum --disablerepo=\* --enablerepo=base,updates groupinstall "Development Tools"
If not so, can you give us the output of:
yum repolist all
EDIT:
Thank you for the output.
I found an article which state the following: "To install the CentOS Development tools, you will need to be able to connect to your Virtual Server using SSH, and work as the root user."
Try switching to user "root" (if you don't know the root login credentials, you can try sudo su. sudo also might work but I see you already have tried that...) and running the above commands.
Lastly, you can try and enable these "sources" repos:
- CentOS-7 - Base Sources
- CentOS-7 - Extras Sources
- CentOS-7 - Updates Sources
And than running yum update followed by groupinstall.
Let me know if that doesn't work. Good luck!
Videos
So, two things...
One: Certificate based repositories are a function of "subscription_manager" while "RHN Classic" is the traditional RHN. First you need to know which type your system is using. If it's "certificate-based repositories" (aka subscription_manager) then you'll see the file /etc/yum.repos.d/redhat.repo with content like:
[rhel-6-server-rpms]
name = Red Hat Enterprise Linux 6 Server (RPMs)
baseurl = https://cdn.redhat.com/content/rhel/server/6/$releasever/$basearch/os
enabled = 0
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-beta,file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
sslverify = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientkey = /etc/pki/entitlement/1111111111111111111-key.pem
sslclientcert = /etc/pki/entitlement/1111111111111111111.pem
metadata_expire = 86400
If this is the case you're likely using subscription_manager, if on the other hand you have a file located at: /etc/sysconfig/rhn/systemid then the system has been registered via "RHN Classic". Regardless, whichever method you have used, the other one should be turned off. This can be done by configuring the corresponding plugin's config located in: /etc/yum/pluginconf.d/
For "RHN Classic" this will be the file "rhnplugin.conf" and for "subscription_manager" it will be "subscription-manager.conf". These are enabled/disabled by setting the boolean value "enabled=[0|1]" in the corresponding configuration file. If you have neither of these configurations then your system is not registered via RHN/subscription_manager and despite having local administration privileges you should contact your sysadmin who is in control of your RHN entitlements. If you are registered, let's keep going.
Once you have disabled the plugin you have chosen not to use, verify that you can see the groups available and no error messages via the command:
yum grouplist
or, even better:
yum grouplist | grep -i development
this should yield output similar to:
redbeard@yum01 [~]# yum grouplist | grep -i development
Additional Development
Desktop Platform Development
Development tools
Server Platform Development
You'll notice that the name "Development tools" has a lowercase initial character in the second word. I did validate that this should work regardless of case.
redbeard@yum01 [~]# sudo yum groupinstall "Development Tools"
Loaded plugins: product-id, security, subscription-manager
This system is receiving updates from Red Hat Subscription Management.
Setting up Group Process
Package 1:pkgconfig-0.23-9.1.el6.x86_64 already installed and latest version
Package binutils-2.20.51.0.2-5.36.el6.x86_64 already installed and latest version
Package elfutils-0.152-1.el6.x86_64 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package autoconf.noarch 0:2.63-5.1.el6 will be installed
---> Package automake.noarch 0:1.11.1-4.el6 will be installed
---> Package bison.x86_64 0:2.4.1-5.el6 will be installed
---> Package byacc.x86_64 0:1.9.20070509-7.el6 will be installed
---> Package cscope.x86_64 0:15.6-6.el6 will be installed
---> Package ctags.x86_64 0:5.8-2.el6 will be installed
....
Nowadays It's not enough being registered the system and it's required "Service Level Preference" to at least "Self-Support". Repository availability is depend on the Service Level Preference. So use following steps to acquire correct service level.
Further after register system using "subscription-manager" on command line, it's possible to manage other features at the Subscription Management Web Portal.
01. Check your enabled subscriptions
subscription-manager list
02. Register your system to Customer Portal Subscription Management
subscription-manager register --username your_username --password your_password
03. List the available service levels
subscription-manager service-level --list
04. Set a your desired level use the switch
subscription-manager service-level --set=self-support
subscription-manager list
05. list of all your provided repositories through a certain subscription
subscription-manager repos --list
yum repolist all
Note: If subscribing is not working can use auto option as follows.
subscription-manager attach --auto
To remove all subscriptions
subscription-manager remove --all
To achieve install development tools use following steps.
01. To find out what is in this group use command
yum groupinfo "Development Tools"
OR
yum grouplist | grep -i development
02. Install Development Tools
yum groupinstall "Development Tools"
03. Check and verify Installed Versions of few tools
gcc --version
make --version
I think your question on development packages removal has a two part answer. The first part is to remove the -devel packages as recommended by others. This will remove the development interfaces for applications such as httpd-devel.
The second part is core development packages for basic development, mostly needed if you need to install program from source code. RHEL groups this packages under Development tools. You can remove these packages using -
yum groupremove "Development tools"
Personally I wouldn't install any development packages on production servers as SvenW mentioned. So I would start with a clean base installation without any development packages and then explicitly install only the absolutely needed ones later depending on your requirements.
yum remove $(rpm -qa "*-devel")
Also, don't do development on your production (or even staging) systems. If you really must rebuild an RPM, use mock which builds it in a chroot and can clean up after itself.