Hi All, Cent OS 5.3. I need to install the gcc toolchain, but what yum packages is this? I need to compile ProFTPD, etc, etc. I tried yum install gcc, what else? -Jason
> Cent OS 5.3. I need to install the gcc toolchain, but what yum > packages is this? > > I need to compile ProFTPD, etc, etc. I tried yum install gcc, what > else?I fill follow up and say it seems that 'yum install gcc' is not enough because I get: [root at Server1 proftpd-1.3.2]# ./configure --sysconfdir=/etc checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl.exe... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. [root at Server1 proftpd-1.3.2]#
Jason Todd Slack-Moehrle wrote:> Hi All, > > Cent OS 5.3. I need to install the gcc toolchain, but what yum > packages is this? > > I need to compile ProFTPD, etc, etc. I tried yum install gcc, what else? > > -Jason >You could use "yum grouplist" to show available groups: yum grouplist Then, use "yum groupinfo" to check on a group that likely provides what you're looking for: [root at rover ~]# yum groupinfo "Development Tools" Loaded plugins: downloadonly, fastestmirror Setting up Group Process Loading mirror speeds from cached hostfile * rpmforge: ftp-stud.fht-esslingen.de * base: mirrors.versaweb.com * updates: mirror.sanctuaryhost.com * addons: mirror.hmc.edu * extras: mirror.dhsrv.com Group: Development Tools Description: These tools include core development tools such as automake, gcc, perl, python, and debuggers. [output truncated] Sounds like the group you want, so: yum groupinstall "Development Tools" should do the trick... -Greg
On Mon, May 4, 2009 at 7:48 PM, Jason Todd Slack-Moehrle <mailinglists at mailnewsrss.com> wrote:> I need to compile ProFTPD, etc, etc. I tried yum install gcc, what else?I'm going to trot out the soap box here for a moment. Why do you need to compile Proftpd? There are rpms for it which work flawlessly in centos. When you start building from source on a distribution designed for package management, you get all sorts of interesting problems creeping up. You should consider a source build as a last resort option when all else has failed. Most software has been packaged already, and if what you need hasn't been packaged, it isn't that hard to build an rpm yourself. Subverting the package management system because it seems faster isn't going to hurt you right away. It's the slow pain you end up with down the road when suddenly you look around and wonder how the hell you got here. Those are also the days when the support folks shrug and wander off because they don't know what you did or what you're using either. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell