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.
I am now a converted Linux user. I am starting to be familiar with operating Linux and I am doing some programming with SDL. I want to start compiling source code to update my Mandrake 9.2. I want to do this in order to facilitate moving to debian in the next few months. I want to lean what is involved and how to compile source code for my computer namely gcc, kernel, fluxbox etc.
I realize I'll need to learn make, but I need to know so much....
well, i'd have to save the output to a file. i get the configure to work, but it appears that the make doesn't. let me check and i'll get back to you. i'll post the very long output.
that's what i figure i'd do. i know there is a make clean and will sort of clean things up, but is there an equivalent with ./configure? also, *warning* stupid question coming, is there a way that configure would have an error, but still say system configured correctly?
will do what you want with ./configure. I suppose it's possible for ./configure to finish properly yet have make fail if the configure script didn't check for everything possible, but then you'd expect the program author to have been informed about that by other people having problems.
ok. the configure seems to work. here is the long.... output from configure.
[root@localhost fluxbox-0.1.14]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/home/solitear/fluxbox-0.1.14/missing: Unknown `--run' option
Try `/home/solitear/fluxbox-0.1.14/missing --help' for more information
configure: WARNING: `missing' script is too old or missing
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C++ preprocessor... g++ -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 ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... no
checking if we can lock with hard links... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for sed... sed
checking for ANSI C header files... (cached) yes
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking dirent.h usability... yes
checking dirent.h presence... yes
checking for dirent.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking libgen.h usability... yes
checking libgen.h presence... yes
checking for libgen.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking process.h usability... no
checking process.h presence... no
checking for process.h... no
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking stdarg.h usability... yes
checking stdarg.h presence... yes
checking for stdarg.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/select.h usability... yes
checking sys/select.h presence... yes
checking for sys/select.h... yes
checking sys/signal.h usability... yes
checking sys/signal.h presence... yes
checking for sys/signal.h... yes
checking for sys/stat.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking whether time.h and sys/time.h may both be included... yes
checking for basename... yes
checking for getpid... yes
checking for setlocale... yes
checking for sigaction... yes
checking for strftime... no
checking for strcasestr... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for catopen... yes
checking for catgets... yes
checking for catclose... yes
checking for t_open in -lnsl... no
checking for socket in -lsocket... no
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for XOpenDisplay in -lX11... yes
checking whether to build support for the XShape extension... yes
checking for XShapeCombineShape in -lXext... yes
checking for X11/extensions/shape.h... yes
checking whether to include the Slit... yes
checking whether to include the new WM Spec... yes
checking whether to include Pseudocolor ordered dithering code... no
checking whether to include verbose debugging code... no
checking whether to include NLS support... yes
checking for setlocale in -lxpg4... no
checking for gencat... gencat
checking whether to use the new timed pixmap cache... yes
checking whether to have KDE slit support... no
checking whether to have GNOME support... yes
checking whether to have Xft support... yes
checking for xft-config... /usr/X11R6/bin/xft-config
checking Xft UTF-8 support... yes
checking whether to have Xmb (multibyte font, utf-8) support... yes
checking whether to build support for the Xinerama extension... no
checking return type of signal handlers... void
fluxbox version 0.1.14 configured successfully.
Using '/usr/local' for installation.
Using 'g++' for C++ compiler.
Building with '-g -O2 -I/usr/X11R6/include -DSHAPE -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/X11R6/include ' for C++ compiler flags.
Building with ' -L/usr/X11R6/lib -lX11 -lXext -L/usr/X11R6/lib -lXft -lX11 -L/usr/lib -lfreetype -lfontconfig -L/usr/X11R6/lib -lXrender ' for linker flags.
I hate to say it but you are going to have to install from CVS. That's a known issue in the latest "stable" source, but CVS works fine.
Here's what you need to do...
To install:
Code:
cd /usr/src/
cvs -qz3 -d:pserver:anonymous@cvs.fluxbox.sourceforge.net:/cvsroot/fluxbox co fluxbox && cd fluxbox && ./autogen.sh
./configure
make
make install
That will change you into /usr/src, download the source code from the Fluxbox CVS, change into the /usr/src/fluxbox directory and run the autogen.sh script. Then you just do your normal ./configure, make and make install stuff as you would with the source you downloaded before.
To update:
Code:
cd /usr/src/
cd fluxbox && cvs -qz3 update -PAd
This just updates all the changed files from CVS, and puts them in the /usr/src/fluxbox directory, after which you just do another configure / make / make install again.
Hope that helps. If you have any more issues, perhaps you should check out #fluxbox on Freenode.net...there are plently of people to help you there with specific fluxbox compile questions.
ok. i've upgraded autoconf. then i realize i need to login and signup and learn about CVS. right now i am extremely frustrated. now i see why linux will only be a geek plaything. yea, i know that MDK 10.0 has an rpm for Fluxbox, but the trouble is that i wanted to learn how to compile. i didn't realize i'd have to upgrade or install 3-4 packages and learn a development tool as ..................
forget it. it just ain't worth it..... Fluxbox that is...........
time to read a novel and forget about computers for a good long time.....
You should be able to type EXACTLY what I have in my first code quote, and that will work. Let us know if you have any issues. I started (and still have) the same problems as you...it's ok to struggle. You will learn.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Simple Tutorial for compiling source code?
Fluxbox that is...........
