yesĬhecking whether we are cross compiling. a.outĬhecking whether the C compiler works. GNUĬhecking for C compiler default output file name. yesĬhecking for style of include used by make. bin/mkdir -pĬhecking whether make sets $(MAKE). usr/bin/install -cĬhecking whether build environment is sane. i686-pc-linux-gnuĬhecking for a BSD-compatible install. i686-pc-linux-gnuĬhecking host system type. Fingers crossed.Ĭhecking build system type.
OK, so far so good! It's successfully created a configure script, and now it's running that script.
To pass any to it, please specify them on the. configure with no arguments - if you wish Utility/Makefile.am:60: `%'-style pattern rules are a GNU make extension Putting files in AC_CONFIG_AUX_DIR, `bootstrap'.Ĭonfigure.ac:63: installing `bootstrap/missing'Ĭonfigure.ac:63: installing `bootstrap/install-sh'Īi/Makefile.am: installing `bootstrap/depcomp'Ĭommon/Makefile.am:97: `%'-style pattern rules are a GNU make extension > Package glibc-devel.i386 0:2.7-2 set to be updatedĪll right, try that freeciv]$. > Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc
#Freeciv 2.2.3 install
(You can also use the su -c command, which allows you to masquerade as ~]# yum install gcc
#Freeciv 2.2.3 software
When you're adding new software to the system, to be accessed by other programs and potentially other users, you need to be root. If you're going to work with Linux, you need to know when you need to be regular user, and when you need to be root. +++ README (working -193,3 +193,4 to self: pick up laundry. + printf("Sixty-five slices of American Cheese.\n") printf("Sixty-four slices of American Cheese.\n") You can find out exactly how you've modified things by running svn diff with no arguments, which prints out file changes in unified diff format: